| GitHub | https://github.com/jakearchibald |
| GitHub | https://github.com/jakearchibald |
RE: https://mastodon.social/@firefoxwebdevs/116675240344077453
The name of these diagrams gives me equal parts pride and embarrassment.
We're experimenting with a way to visualize session history in Firefox DevTools, and we'd love your feedback!
Here's the background, and how to try it: https://blog.farre.se/posts/2026/06/01/session-history-diagrams/
Yesssss @bramus got the fix merged into Chrome 149, which rolls out next week.
The bug's still there if you have a passive "wheel" listener on any parent, but hopefully that's less common. https://issues.chromium.org/issues/516844151
Yesssss @bramus got the fix merged into Chrome 149, which rolls out next week.
The bug's still there if you have a passive "wheel" listener on any parent, but hopefully that's less common. https://issues.chromium.org/issues/516844151
The 'fixed' behaviour in Chrome 150 is screwy too:
Default: mouse wheel doesn't change the input value. Allows scrolling.
If there's a non-passive 'wheel' listener on any parent: wheel does change the value. Prevents scrolling.
If there's a passive listener: The bug returns.
Watch out! Chrome has a huge bug with <input type="number"> which causes values to change unexpectedly.
It's fixed in Chrome 150, but that won't land until the end of June.
Which of the following CSS features would you prefer Firefox to support first?
(note that we already support the quirky -webkit-line-clamp)