26454 2014-07-29 09:39:05 +0000 <fieldset> elements that are descendants of disabled <fieldset> elements should also match :disabled 2014-09-05 23:01:20 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#disabled-elements P3 normal Unsorted 1 contributor ian ian mike Ms2ger contributor oldest_to_newest 109477 0 contributor 2014-07-29 09:39:05 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/scripting.html Multipage: http://www.whatwg.org/C#disabled-elements Complete: http://www.whatwg.org/c#disabled-elements Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/scripting.html Comment: fieldset descendant of a disabled fieldset should match :disabled Posted from: 87.64.245.230 by ms2ger@gmail.com User agent: Mozilla/5.0 (X11; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0 109478 1 Ms2ger 2014-07-29 09:46:23 +0000 Looking at <http://software.hixie.ch/utilities/js/live-dom-viewer/saved/3080>, Fx and Chrome already do this; IE (or at least the version I have here, claims to be 11.0.9431.0) seems to pay no attention to fieldset[disabled] for :disabled matching at all. 109483 2 Ms2ger 2014-07-29 10:37:51 +0000 Anne says Safari matches Fx/Chrome. 109503 3 ian 2014-07-29 16:51:25 +0000 That's... what the spec says, no? 109505 4 Ms2ger 2014-07-29 16:54:26 +0000 <http://www.whatwg.org/html/#concept-element-disabled> says "fieldset elements that have a disabled attribute" 109506 5 ian 2014-07-29 16:57:28 +0000 Ah, interesting. I wonder how we ended up with interop here! I'll update the spec. 111115 6 contributor 2014-09-05 23:01:20 +0000 Checked in as WHATWG revision r8753. Check-in comment: Make sure :disabled matches fieldsets inside disabled fieldsets, since apparently that's a thing. Also, editorial cleanup around 'disabled'. http://html5.org/tools/web-apps-tracker?from=8752&to=8753