for the very first time, mastodon's stock interface is starting to look like it was properly designed.

https://blog.joinmastodon.org/2026/10/5.0-a-closer-look/

`@private` variables may be coming to CSS, whoa!! https://drafts.csswg.org/css-mixins-1/#private

anchor positioning solves what would otherwise be major headaches. with two lines of code!

i wish the `focusgroup` proposal was even smaller in scope, focusing (heh) only on toolbar and menus, both of which are self-sufficient.

currently, `focusgroup` "supports" things like tablist and listbox, but requires manual scripting to actually use those patterns, making the proposal feel half baked.

"always provide text content or accessible text attributes for your `option` elements." – https://webkit.org/blog/18117/the-golden-rule-of-customizable-select/

this also applies to literally every other control but yea

TIL: "palpable content"

https://html.spec.whatwg.org/multipage/dom.html#palpable-content

this could become a common pattern to counter overly zealous use of `headingoffset`:

```
<h2 headingreset>Do not fuck with me</h2>
```

i do think it's best used in moderation.

instead of making everything h1, i would start at h2 in most places (unless of course it's literally a document), with `headingoffset` sprinkled more intentionally.

a page with a hundred h1s is nonsensical, but the same amount of h2s can still make sense.

RE: https://mastodon.social/@firefoxwebdevs/116680726980295049

i like that this feature encourages local thinking — as long as you can ensure that a portion of a page has correct hierarchy in isolation, `headingoffset` will allow it to fit into a larger outline.

i also really like that you can opt out a subtree using `headingreset`. this is the very first thing i went looking for. https://html.spec.whatwg.org/multipage/sections.html#attr-headingreset

normally i'm all for web tech, as it's the most pragmatic way to develop cross-platform apps. but Raycast is very unique piece of software where performance is critical.

it's still in beta, so some of this is to be expected and will surely improve. still, having used the native app, i've seen how good it could be. the ceiling is much higher with native.

trying the new Raycast beta, which they've rewritten using web tech.

already ran into a few cases of slowdown:
- it can silently swallow keystrokes if i open it and start typing right away.
- when waking from sleep (and on low battery?), it sometimes doesn't open until after a few seconds.

found `cursor: none` on a button today. that's a new one.

even with the "fix" in Chrome 150, i think the scroll behavior is unacceptable.

detecting the presence of a `wheel` event listener is such a weird way for opting in/out. not to mention that some frameworks also delegate all events by preemptively listening to every single event for you, no matter whether you need it in your own code.

RE: https://mastodon.social/@jaffathecake/116645867765357032

i despise `<input type=number>` with a passion. it's utterly broken!

this is what i use and recommend instead:

```
<input inputmode="numeric" pattern="[0-9]*">
```

(the `inputmode` attribute improves the experience for touchscreen keyboard users, and the `pattern` attribute helps with validation)

it pierces shadow boundaries automatically :0

normally, this would be really tricky to do in the author origin.

the implementation is actually interesting:

- it takes effect instantly as you're editing the CSS. this makes such a huge difference!

- it shows up as a "user agent" stylesheet, which is quite similar to if it was actually in the "user" origin defined in the css-cascade spec. this does mean it's weaker than author styles (unless combined with `!important`).

zen now supports user styles, which means i don't need a third-party extension anymore!

for the longest time, i've thought one of my life goals is to get to work on a browser someday.

not the browser engine, but all the UI that goes around it. browsers have largely remained stagnant over the years, barring a few recent innovations (vertical tabs, split view). there's so much room for making a nicer browser.

google is apparently speedrunning breaking every ethical web principle listed here: https://www.w3.org/TR/ethical-web-principles/

(it's a good read regardless)

i’ve already spent more time on this than i would like. i hate talking about these tools (which normalizes them).

there is nothing in it for me. i don’t want to talk about any of this shit. i’m not getting paid, and none of it is useful in my own work in any meaningful way.

but i've taken the time to properly understand these systems because i think it's important to stay informed. hopefully this thread was helpful for anyone who’s curious about this whole thing.

/fin.