Erotic web browser fan-fiction.
In an effort to pivot this site into a full on graphic design side business after 2 blog posts about logos in a row (hit me up exclusivly on FB to request a consultation), I thought I would reveal my new, new logo for the W3C. It turns out they recently launched a new one, but some folks don’t love it . As an artist, it’s not my job to critique other art, but instead to offer my own compelling…
Note from the future (Oct 20, 2025): I just opened my editor and found this half-written draft. Might as well publish it. It’s a bit awkward that I haven’t blogged in some 19 months so, as owner and author of the best blog about broken websites on the internet. I guess I’ve been busy, or lacking motivation to write, or perhaps both. Who can really say. But this morning I was just sitting at a…
If you happen to be using Firefox Beta 109 on an overpriced MacBook Pro that has a sticky letter s today (the 29th of December, 2022), this is what the User-Agent string looks like: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/109.0 And as of last week , the UA string in Firefox for versions 110 and higher looks like so: Mozilla/5.0 (Macintosh; Intel Mac OS X…
Over the weekend frontend-firebrand Alex Russell tweeted that it’s confusing these days to know how to get the major version of a Chromium browser, either via the User-Agent header (given User-Agent Reduction ), or from User-Agent Client Hints . (btw, I asked DALLE2 Alex’s question “Can you make hide or hare of this?”, and yeah, it mostly can.) Before I spend any energy improving the docs ( thanks…
If you somehow found this blog post because you googled or binged “site not working Chrome 100”, well, congrats my SEO trap worked successfully. Also, don’t panic. The quickest way to test if your site is broken due to a 3-digit version parsing bug is to temporarily enable the chrome://flags/#force-major-version-to-minor flag and restart the browser. This will change the version that Chrome…
In my last post on testing Chrome version 100 , I encouraged everyone to flip on that flag and report bugs. It’s with a heavy heart that I announce that Ian Kilpatrick did so, and found a bug . (⌣_⌣”) The predictable bug is that parks.smcgov.org will tell you your browser is out of date, and recommend that you upgrade it via a modal straight out of the year 2009. (Full Disclosure: I added the…
Great news readers, my self-imposed 6 month cooldown on writing amazing blog posts has expired. My pal Ali just added a flag to Chromium to allow you to test sites while sending a User-Agent string that claims to be version 100 (should be in version 96+, that’s in the latest Canary if you download or update today): I’ll be lazy and let Karl Dubost do the explaining of the why, in his post “Get…
Last week my pal Karl sent me a link to web-bug 67866 : which has the cool title “menu buttons don’t work in Firefox version 100”. It turns out that Mozilla’s Chris Peterson has been surfing the web with a spoofed UA string reporting version 100 to see what happens (because he knows the web can be a hot mess, and that history is bound to repeat itself ). The best part of the report, IMHO, is…
The other day I was reading Firefox’s CookieService.cpp to figure out how Firefox determines its maximum cookie size (more on that one day, maybe) when the following comment (from 2002, according to blame) caught my eye: The following test is part of the RFC2109 spec. Loosely speaking, it says that a site cannot set a cookie for a path that it is not on. See bug 155083. However this patch broke…
I thought I would document how I do branching in git because it’s clearly the best a perfectly acceptable way to do it, especially if you use GitHub. Step 1: git checkout -b <bug-number>/<rev> (That’s it.) <bug-number> maps to the GitHub (or Bugzilla, or Chromium, or Roblox customer support, etc.) issue number. <rev> is an integer, and maybe 99% of the time it’s just 1 for me. But if, for whatever…