News for hackers. Stuff that matters.

A comment on 300ms Faster: Reducing Wikipedia's Total Blocking Time. Parent comment

Re:300ms Faster: Reducing Wikipedia's Total Blocking Time by Mystery-Machine on Monday May 29, 2023 @10:36AM (#36114421)
"Better interactivity" is subjective. You could argue that faster is better. Expanding and collapsing sections can be achieved faster and with zero JavaScript (which also makes it work on browsers with disabled JS) with a hidden input[type="checkbox"]. Aa for the media viewer, it could be a great exercise to try and make it in a similar manner with input[type="checkbox"] for opening/closing media viewer and input[type="radio"] for switching to prev/next image. This one probably requires browsers to support the `:has` CSS selector.

Also, if you want to further speed up your site, just like you said, the fastest way to speed up the site is to delete JavaScript, get rid of jQuery.

[ Parent | on HN ]
Re:300ms Faster: Reducing Wikipedia's Total Blocking Time by 6510 on Monday May 29, 2023 @10:46AM (#36114511)
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/de...

<details> is completely supported.

[ Parent | on HN ]
Re:300ms Faster: Reducing Wikipedia's Total Blocking Time by toast0 on Monday May 29, 2023 @12:33PM (#36115459)
Oooh, that's lovely. I have a page with ~50 lines of javascript to do this, and it looks like I can make it zero lines of javascript instead.
[ Parent | on HN ]
Re:300ms Faster: Reducing Wikipedia's Total Blocking Time by 6510 on Monday May 29, 2023 @12:53PM (#36115649)
One could use js to push the state into the url.
[ Parent | on HN ]
Re:300ms Faster: Reducing Wikipedia's Total Blocking Time by toast0 on Monday May 29, 2023 @12:58PM (#36115698)
It's just opening and closing detail panes (personal recipie site), there's no reason to put the open/closed state in the url.

But if I can do it with all html, that's better than a function to add / remove a css class and document.onclick = a function to find which recipie you clicked on and adjust the css class.

[ Parent | on HN ]
Re:300ms Faster: Reducing Wikipedia's Total Blocking Time by 6510 on Monday May 29, 2023 @02:16PM (#36116462)
Probably more useful for a nested menu. The default thing almost works out of the box. You need some css to set a proper cursor and style the clickable text properly.
[ Parent | on HN ]
Re:300ms Faster: Reducing Wikipedia's Total Blocking Time by janpio on Monday May 29, 2023 @10:47AM (#36114525)
You are not wrong.

I assume the author of the blog post just wanted to optimize the current situation, not completely change how these features work (which would most probably be a much more elaborate change).

Same for dropping jQuery - that will probably be a few weeks or months of work in a codebase the size of Wikipedia/Mediawiki.

[ Parent | on HN ]
Re:300ms Faster: Reducing Wikipedia's Total Blocking Time by robertoandred on Monday May 29, 2023 @09:39PM (#36120256)
Using inputs like that is incorrect in terms of accessibility.
[ Parent | on HN ]