We have counters for it too (which is almost zero it seems):

https://www.chromestatus.com/metrics/feature/timeline/popularity/798
https://www.chromestatus.com/metrics/feature/timeline/popularity/799

Marking as Available.

WIP CL : https://codereview.chromium.org/2730413003/

I think we should handle the two style elements together here. These are the counters for HTMLStyleElement:
https://www.chromestatus.com/metrics/feature/timeline/popularity/812
https://www.chromestatus.com/metrics/feature/timeline/popularity/813

Usage is a bit high for comfort. The first step here I think is to understand how all the disabled IDL and content attributes fit together, and which bits are already shipping in all browser engines. I have a 50% hunch that the right path here will be to just add these things back to the specs.

The HTMLLinkElement use counter is also relevant:
https://www.chromestatus.com/metrics/feature/timeline/popularity/809

Throwing in HTMLLinkElement into this bucket of work as well.

Our IDL files link to this spec bug:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14703

This is tracked as https://github.com/whatwg/html/issues/1081. The problem is that the Chrome code for this (and probably the WebKit code also) is weirdly complicated and so I wasn't very keen on speccing it, especially without knowing what other UAs do.

My ideal scenario would be discovering that Gecko and/or Edge implement a much simpler model, and that all the browsers are OK with converging on that.

Out of these three element interfaces, all four engines have disabled everywhere, with one exception: Gecko doesn't have SVGStyleElement#disabled.

All engines also have StyleSheet#disabled, although that isn't being considered for removal anyway.

Concrete next step for this issue: Investigate in more detail what these IDL attributes do in each engine. One oddity to look at is the fact that HTMLLinkElement#disabled is a reflected attribute in Blink, but HTMLStyleElement#disabled and SVGStyleElement#disabled are bare IDL attributes.

domenic@, do you know of other odd things that should be investigated?

 Issue 866305  has been merged into this issue.