Comment 32 for bug 1914584

> So I'm not really clear what's going on here.

That's the problem, and why I suggested a new bug should be opened for this bug; it was marked fix-released but never actually fix-released, and then it was going to be re-used by manually changing from fix-released back to new and then go thru the process again. Not confusing at all right? ;-)

I had to re-read the bug 4-5 times to finally understand that the bug was initially incorrectly marked fix-released in comment 20 and comment 21, when in fact the incorrect fix never actually made it to -updates, but then again was incorrectly marked fix-released in comment 23 and comment 24, still without the incorrect (or correct) fix ever making it into -updates, and then was about to be 'fixed' yet a 3rd time with an actual fix.