Fortgeführter Thread
@webkit Also, while I'm here, #firefox #mozilla @FirefoxDevTools where's my support for `has(...)` at!?!
#testthewebforward
0 Beiträge0 Beteiligte0 Beiträge heute
Antwortete im Thread
@matuzo Shadow DOM isn’t the only part of the platform that #webComponent popularity is adding pressure on automated tools to support. Things like Element Internals are getting left off the menu in many places, like https://github.com/dequelabs/axe-core/issues/4259, just as they and soon things like Reference Targets start to expand as well.
I love it when a plan comes together!!
`has(...) {}` is now shipping in Chromium!
issues.chromium.orgChromium
Fortgeführter Thread
Non-controversial selector testing shipped!
Now, let's get people checking out https://github.com/web-platform-tests/wpt/pull/47441 and its thoughts on `:host(:has(...)` (which great browsers like @webkit have already shipped) and `has(...)` https://github.com/w3c/csswg-drafts/pull/10586 which will be really powerful when `::has-slotted(...)` starts to ship.
GitHubTest :host(:has(...)) and :host:has(...) selectors by Westbrook · Pull Request #47441 · web-platform-tests/wpt
A little Saturday #webPlatformTests writing session going on over here:
- https://github.com/web-platform-tests/wpt/pull/47440
- https://github.com/web-platform-tests/wpt/pull/47441
That second one's a little spicy with both unspec'd behavior based on mixed implementation and "tentative" tests for things no browser has started to support yet.
GitHubEnsure :part(...):disabled works alone and in grouped selectors by Westbrook · Pull Request #47440 · web-platform-tests/wpt