The order of toggle events on details element is not follow the spec
Reported by
t...@mozilla.com,
Mar 10 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:46.0) Gecko/20100101 Firefox/46.0 Example URL: https://jsfiddle.net/aethanyc/oq2qLg48/ Steps to reproduce the problem: Open https://jsfiddle.net/aethanyc/oq2qLg48/ What is the expected behavior? The div with yellow background has text "toggle details1 toggle details2" What went wrong? The div with yellow background has text "toggle details2 toggle details1" Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: <Copy from: 'about:version'> Channel: n/a OS Version: OS X 10.11 Flash Version: Shockwave Flash 20.0 r0 If I read the spec correctly, "details.open = false;" should not fire a toggle event since the toggle event trigger by "details.open = true;" has been queued. https://html.spec.whatwg.org/multipage/forms.html#details-notification-task-steps
,
Mar 10 2016
,
Mar 10 2016
,
Mar 11 2016
Sorry, I was somehow misreading the spec; it looks like Chromium's behavior is correct.
,
Mar 17 2016
I think this bug can be closed as invalid since I read the spec wrong.
,
May 5 2016
Since as per spec blink works as expected, closing this bug. https://html.spec.whatwg.org/multipage/forms.html#details-notification-task-steps When the open attribute is toggled several times in succession, these steps essentially get coalesced so that only one event is fired. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dglazkov@chromium.org
, Mar 10 2016Components: -Blink Blink>HTML>Details
Labels: -Pri-2 OS-All Pri-3
Status: Untriaged (was: Unconfirmed)