Opera oddity

liunx

Guest
Here's a mystery why is it that on <!-- m --><a class="postlink" href="http://www.kurtworkholding.co.uk/">http://www.kurtworkholding.co.uk/</a><!-- m --> and only the home page the background does not show in Opera. This is a mystery to me as the entire site runs on a PHP stucture (ie. index.php?page=) and the only page that is affected is the home page. I've done a validation check for HTML and CSS, and nothing shows up.

Any ideas?are you referring to the fading blue background to the left?
It appears identical for me in Opera 7.54, Firefox 1.07 and IE6.Dave check it in Opera 8.5.

Brollachan, try applying the background to html in addition to body.


Why tables for layout is stupid (<!-- m --><a class="postlink" href="http://www.hotdesign.com/seybold/index.html">http://www.hotdesign.com/seybold/index.html</a><!-- m -->)
Why avoiding tables (for layout) is important (<!-- m --><a class="postlink" href="http://davespicks.com/essays/notables.html">http://davespicks.com/essays/notables.html</a><!-- m -->)
<!-- m --><a class="postlink" href="http://www.workingwith.me.uk/tablefree/why/">http://www.workingwith.me.uk/tablefree/why/</a><!-- m -->
<!-- m --><a class="postlink" href="http://www.sitepoint.com/article/tables-vs-css/">http://www.sitepoint.com/article/tables-vs-css/</a><!-- m -->
<!-- m --><a class="postlink" href="http://www.phrogz.net/CSS/WhyTablesAreBadForLayout.html">http://www.phrogz.net/CSS/WhyTablesAreBadForLayout.html</a><!-- m -->
<!-- m --><a class="postlink" href="http://www.westciv.com/style_master/house/good_oil/dead_layout/No">http://www.westciv.com/style_master/hou ... _layout/No</a><!-- m --> apparent luck, yes it is Opera 8.5 that I'm checking the site in. I've noticed that when loading the background briefly appears before the white appears to cover it up.

I have now found a fix for the problem and that was on the main index.php file in <tr> to change it to <tr style="background:transparent;"> which seems to have got it working. Though it's still odd why this problem only occured on one page and not the entire site as this change was on the main template.
 
Back
Top