- From: <bugzilla@jessica.w3.org>
- Date: Wed, 08 Aug 2012 05:17:52 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18455 --- Comment #4 from Shinya Kawanaka <shinyak@chromium.org> 2012-08-08 05:17:51 UTC --- (In reply to comment #3) > Let me reopen this. > > It sounds reasonabe, but there are some use cases that we must handle. > > When I tried to add 'load' and 'error' events to the 'stop' list, some layout > tests in WebKit started to fail. > One of them is a fast/dom/shadow/shadowdom-for-image-dynamic.html. > > We have some layout tests which depends on an assumption like the following: > 1. <img> element, which will be a shadow host, has a 'onload' listener. > 2. A user adds a shadow root to the <img> element. > 3. The listener registered on the shadow host should still receive a 'load' > event for the 'image'. > > So we will break the compatibility in this case. Yeah, I think this change will conflict to replaced elements spec. When considering Replaced Elements like <img>, it seems natural that 'load' event is fired on a special element in the shadow subtree of <img>, because an element in shadow subtree would like to handle 'load' event. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 8 August 2012 05:17:53 UTC