[RESOLVED] jQuery parameters break HTML validator? Is there a workaround I don't know about?

dalecosp

I've got this in the HTML output of my page:

<script type="text/javascript">
jQuery(document).ready(function($) {
$('#prod_img').bjqs({
'height' : 350,
'width' : 350,
'nexttext' : "<img style='position:relative;left:25px;' src='/images/buttons/btn_pop_next.gif' alt='next' />",
'prevtext' : "<img style='position:relative;left:-25px;' src='/images/buttons/btn_pop_previous.gif' alt='previous' />",
'showmarkers' : false,
'responsive' : true
});
});
</script>

The good ol' Validator says I can't have IMG tags here. Nor does putting a "<div>" before/after help.

I'm not even sure what to Google for this ... it could be simply because it's after 4PM here 😃

Thoughts? Do I care if the validator craps out only for this one?

bradgrafelman

Out of curiosity... what happens to the validator if you surround the [FONT=Courier New]<script>..</script>[/FONT] block with [FONT=Courier New][/FONT] ?

Weedpacket

FWIW, I mocked up a page with that code in it (in the conventional right-before-the-</body>-tag position), and the page validated; in both HTML4.0.1 and HTML5 versions.

Bonesnap

Can you not put that code into an external script file and run it from there?

dalecosp

bradgrafelman;11025225 wrote:
Out of curiosity... what happens to the validator if you surround the [FONT=Courier New]<script>..</script>[/FONT] block with [FONT=Courier New][/FONT] ?

There we go. So now we know ... the W3C Validator is the stereotypical "Dumb" browser we all read about....

Weedpacket;11025239 wrote:
FWIW, I mocked up a page with that code in it (in the conventional right-before-the-</body>-tag position), and the page validated; in both HTML4.0.1 and HTML5 versions.

I've got the script inside the body, but IIRC it complained in the head position too. Of course, I've got the code running in two different locations and I'm not 100% sure if they were staying in sync while I was playing at w3.org ...

Thanks for testing, though. :-) Looks like with Brad's reminder I'll be able to get it to validate tomorrow. I'd really like to have it deployed....

bradgrafelman

Any chance you could post the HTML or a link to it?

dalecosp

First off, it's fixed. I just did the comment wrapper as Brad suggested at first.

Weedpacket;11025239 wrote:
FWIW, I mocked up a page with that code in it (in the conventional right-before-the-</body>-tag position), and the page validated; in both HTML4.0.1 and HTML5 versions.

I didn't think about this when I first read your post, but I've got an XHTML 1.1 Doctype. Perhaps that's stricter?

Bonesnap;11025241 wrote:
Can you not put that code into an external script file and run it from there?

Another fine idea! Too bad I couldn't think of idea after yesterday's brain fry.

I'm sure if there was anyone else here @work that had the collective experience and knowledge that the PHPBuilder regulars do: 1] we'd have a top 1000 site, and 2] we couldn't afford payroll ;-)

bradgrafelman;11025269 wrote:
Any chance you could post the HTML or a link to it?

Hopefully, within a few days it will be the individual listing page at the site linked in my sig. ;-) I'm planning to serve it from a RAMdisk and see if we can kick our load issues in the tuchis for a good long while ....

Weedpacket

dalecosp wrote:
I didn't think about this when I first read your post, but I've got an XHTML 1.1 Doctype. Perhaps that's stricter?

Yes, being XML and all, and lacking special rules for the parsing (or otherwise) of the content of <script> tags. It would want the stuff it should be treating as verbatim to be inside [font=monospace]<![CDATA[ ... ]]>[/font] delimiters (better than commenting it out with [font=monospace][/font] because [font=monospace]--[/font] is invalid inside a comment - validation will fall over as soon as you decrement something).
Problem then of course is that the JavaScript parser would probably choke on the delimiters, so the delimiters would need commenting...

//<![CDATA[
...
//]]>

(Addendum: apparently this is the official position. See http://www.w3.org/TR/2002/REC-xhtml1-20020801/#h-4.8)