Just remembered my all-time favourite bug, where Android accidentally rendered the name of the "Grunt" tool on its webpage as "Dorkq" https://github.com/gruntjs/gruntjs.com/issues/81
Home page shows the project title as "dorkq" on some Android devices · Issue #81 · gruntjs/gruntjs.com

See here: http://www.browserstack.com/screenshots/2308d26f99f0b5915b53829c4ae5f9567b2d84be I haven't tried to figure out why. @practicum noticed that the letters are all 3 off and lowercase. G-3=d,...

GitHub
@misty okay but...how??
@Drunkonhugs It was a bug in Java's font code. When a font is rebuilt/replaced/updated, the cache wasn't also rebuilt, leading to a glyph table that no longer represents the actual font being rendered.
@misty you’d think text on a page would be simple
@misty What
@d Apparently it was a Java bug - it wasn't busting the cache for its character-to-glyph map if the font gets updated/refreshed/replaced. So you get a little caesar cipher effect if a font gets loaded just the right way
@misty someone make dorkq a real thing
dorkq

The JavaScript Task Runner. Latest version: 1.0.0, last published: 10 years ago. Start using dorkq in your project by running `npm i dorkq`. There are no other projects in the npm registry using dorkq.

npm
@misty How uh, did that happen?
@kira My understanding is it's a Java bug; it didn't update the cached map between characters and glyphs if a font was updated somehow, leading to that map getting out of date.
@misty thank you for explaining!
@misty @whalecoiner oh my god i can’t believe this is almost TEN YEARS OLD
@misty wow, this is incredible. Hadn't heard of this before, but this is one for the books.
@misty ...how does this happen lmao

@misty

> The issue is
> -webkit-text-stroke: 4px;

Ehm what?!?

@agowa338 @misty The root issue was a font caching one (the font had been updated, the cache hadn't) , so presumably this CSS affected it because if you changed how the text was rendered, it no longer used the old cache
@foone @agowa338 @misty Ohhhhh. that makes much more sense.
@misty truly the funniest bug to have ever happened