See https://github.com/web-platform-tests/wpt/pull/22645 and https://github.com/whatwg/html/pull/4519.
<rdar://problem/96304439>
It looks like we fail a couple of these tests (though we pass most). Importing.
We are only browser failing but just two tests: https://wpt.fyi/results/css/cssom?label=master&label=experimental&aligned=&q=cssom%2Fhtmllinkelement-
Blink Commit - https://chromium-review.googlesource.com/c/chromium/src/+/2216701
(In reply to Ahmad Saleem from comment #3) > We are only browser failing but just two tests: > > https://wpt.fyi/results/css/ > cssom?label=master&label=experimental&aligned=&q=cssom%2Fhtmllinkelement- The patch in https://github.com/WebKit/WebKit/pull/17001 gets WebKit passing all those tests. But that patch isn’t a full implementation of the spec requirements in https://github.com/whatwg/html/pull/4519. I have a separate patch that implements the “explicitly enabled” boolean flag specified in https://github.com/whatwg/html/pull/4519 — but I don’t yet know how to test it, or if WebKit even needs it. I say that because HTMLLinkElement-disabled-003.html to HTMLLinkElement-disabled-007.html there all include some tests for the “explicitly enabled” requirements — but since WebKit is already passing all those tests, then it seems like either those tests aren’t correctly testing the “explicitly enabled” requirements, or else the WebKit implementation somehow already conforms to those requirements.
The "explicitly enabled" boolean flag is implemented as m_disabledState == EnabledViaScript in WebKit.
(In reply to Emilio Cobos Álvarez (:emilio) from comment #6) > The "explicitly enabled" boolean flag is implemented as m_disabledState == > EnabledViaScript in WebKit. aha, I see now — thanks much
Should this be duped to bug 260642?