@jensimmons@front-end.social3 even more:
1 Please add a button to invoke the responsive design mode to the ui. The keyboard shortcut alone is to "hidden" in my opinion.
2 Make the invokation of the bottom half console view more easy, when eg. in the elements tab. Currently one has to type something in the single visible repl line to open the lower console view.
3 Please improve the javascript error messages. There are still plenty javascript syntax errors that do not show up in the console at all.

@jensimmons

- add support for `overflow-anchor`
- support for `:has-slotted`
- a API for DOM templating
- focus groups
- Reference Target API
- elementInternals.type
- Platform based windowing/virtualization
- Declarative Partial Updates https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ShadowDOM/explainer.md
- CSS Anchor position is coming and is SOOO exciting
- commandfor
- [popover=hint]

#webDev#thanksWebkit

An employee of Cook/Jobs, @jensimmons, asks on a copylefted platform what she can do improve #WebKit.

The answer is simple: Comply with the LGPLv2.1. Participate with upstream projects rather than manipulating them so you can control them.

Employees of your company used to be forbidden from talking to FOSS communities. You've spent decades working against copyleft. But you now follow Microsoft's plan to “embrace, extend, & extinguish” #FOSS.

We see the game is afoot. Don't underestimate us.

@jensimmons performance improvements would be the number one by a mile.
I can not scroll PRs on GitHub when they get long. And I don’t just mean that aren’t smooth. I mean it literally can not be done because it renders so slowly. And that’s on a M3 Max chip 😬
Yeah yeah, probably GitHub could and should improve the performance of the site too, but it scrolls butter smooth in other browsers.