aboutsummaryrefslogtreecommitdiffstats
path: root/actionview/test/ujs/public
Commit message (Collapse)AuthorAgeFilesLines
* Fix mistake in JS response parser:Dmytro Vasin2017-04-131-0/+28
| | | | | | - Restore ability to accept ecmascript JS response should not modify DOM.
* Set current page as default for ajax requestsDmytro Vasin2017-04-111-22/+45
|
* Prevent event propogation if element is disabled when event chain begins.Patrick Toomey2017-03-091-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | | The existing UJS event behavior relies on browsers not sending events for various events when an element is disabled. For example, imagine the following: <button type="submit" disabled="disabled">Click me</button> The above button is disabled, so browsers will not trigger a click event and all UJS behavior is prevented. However, imagine a button like this: <button type="submit" disabled="disabled"><strong>Click me</strong></button> The above is treated differently by browsers such as Chrome/Safari. These browsers do not consider the strong tag to be disabled, and will trigger click events. UJS has logic to walk up the DOM to find an associated element subject to UJS behavior. But, this logic does not take into account the disabled status of the element. I originally thought we could simply change the selectors used to match elements to ignore disabled elements. However, UJS disables some elements as part of the event chain. So, an element might match early in the chain and then fail to match later. Instead of changing the selectors I added a callback to the chain that calls `stopEverything` if an element is disabled when the event chain begins.
* Import rails-ujs v0.1.0 from rails/rails-ujsGuillermo Iguaran2017-02-204-202/+21
|
* Correct spellingBenjamin Fleischer2017-02-051-1/+1
| | | | | | | ``` go get -u github.com/client9/misspell/cmd/misspell misspell -w -error -source=text . ```
* s/an/a/Akira Matsuda2017-01-261-1/+1
| | | | [ci skip]
* Add UJS testsGuillermo Iguaran2016-11-2615-0/+5092