136 things every web developer should know before they burn out and turn to landscape painting or nude modelling


A slightly tongue-in-cheek list of the things I’ve learned about web dev over the past 23 years. 🙂

@schnittchen Yeah, I know. It however doesn’t crash Firefox mobile on ChromeOS so I need to dig up one of my old Android test phones to figure out why. (I need to figure out where I packed them during my move.)

I’m guessing it has something to do with the web font (the page has no JS and the CSS is fairly commonplace) but the typeface is only supposed to be loaded if the browser supports its features.

@schnittchen It isn’t the typeface or the CSS as other blog posts from the site load correctly in Firefox Mobile on Android. And it seems to be ARM related. Firefox Mobile on ARM crashes. Doesn’t crash on ChromeOS Intel. Firefox on macOS Intel works fine but Firefox on macOS M1 crashes.

Literally, something about the HTML of that one blog post is crashing Firefox *only* on ARM. 🤨

@baldur @schnittchen
Additional info: Firefox mobile 84.1.1 (Build #2015781795) works fine. Tested in public and private browsing, both times with uBlock Origin enabled.

I'm not too sure about the "download typefaces" setting, I remember disabling that in FF60 or s.th. like that, but cannot determine whether it's still active, as all my settings seemed to be gone after FF published a major UI overhaul and now that option is gone from the UI.
Please check font in screenshot.

@anathem @schnittchen That looks like the right typeface.

I also discovered that Firefox Nightly on Android works fine. But it crashes in Firefox mobile 88.1.2. So this looks like a regression that has been fixed in an upcoming version


@baldur @anathem @schnittchen I can't believe three different people are using Firefox on Android. I thought I was the only one 🤣

· · Web · 1 · 1 · 2

@pkra @baldur @anathem @schnittchen It also crashes FF on Linux 🤷

Fans did spin up briefly. Log has this before it dumped core:

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Attempting to create a render task of size 812x19719

@bekopharm @baldur @schnittchen Oooh... that looks like FF needs to learn to split rendering of a looong <ol> into chunks. It probably produces one render context for that whole list, then tripping over its own memory limits. ^^

Funny, that problem was way worse in Chrome mobile, back when I still used that.

@bekopharm @baldur @anathem @schnittchen fwiw, it was fine for me on Linux. Not that that says much.

But really: look at Baldur breaking the web so casually. Tsk tsk tsk. 🙃

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!