Nathan Knowler

@knowler.dev

Building web stuff and design systems. Focused on accessibility, progressive enhancement, and web components. At the intersection of CSS and the Shadow DOM. he/him Métis/settler Treaty 1/wpg https://knowler.dev https://sunny.garden/@knowler

love the react native effect: rotated my device or resized my browser and lost the current state (watching an embedded video in a feed; trying to log in; was unauthenticated)

If I made a rich text editor, I would make it impossible to use empty paragraphs or line breaks to space out paragraphs. In other words, I still have undealt with trauma from Wordpress.

I want the reduced white point accessibility feature on my macbook so bad. I know I can do it with colour profiles, but like just give me a control center slider.

wish: in GH’s blame view, the blamed commit should be sticky in the column so I don’t have to scroll up endlessly, inevitably passing it.

*starts drafting a blog post* Me: ”I wonder if I should use the new CodePen 2.0 editor for this example even though it’s still beta?” *2 hours later* CodePen: “CodePen 2.0 is here!”

There are a lot of valuable web features that get opposed because of fingerprinting concerns. Security is important, but this situation is stunting the potential of the web. Is there a better way to allow users to trust a web site/web app that can get us over this hurdle?

I love that we have focusgroup in Chrome… but again similar to invoker commands… there’s no good way to use it as a progressive enhancement without JS for feature detection.

I’ve said this before, but HTML includes will inherently disappoint a number of folks who are excited for them… especially folks who want to just Use The Platform™ rather than frameworks.

Kind of bizarre: the button within `<legend>` does not become `disabled` from the `<fieldset>`. ```html <fieldset disabled> <legend><button type=button>Review</button></legend> <button>Submit</button> </fieldset> ```

I’ve consistently had this issue in Chrome’s devtools where on reloading the page it’s inspecting switches to a “warmup.html (prerender)”