5 ms·
This website almost crashed my m1 macbook pro (renders at 1 fps or something), so I guess point taken: rendering text is not simple!
by krstffr 11mo ago
This website almost crashed my m1 macbook pro (renders at 1 fps or something), so I guess point taken: rendering text is not simple!
- dist-epoch 11mo agoAnd on my desktop, scrolling this page is painfully slow. Author: frontend technical lead, setting high code standards
- eviks 11mo agowhat's worse is that scrolling doesn't actually work unless you have the text area focused/under the wheel... very weird. Which is even worse for PgUp/Down as who would think to focus the area first for scrolling???
- doodpants 11mo ago> who would think to focus the area first for scrolling??? Sadly, this problem is common enough that click-before-keyboard-scrolling has become second nature for me.
- coxley 11mo ago> Author: frontend technical lead, setting high code standards Haha, to be fair it's common to half-ass personal projects even if it's your primary domain.
- wmanley 11mo agoLooks like it's caused by `backdrop-filter: blur(6px);` on `.menu-content`. After disabling that it's slow, but not that slow. Edit: This is with Firefox 144 on Ubuntu 22.04
- wmanley 11mo agoIt's also perfectly responsive if you disable JavaScript. Maybe something related to the --positionX and --positionY CSS variables that are updated on every mouse move?
- wmanley 11mo agoNo, actually the biggest difference is removing the `filter` property from the `.wave2` class which is used for rendering the background. With that removed the page is responsive even with the backdrop-filter - and it makes no visual difference AFAICS.
- deejayy 11mo agoThanks folks for all the suggestions, I've rewritten the whole page :)
- jeffbee 11mo agoWith what browser? Seems fine with Chrome.