Groups > Browsers > Opera Browser Technical topics > Re: Opera doesn't like something about vBulletin or is it simply their bad programming?




Opera doesn't like something about vBulletin or is it simply
their bad programming?

Opera doesn't like something about vBulletin or is it simply their bad programming?
Tue, 13 Nov 2007 13:14:07 -080
Since one of my favorite sites (svrider.com) moved from SMF to vBulletin,  
it's nearly unusable in Opera.

Every time I load a page, I see, in the status area, Images: X-3 / X and  
that's the end. That is, it loads 3 fewer images than requested then waits  
forever or until I push the X (stop loading) button, whichever comes  
first. ;)

Works fine with Internet Exploder 7 but jeez! who wants to use THAT?   
Haven't tried FF.  Is there an Opera tweak that might help?  I did set to  
identify as IE, no change.  Maybe someone could tell me a fix I can pass  
along to svrider.com?

WinXP MCE, java  1.60_03.

Below is from http://validator.w3.org/check#
--------------------------------------------

  Line 2, Column 1: Missing xmlns attribute for element html. The value  
should be: http://www.w3.org/1999/xhtml.
<html dir="ltr" lang="en">

Many Document Types based on XML need a mandatory xmlns="" on the root
 
element. For example, the root element for XHTML will look like:
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"
lang="en">
  Line 359, Column 19: there is no attribute "background".
     <td background="images/dark_vb/misc/header_repeat.gif"
width="100%"  
height="

You have used the attribute named above in your document, but the document  
type you are using does not support that attribute for this element. This  
error is often caused by incorrect use of the "Strict" document type
with  
a document that uses frames (e.g. you must use the "Transitional"
document  
type to get the "target" attribute), or by using vendor proprietary  
extensions such as "marginheight" (this is usually fixed by using CSS
to  
achieve the desired effect instead).

This error may also result if the element itself is not supported in the  
document type you are using, as an undefined element will have no  
supported attributes; in this case, see the element-undefined error  
message for further information.

How to fix: check the spelling and case of the element and attribute,  
(Remember XHTML is all lower-case) and/or check that they are both allowed  
in the chosen document type, and/or use CSS instead of this attribute. If  
you received this error when using the <embed> element to incorporate  
flash media in a Web page, see the FAQ item on valid flash.
  Line 364, Column 345: end tag for "img" omitted, but OMITTAG NO was 

specified.
?' title='TEchSpec-USA' border='0'></a><div id="beacon_6"
style="position:  
abs

?

You may have neglected to close an element, or perhaps you meant to  
"self-close" an element, that is, ending it with "/>"
instead of ">".
  Line 364, Column 168: start tag was here.
?ww.techspec-usa.com' target='_blank'><img  
src='http://ads.svrider.com/adimage
  Line 364, Column 662: end tag for "img" omitted, but OMITTAG NO was 

specified.
?tyle='width: 0px; height: 0px;'></div><!-- END ad 96495895 -->

?

You may have neglected to close an element, or perhaps you meant to  
"self-close" an element, that is, ending it with "/>"
instead of ">".
  Line 364, Column 434: start tag was here.
? 0px; top: 0px; visibility: hidden;"><img  
src='http://ads.svrider.com/adlog.p
  Line 1565, Column 85: end tag for "br" omitted, but OMITTAG NO was 

specified.
?completegfx.com/">CompleteGFX</a><br>

?

You may have neglected to close an element, or perhaps you meant to  
"self-close" an element, that is, ending it with "/>"
instead of ">".
  Line 1565, Column 81: start tag was here.
?www.completegfx.com/">CompleteGFX</a><br>
  Line 1578, Column 6: end tag for "td" omitted, but OMITTAG NO was  
specified.
</form>

?

You may have neglected to close an element, or perhaps you meant to  
"self-close" an element, that is, ending it with "/>"
instead of ">".
  Line 1561, Column 0: start tag was here.
<td>
  Line 1578, Column 6: end tag for "tr" omitted, but OMITTAG NO was  
specified.
</form>

?

You may have neglected to close an element, or perhaps you meant to  
"self-close" an element, that is, ending it with "/>"
instead of ">".
  Line 1560, Column 0: start tag was here.
<tr>
  Line 1578, Column 6: end tag for "table" omitted, but OMITTAG NO was
 
specified.
</form>

You may have neglected to close an element, or perhaps you meant to  
"self-close" an element, that is, ending it with "/>"
instead of ">".
  Line 1559, Column 0: start tag was here.
<table cellpadding="6" cellspacing="0"
border="0" width="100%"  
class="page" alig
  Line 1579, Column 4: end tag for element "td" which is not open.
</td>

The Validator found an end tag for the above element, but that element is  
not currently open. This is often caused by a leftover end tag from an  
element that was removed during editing, or by an implicitly closed  
element (if you have an error related to an element being used where it is  
not allowed, this is almost certainly the case). In the latter case this  
error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should  
probably read this FAQ entry.
  Line 1580, Column 4: end tag for element "tr" which is not open.
</tr>

The Validator found an end tag for the above element, but that element is  
not currently open. This is often caused by a leftover end tag from an  
element that was removed during editing, or by an implicitly closed  
element (if you have an error related to an element being used where it is  
not allowed, this is almost certainly the case). In the latter case this  
error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should  
probably read this FAQ entry.
  Line 1581, Column 7: end tag for element "table" which is not open.
</table>

The Validator found an end tag for the above element, but that element is  
not currently open. This is often caused by a leftover end tag from an  
element that was removed during editing, or by an implicitly closed  
element (if you have an error related to an element being used where it is  
not allowed, this is almost certainly the case). In the latter case this  
error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should  
probably read this FAQ entry.
  Line 364, Column > 80: XML Parsing Error: Opening and ending tag  
mismatch: img line 364 and a.
?/ads.svrider.com/adclick.php?bannerid=6&amp;zoneid=1&amp;source=&am
p;dest=htt?

?
  Line 364, Column > 80: XML Parsing Error: Opening and ending tag  
mismatch: img line 364 and div.
?/ads.svrider.com/adclick.php?bannerid=6&amp;zoneid=1&amp;source=&am
p;dest=htt?

?
  Line 365, Column 6: XML Parsing Error: Opening and ending tag mismatch:  
div line 364 and td.
	</td>

?
  Line 366, Column 5: XML Parsing Error: Opening and ending tag mismatch: a  
line 364 and tr.
</tr>

?
  Line 367, Column 8: XML Parsing Error: Opening and ending tag mismatch:  
td line 363 and table.
</table>

?
  Line 1568, Column 7: XML Parsing Error: Opening and ending tag mismatch:  
br line 1565 and div.
	</div>

?
  Line 1578, Column 7: XML Parsing Error: Opening and ending tag mismatch:  
div line 1562 and form.
</form>

?
  Line 1620, Column 7: XML Parsing Error: Opening and ending tag mismatch:  
form line 1557 and body.
</body>

?
  Line 1621, Column 7: XML Parsing Error: Opening and ending tag mismatch:  
tr line 361 and html.
</html>

?
  Line 1621, Column 7: XML Parsing Error: Premature end of data in tag  
table line 357.
</html>

?
  Line 1621, Column 7: XML Parsing Error: Premature end of data in tag body  
line 353.
</html>

?
  Line 1621, Column 7: XML Parsing Error: Premature end of data in tag html  
line 2.
</html>

?




-- 
Post Reply
Re: Opera doesn't like something about vBulletin or is it simply their bad programming?
Tue, 13 Nov 2007 13:57:54 -080
On Tue, 13 Nov 2007 13:14:07 -0800, Peter Bradshaw <vmweenie98@yahoo.com> 

wrote:

Oops.  Opera 9.24.   So sorry.


> Since one of my favorite sites (svrider.com) moved from SMF to  
> vBulletin, it's nearly unusable in Opera.
[ blah blah blah]


Post Reply
Re: Opera doesn't like something about vBulletin or is it simply
Wed, 14 Nov 2007 16:32:13 +010
Op Tue, 13 Nov 2007 22:14:07 +0100 schreef Peter Bradshaw  
<vmweenie98@yahoo.com>:

> Since one of my favorite sites (svrider.com) moved from SMF to  
> vBulletin, it's nearly unusable in Opera.
>  Every time I load a page, I see, in the status area, Images: X-3 / X  
> and that's the end. That is, it loads 3 fewer images than requested then  
> waits forever or until I push the X (stop loading) button, whichever  
> comes first.

It seems to work fine here... Could there be some setting interfering? The  
'Block content' feature comes to mind.

-- 

                                                    Rijk van Geijtenbeek
                                  Opera Software ASA, Documentation & QA
Post Reply
Re: Opera doesn't like something about vBulletin or is it simply their bad programming?
Wed, 14 Nov 2007 19:55:24 +010
On Tue, 13 Nov 2007 13:14:07 -0800, Peter Bradshaw wrote:

> Since one of my favorite sites (svrider.com) moved from SMF to vBulletin, 

> it's nearly unusable in Opera.
> 
> Every time I load a page, I see, in the status area, Images: X-3 / X and  
> that's the end. That is, it loads 3 fewer images than requested then waits 

> forever or until I push the X (stop loading) button, whichever comes  
> first. ;)

   It works fine for me, but I've seen the same happen on
other pages. Perhaps Opera's cache gets confused depending
on the number of open pages and what not.

   By the way, are you sure that it loads to few images?
Sometimes, Opera counts more images than were requested:

  <http://luden.se/www/opera/heisenbugs/images/image-2of2.png>


Post Reply
about | contact