#testTheWebForward

westbrookwestbrook
2026-02-09

Inversely, I love, love, love how this "just worksℒ️" in 😍

codepen.io/Westbrook/pen/XJKye

Where's my and peeps at?!?

You're seeing that right, `:host(:has(...))` and `:host:has(...)` are different, in a good way, but supported differently across browsers, in a bad way. Let's go head a build ALL the things that are meant to be in the browser. Not just some.

Pretty please πŸ™

westbrookwestbrook
2026-02-09

Love, love, love how this "just works ℒ️" in and 😍

codepen.io/Westbrook/pen/KwMrm

Where's my peeps at?!?

westbrookwestbrook
2025-12-31

_IS_ a browser.

The fact that it cannot see what a browser sees is...disappointing, at best.

If the browser can build the correct AccessibiliTree from the code to pass on to the Assistive Technology of your visitors choice, why can't Playwright? I just want to test my apps that way an actual visitor would use them and not with some alternate interpretation. Alas.

github.com/microsoft/playwrigh

westbrookwestbrook
2025-10-11
westbrookwestbrook
2025-10-07

Writing tests this Tuesday morning. 😁

Forgot how nice it is to _be sure_ the code your team writes works!

westbrookwestbrook
2025-08-07

Because the world should be a slightly better place, and that includes the often greater that 1/3 of my week where working is happening, let people know how you feel about HTML at survey.devographics.com/en-US/ Future us's will thank us. 🀨

westbrookwestbrook
2025-06-06

@webkit Also, while I'm here, @FirefoxDevTools where's my support for `:host:has(...)` at!?!

westbrookwestbrook
2025-06-02

Who can tell which is correct?

When visiting codepen.io/Westbrook/pen/gbpMb should there be four red squares (Blink) or four vertical red bars/lines (FF/WebKit)?

Not sure which is the bug to submit one. Help!

The Blink rendering of this page with four red boxes.The FF/WebKit rendering of this with four red lines.
westbrookwestbrook
2025-05-22

If you like this sort of content, or are diving into consuming/developing a myriad of new or long standing APIs available as web components, come join the conversation around making them better at discord.gg/kbba8cKPg9

westbrookwestbrook
2025-05-19

@matuzo Shadow DOM isn’t the only part of the platform that popularity is adding pressure on automated tools to support. Things like Element Internals are getting left off the menu in many places, like github.com/dequelabs/axe-core/, just as they and soon things like Reference Targets start to expand as well. πŸ₯Ί

westbrookwestbrook
2025-02-25

Perf test your website/app on cell service while you wait for you dentist. It’ll either feel horrible, getting you ready for the cleaning, or feel great, getting you ready for the cleaning. The change I’m making appears to give ~5s back to visitor by not rendering a bunch of unnecessary UI. AND, there’s more work to be done!

Clear teeth, clean web.

westbrookwestbrook
2024-11-19

@intenttoship :ThisTBH: πŸ‘ πŸ‘ πŸ‘ πŸ‘ πŸ‘

westbrookwestbrook
2024-11-06

Added a bunch of new tests, results, and thoughts. Hope you'll take a look at share the results you're seeing when testing locally!

westbrookwestbrook
2024-10-29

@pablolarah @eric @piccalilli Can’t wait till all browsers support `:host(:has(…))` the way does and partially does so that this is even more natural for development, too.

wpt.fyi/results/css/css-scopin

westbrookwestbrook
2024-10-18

I love it when a plan comes together!!

`:host:has(...) {}` is now shipping in Chromium! πŸͺ„ πŸ’« ✨

issues.chromium.org/issues/359

westbrookwestbrook
2024-10-14

If you're into using `@property {}` declarations with `light-dark()` values, you may want to track this issue in ...

bugzilla.mozilla.org/show_bug.

Seems to get stuck in the "light" value when defined by `@property {}` 😞

westbrookwestbrook
2024-09-23

Who ever thought that writing tests for under discussion browser features would be so relaxing...

:has-slotted, github.com/web-platform-tests/

westbrookwestbrook
2024-09-03

@kizu Caught an interesting bug here... seems that a parent with "transform" related styling will confused "position-anchor" resolution. πŸ›

issues.chromium.org/issues/364

If you'd love this to be fixed too, remember to add your "+1" to support Chromium Devs in understanding the priority of issues like these. πŸ™‡

westbrookwestbrook
2024-08-31

@davatron5000 Are yall seeing:

this.attachShadow({
mode: "open",
referenceTarget: "real-input",
});

Work directly? I'm only able to achieve the relationship with:

this.shadowRoot.referenceTarget = 'real-input';

😒

westbrookwestbrook
2024-08-28

@Jamessw Issue, in case anyone following along is interested, can be found here: issues.chromium.org/issues/362

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst