D1278-118 D1278-012 Living Rainforest img_1340 img_16924 img_14078 crw_6867.jpg img_1140 Living Rainforest img_18369 img_15645 crw_10231 green bubbles crw_0030 img_1442 img_16424 img_14097 IMG_0844 img_1312 Hursley Model Railway

@antonpiatek on twitter

Posting tweet...

Powered by Twitter Tools

Themes, css and why IE is a pain

So I have been working on the theme on my site and while I still have a few things to do (including editing TinyMCE to do proper quoting of text and of code as well as embedded gallery images) but feel it is much better. For a start it looks much better in Internet Explorer.

Internet explorer is a pain to work with for websites, especially its CSS processing. It makes up its own rules and does what it wants, so I have extra stylesheets for IE to make it do what firefox and opera do. Saying that, firefox is not perfect either, as I found it rendered some things wrong too whereas opera actually did what I expected. This is not to say that opera is the best at following standards as I had to add some extra stylesheets as it had a few glitches I could not figure out why.

It is a shame that browsers cannot actually follow standards properly (though I had some fun when I did not have the DOCTYPE as the first text in the page and the browsers then reverted to a non-standard renderer (as opposed to XHTML). That really had me confused for a while as the whole of the embedded gallery was showing with huge fonts.

Random Posts

1 comment to Themes, css and why IE is a pain

  • Shogun

    I feel your pain. My website creating productivity would double if it wasn’t for CSS issues between browsers!

    Bring back tables and frames! :-)

Leave a Reply

  

  

  

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="" highlight="">