AjaxSource: replace global with eventPropagation / deprecate global
See original GitHub issueSee #8302
The eventPropagation
attribute will be used to trigger a local and/or a global Ajax status based on the value.
Possible values: component
,global
,both
(default),none
.
Whether component
(or local) Ajax status will be applied depends on the component, if it’s implemented in its widget.
global
will be deprecated in 12, removed in 13. If you would use global="false"
, that will imply eventPropagation="none"
. If you would use both global="false"
and eventPropagation
, global
would “win” as eventPropagation
has a default value.
Issue Analytics
- State:
- Created 2 years ago
- Comments:24 (22 by maintainers)
Top Results From Across the Web
JQMIGRATE: Global events are undocumented and deprecated
This is a piece of code from JQMIGRATE responsible for warning // Turn global events into document-triggered events jQuery.event.trigger ...
Read more >event.stopPropagation() | jQuery API Documentation
Description: Prevents the event from bubbling up the DOM tree, preventing any parent handlers from being notified of the event. version added: 1.0event....
Read more >datatables column filtering disable search on last ... - You.com
I'd like to remove the global search box, but leave the column filtering functionality in tact. It appears that setting bFilter: false removes...
Read more >Rev 2807 and /web/ Rev 2808 - WebSVN – ALCASAR
DESC : Designed to fix that problem by applying appropriate filters to user specified elements, while keeping all element tags intact. USED :...
Read more >The Dangers of Stopping Event Propagation - CSS-Tricks
Like a lot of things in JavaScript, DOM events are global. And as most people know, global variables can lead to messy, coupled...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
i would like to hear opinions of @Rapster @christophs78 @melloware @mertsincan
Thomas said “This is a hard question. I think it general it makes sense to make it configurable but enable it per default as AJAX requests are queued anyway and does not make problems. Im not sure if anyone use it async requests and spawn multiple requests but…” @jepsar I added a comment for 2, referring to this. You can ignore my comment about “Discussions”. If the disableOnAjax attribute is ok for all of us, I think we can add it.