This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#the-details-element Complete: http://www.whatwg.org/c#the-details-element Referrer: Comment: Shouldn't <details> also allow intermixed script-supporting elements (before the <summary>)? Posted from: 2a00:801:e0:30:d9c4:c34f:b530:6023 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 OPR/21.0.1432.48 (Edition Next)
Is there any benefit to putting a <script> element before the <summary> rather than after it? Note that <style scoped> elements are just allowed where the flow content starts, not at the start of the parent element. Why would that not be enough for script also?
The end result for <style> is the same if it's first or not (modulo selectors I guess). The same is not true for <script> -- the DOM is different when the script runs. (But I'm not sure the current situation is great for <style scoped> either.)
I agree that the DOM would be mildly different, but it's not clear that that is a particularly big deal here.
Let’s re-raise this in the GitHub issue tracker if necessary.