Elliott C. Back: In Aere Aedificare

There are times I wish it were either just IE or Firefox in circulation, and not both. And these are days when I run into differences in the rendering engines of those browsers. Right now my single pages render fine in IE, validate, but show a break in Firefox between the header and the little header-bit. The menu-bar is also 1-pixel off in Firefox, which is extremely annoying. Take a look at these illustrations:

I suppose I should fix this sometime…. sigh…

10 Responses to 'Why I wish there were 1 browser'

1. Zeke said:

   on December 31st, 2004 at 4:10 am

   The background not stretching in Firefox on single pages is annoying too

2. Shaun said:

   on January 2nd, 2005 at 10:09 pm

   IF only IE rendered CSS/XHTML to standards, hey?

3. K. Restoule said:

   on January 3rd, 2005 at 2:41 pm

   The deal is that its Microsoft’s fault (Yeah its easy to blame Microsoft but I’m serious) IE is designed to be “forgiving” for html errors while other browsers like Firefox, Modzilla, Safari, Netscape, and Avant are not. As well, Microsoft likes “reinvent things” by creating HTML code that will work on IE but no other browser.

   That is my geek rant for the day

4. Elliott Back said:

   on January 3rd, 2005 at 4:39 pm

   Well, K. I have to agree with your factual statements! Microsoft has designed its browser to render incorrect HTML and guess about correct structure, and introduce its own propietary features. However, this comes out of the old browser wars where having a browser that would render almost anything as if it were correct helped. Then every idiots web page looked right through IE. See, it’s hard to tell a consumer that the reason the web page looks wrong is because the author didn’t adhere to proper design standards. No. The first thing your average user will do is blame the browser.

   But, we’re passed all that, and we’d like standards compliance now…

5. K. Restoule said:

   on January 3rd, 2005 at 8:46 pm

   Tell the to Microsoft. They’re constantly trying to “reinvent the wheel”

6. don’t worry said:

   on January 6th, 2005 at 5:47 pm

   Doesn’t look like it validates to me

7. Denis said:

   on January 14th, 2005 at 2:47 pm

   IF only IE rendered CSS/XHTML to standards, hey?

   As fas as I tried, Firefox 1.0, despite its endorsement of css, is not css-1 compliant.

   Consider the following:

   blah

   It is perfectly valid xhtml and css.

   According to the w3c specs regarding the dom’s box model, you should get a text area within a division that has a 30px padding and a 1px black border. You get precicely that in IE. In Firefox 1.0, on the other hand, the text area is properly positionned, but has the division’s width rather than 60px less.

   Similarly, consider:

   blah

   IE renders an outset border. Firefox, on the other hand, renders this as a solid border.

   My $.02 as a Firefox user.

8. Denis said:

   on January 14th, 2005 at 2:50 pm

   Silly html stripping… It you should read:

   div style=”border: solid 1px black; padding: 30px;”
   textarea style=”width: 100%”
   (…)

   and:

   table style=”border: outset 1px”
   tr
   td
   (…)

   respectively

9. New Jersey Web Design said:

   on January 20th, 2006 at 10:02 am

   Oh how I agree……As a web designer, I have to test on multiple browsers to make sure that all elements on the page are displayed properly across multiple browser platforms. I constantly notice that IE can “figure” out the code’s intentions and properly display the image or element correctly. However, on the other hand, FireFox has a tough time parsing the code and translating it correctly on the screen, especially if there are errors in the code. Typical errors that affect the browsers are open tags, and erroneous code. I also recommend validating your code here: validator.w3.org/

10. ghfghfgh said:

    on December 21st, 2006 at 6:16 pm

    gdfhjxfygjkgygh

Leave a Reply

Name (required)

Mail (will not be published) (required)

Website

Powered by WP Hashcash

Fresh, related resources: