Source code is available on my GitHub, I will update it regularly and I hope to be able to port make it work with xoram.dev once I'm done with the prototyping phase.
github.com/Ragnar-Oock/...

an in FF it's basically the same (I don't think the difference is significant here)

And regarding attending, I'll be at work at that time so no can do sadly.

I'll take that as a no then 😆

so... is there anything about the grid shorthand in it 👀
(no I'll never stop xD)

I use cropped Fullscreen capture when I stream, i feel like it's a lot more versatile than anything else I tried. It would be nice to be able to lock the crop to the size of a given window (so stuff displayed on top would still show) but it never bothered me enough to warrant a fix.

I have a setup like this on my G9 using PowerToys FancyZones. I have it set up with 4 8:9 zones, and fancy zones allow you to snap a window into multiple adjacent zones. So I can have 2 "full-width" windows or a centered full-width surrounded by "half-width" ones with no configuration change.

I personally don't have any issue with IDREFs that would warrant any changes to the spec and seeing valuable contributor time being potentially wasted on it is worrying.

... if this is the element we're looking for".
When the complexity of DOM element linking is not straight up dismissed on the ground of being annoying :/

I just gave a quick read to that GitHub discussion and I understand why you're worried. To me the whole discussion starts from the flawed assumption that IDREFs are at fault but all the propositions I found in the discussion trade the "it's hard to have a unique id value" with "we aren't sure...

- what I like about them? Meh... They're alright...

- what design constraints [...] ? Nothing comes to mind.
- What is the user impact [...] ? From what? Things work ok currently when you stop 5s to think about how to make something work with tools with a good DX like Vue or Svelte.

- For the times I had issues with making something accessible the issue always stemmed from a poor understanding of either the html attributes or aria attributes uses. Never from the IDREF itself.

For example which element should have which attribute (can't remember which one it was sarry)

Vue has useId that guarantees equality between frontend and backend and can be used to get a random opaque value to set as the id where needed.

- I never found myself in a case where a random uuid or a framework provided tool didn't solve the issue.

But I can remember only a single time it made things a bit challenging to do when I was working on a menu and menuitem abstraction layer in Vue.

- Usually when I need to get an id I either use a random uuid in js or a framework provided helper when doing stuff from the backend.

- The only pain point I can think of is not really one honestly, it's the whole page uniqueness. That's a bit tricky to satisfy in some rare situations because the different elements linked by the IDREF are not in the same component.

I use whichever syntax the tool I used to pick the color supports so C... So that means there can be more than one syntax used in the same file.
But if I have to type it out i do comas, with deg and percents.

That, or the fact that people who just didn't care/knew about it last year tried them since then.