This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This was was cloned from bug 17165 as part of operation convergence. Originally filed: 2012-05-24 05:35:00 +0000 ================================================================================ #0 contributor@whatwg.org 2012-05-24 05:35:13 +0000 -------------------------------------------------------------------------------- Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html Multipage: http://www.whatwg.org/C#styling Complete: http://www.whatwg.org/c#styling Comment: Need to define processing model for style and link Posted from: 71.184.125.56 by bzbarsky@mit.edu User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/15.0 Firefox/15.0a1 ================================================================================ #1 Boris Zbarsky 2012-05-24 05:36:33 +0000 -------------------------------------------------------------------------------- In particular, at what points are the stylesheets actually loaded/parsed respectively? What happens if the DOM inside <style> is mutated? What happens if the CSSOM is mutated and then attributes that affect the styling behavior (e.g. title, rel, media) are changed? UAs seem to be somewhat inconsistent on all this stuff. ================================================================================ #2 Boris Zbarsky 2012-05-24 05:37:33 +0000 -------------------------------------------------------------------------------- Also, how changes to rel and media interact with .disabled. ================================================================================
Mass move to "HTML WG"
Keeping the WHATWG bug and this one in sync related to resolution/fix. *** This bug has been marked as a duplicate of bug 17999 ***