> they're just not inclined to fix it in the current releaseNor in the next, or in the one after that. I wouldn't had said anything if they had planned to fix it in some near future, but right now it's just "Firefox134 - wontfix, Firefox135 - fix-opt...
Yes, sorry about that ranting yesterday, but it's still very annoying to see a arbitrary "wontfix--go lay an egg" on a regression issue. Regression = sloppy testing.Besides, what is this update mechanism I'm hearing about? Why doesn't it just check f...
☹️ firefox134 --- wontfix firefox135 --- fix-optionalAnd to add insult to injury, somebody in the bug thread claimed affected users should simply "know the dates of [Mozilla's] planned releases"!... No biggie.Sorry, but it's not ...
Same here (Linux Mint 21.3 "Virginia" (base: Ubuntu 22.04 "jammy")).Problem as described above, also started after (manually) updating to 134.0, and (manually) updating to 134.0.1 didn't fix it. I do have the same two, always returning, 0 byte files ...
