| 04:42 | <sideshowbarker> | Trying to get Ladybird to properly handle searchfox.org pages — including the ability to click to select lines and line ranges. |
| 04:42 | <sideshowbarker> | And finding myself a little surprised that a page like https://searchfox.org/firefox-main/source/modules/libpref/init/StaticPrefList.yaml#16955-16965 is 16MB. |
| 04:43 | <sideshowbarker> | …where the local file in my Firefox clone is 613K. |
| 04:43 | <sideshowbarker> | But I guess that’s probably a not-atypical case for something that’s got syntax highlighting added, and what-not. |
| 04:45 | <sideshowbarker> | However, to put things in perspective a bit: That 16MB is the same size as the single-page https://html.spec.whatwg.org/ HTML spec. |
| 04:46 | <sideshowbarker> | — which on the face of makes 16MB to show just one code file seem… a bit excessive |
| 04:46 | <sideshowbarker> | Or maybe it’s not, I dunno. |
| 04:49 | <sideshowbarker> | It’s just that, I actually use searchfox.org in Ladybird — for grabbing links to Firefox sources when I’m writing up Ladybird PR descriptions for PRs where the change includes something modeled on Firefox code. |
| 04:49 | <sideshowbarker> | And, I like to give reviewers links to the specific line numbers/ranges. |
| 04:50 | <sideshowbarker> | Ladybird anyway doesn’t yet have super-spectacular performance with large files. So I already didn’t exactly prefer trying to use the single-page HTML spec in LB. |
| 04:52 | <sideshowbarker> | But … to at least be able to click-link as expected to line numbers in searchfox.org pages — that doesn’t seem like it should need to require great performance on super-large files. |
| 04:53 | <sideshowbarker> | // end rant |
| 05:10 | <sideshowbarker> | in contrast, https://github.com/mozilla-firefox/firefox/blob/main/modules/libpref/init/StaticPrefList.yaml is actually pretty snappy in Ladybird — it loads relatively quick, and the linking-to-lines behavior is usable right way |
| 05:11 | sideshowbarker | goes back to finishing up the PR description which led him into this ranting detour |
| 07:53 | <annevk> | zcorpan: instead of posterfromimg, was it ever considered to use poster=""? It seems we already special case that state. |
| 07:56 | <zcorpan> | annevk: It doesn't allow using a fallback and makes feature-testing harder. But maybe it's better in the long term? |
| 07:58 | <annevk> | zcorpan: currentPoster enables the feature testing, no? So you could do the fallback based on that I suppose. posterfromimg seems very ungainly. |
| 08:00 | <zcorpan> | annevk: Yes. Just lacks a declarative way to do fallback, but that seems ok |
| 08:25 | <zcorpan> | Do people use the 'y' shortcut in specs for the commit snapshot link? It seems to me it could be activated by accident |
| 08:37 | <zcorpan> | See https://github.com/whatwg/whatwg.org/pull/507 |
| 09:46 | <zcorpan> | annevk: I think Noam's stack is ready now |
| 11:11 | <zcorpan> | How important is the font for https://html.spec.whatwg.org/#table-example-1 ? Thinking of yanking it and making it monospace to optimize perf |
| 11:20 | <Ms2ger> | Is very pretty though |
| 11:43 | <zcorpan> | https://github.com/whatwg/html/pull/12906 |
| 16:10 | <Noam Rosenthal> | had to rebase with the javascriptURLs commit, it's all resolved now |