Don't remember why I was subscribed to the bug, must have commented on it or something. Got the occasional email notification about it over the years, always got a chuckle out of it. Then a couple of days ago, lo and behold, it was fixed!
Don't remember why I was subscribed to the bug, must have commented on it or something. Got the occasional email notification about it over the years, always got a chuckle out of it. Then a couple of days ago, lo and behold, it was fixed!
I've learned not to bother submitting bug reports unless I can guarantee that my time will not be wasted. If I find a bug in a project that doesn t guarantee this, I either fix it privately for myself or switch to another project.
Closing issues automatically. What a demented idea.
And so often there’s the added gaslighting of a project that provides some rationale for closing but then inexplicably locks too as if that’s the same.
It still turns up in search and you can comment on it (some even reopen automatically if you do).
Locking automatically is just the worst - we don’t care, we won’t care, and you’ll never get us to care.
It’s worth pointing out that this bug fix doesn’t actually do that. For a start, it’s a preference that can be toggled on by the user or an extension, rather than a default thing that websites can choose. Probably for the best: it’d certainly open up new avenues for clickjacking.
Mozilla Suite rather than Netscape Navigator. This is from 2000 which was well into the Mozilla era and I don't think that Netscape bugs made it into Bugzilla anyway.