Call me picky, but…
I sometimes wonder why different browsers see HTML, CSS and JavaScript in different ways. It frequently makes my life that much more interesting as a web developer. What works in one browser, won’t work, or won’t even exist in another one. Luckily, these aren’t usually large issues.
One of those peculiar discrepancies is the margin and padding of the paragraph and header tags. In IE there is no difference between using margin and padding for the spacing between paragraphs (and in Firefox, for the most part, there isn’t a difference there either). However, the interesting thing happens when the div containing the paragraph or header has a background. Firefox makes margins tear large holes in the background, forming unsightly gaps in the website layout that shouldn’t otherwise be there. That was the most interesting bug so far, since Firefox doesn’t usually have such issues. The only fix for this problem was to set margins to nothing, and use padding instead.
Also, you might know about the infamous line break bug in IE… Where IE reads the file’s line feed and carriage returns and uses them to make gaps in certain places on web pages (which is quite odd since all browsers are supposed to ignore whitespace altogether – the only thing they’re supposed to do with it is make single space between words in the content of the page). If you’ve used tables with cells that contain images, you’ll know what I mean (actually, you’ll only see this happen if the closing table data tag is on another line than its content).
I find it quite interesting to have found a bug in Firefox, as I’m sure most geeks know that Firefox is supposed to be standards compliant. And I’m calling it a bug because a margin isn’t supposed to mess up the background of its container div. Because if that was part of the standard, I would say it’s really weird.
I’m finished my rant (many of you may be exhaling in relief at this very moment). Thank you for your time. You may continue your regularly scheduled day.