Normally, we all agree that Firefox is the best thing ever. Well, maybe not the best thing ever, but the best thing that won’t get you locked up or punched in the face by your significant other for suggesting. That’s never happened to you? Your loss…
However, a series of unfortunate events today brought to my attention two obscure bugs in Firefox:
- Firefox has a buffer limit with xml content nodes of 4096 characters. After that, it magically splits what you are expecting to be one xmlNode into two or more. Ben Dowling explains the whole thing better and in more detail. The mozilla ticket is here.
- Firefox will cut off a fieldset that extends past the printing page’s boundaries. This means that if you have a large / huge
in a webpage, when you go to print it in Firefox, you will see one page of the fields then blank pages after. The full mozilla bug description is
- If you’ve never done a search on the bugzilla.mozilla.org system, you should. It will brighten your day.
Both of these bugs are several years old, and kind of striking. I imagine the xmlNode issue is buried pretty deep in the logic engine of Firefox, but seriously a two-year old printing bug? Says the guy who doesn’t own a printer … pseudo-outrage is awesome.