Project

General

Custom queries

Profile

Actions

Bug #1528

closed

Cancel button on pop-up fire an AJAX request and sometimes lag

Added by François ARMAND over 13 years ago. Updated almost 8 years ago.

Status:
Rejected
Priority:
4
Assignee:
-
Category:
Architecture - Code maintenance
Target version:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
31
Name check:
Fix check:
Regression:

Description

For (all ?) pop-up used to create items, like "configuration rule creation pop-up", the cancel button should only close the pop-up, a pure JS, client-side event. But currently, they fire an Ajax request, that does nothing (safe spending time one server and leading to some client side lag).

=> replace SHtml.ajaxButton("Cancel", { () => closePopup() }) by something like: <button onclick="closePopup();return false;">Cancel</button>

Actions #10

Updated by Nicolas CHARLES over 10 years ago

Hum, i can prevent having a post+get, to have only an empty post, but i'm don't know how to do better than that...

Actions #11

Updated by Nicolas CHARLES over 10 years ago

even hardcoding the button in the template and removing everything on scala will still trigger a post, as it is inside a form that we close
i'm not sure which solution i should use...

Actions #17

Updated by Nicolas CHARLES about 10 years ago

  • Assignee changed from Nicolas CHARLES to François ARMAND

i'm reassigning this ticket to you Francois, as I couldn't fix it

Actions #46

Updated by Raphael GAUTHIER almost 8 years ago

  • Status changed from New to Rejected

This bug doesn't appear anymore.
Rejecting

Actions

Also available in: Atom PDF