My hilarious front-end bug: As a junior developer, I was implementing a slider with some fancy features - I'd completed my work of art and tested it thoroughly (or so I thought).

As I'm demonstrating this pièce de résistance of sliders, I switched to the tablet to show how it adapts to touch input.

After I've gone through all the features I slip with my finger and drag the handle a little too harshly... to my confusion, the drag handle had broken free of its confines and could now be moved anywhere one the page, all I could do is laugh, I'm glad my colleague found it equally amusing.

Also, the number of times I've seen bugs like No. 3 on big, live sites. Clearly a macbook monoculture and noone bothering to test on any other platforms. Seems like people forget scroll wheels are a thing too...

"Read the rest of this story with a free account." - extremely amusing.

I have to admit "The recurring nightmare" is no funny bug for me. It really took away nights of mine. First of all reproducing itself is a tough job locally. Added the patch of showing scroll all the time and UX designers were are not happy about that. Finally added a javascript code to put a check on that. And I hate that piece of code.

One hilarious front end bug is posting a blog to a platform that discourages reading the blog.

I have some of my interesting debugging stories piled up on my blog drafts. One of them was the issue "script not triggered when opened in a new tab". And indeed, there was a 3rd party script on our page that was triggered on every page (re)load, but not when opened in a new tab. I was baffled at first, but the reason was rather straightforward: the injected script was using an "if (!document.hidden)" check, which wasn't passing for background tabs.

in the world of front end dev always expect the unexpected. the amount of head-scratching moments i've had....lost count.

i think the worst and most frustrating type of "bug" (not really) - is the "reload - no update" issue. not sure if it has another name.

its when you make some change, reload the browser but the update is not reflected :D - usually very trivial but often times the straw that broke this camels back.

All these are classics:

Quirks mode. Unicode normalization. Scrollbar resize infinite loop. Accidental misparse. And of course another IE bug.

Each one has manifested a zillion times on as much different web sites. And yet they keep biting us.

Is there an effective way to restructure programming to make these disappear, without locking ourselves up in a turing tar pit. Linters, fault injectors, ... Or some rust safety equivalent for the front end?