- From: Anne van Kesteren <notifications@github.com>
- Date: Wed, 12 Oct 2016 03:48:53 -0700
- To: whatwg/dom <dom@noreply.github.com>
Received on Wednesday, 12 October 2016 10:49:21 UTC
There's another major difference between implementations here. It seems Chrome/Safari follow HTML when it comes to only running the pre/post steps for a single element, whereas Firefox does it for the entire event path. Simple demonstration: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/4570. (What Chrome/Safari matches HTML's current language around "activation behavior" and seems better.) (Note that you cannot mutate the event path so you'll always get the same element.) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/325#issuecomment-253180903
Received on Wednesday, 12 October 2016 10:49:21 UTC