which flag to stop <noscript> errors

For technical support for all editions of CSE HTML Validator. Includes bug reports.

which flag to stop <noscript> errors

Postby jscar » Wed Nov 23, 2011 8:48 am

Hi
our CMS is putting the following noscript content in the <head> element:
<noscript><div>You need to enable javascript for this functionality</div></noscript>

CSE is showing errors because you can't have <div>s in the <head> and it's saying it for every page on our site :(

I need to stop these errors from being flagged so I can see if any others are being generated on the site. Which flag handles these errors (either to stop all <noscript> messages or to stop <div> or text contents in the <head> being flagged)

Thanks

Julian
jscar
Rank II - Novice
Rank II - Novice
 
Posts: 47
Joined: Mon Jul 16, 2007 3:12 am

Re: which flag to stop <noscript> errors

Postby Albert Wiersch » Wed Nov 23, 2011 10:50 am

Hi Julian,

Are you able to change the CMS output? If you are you could fix the output (move it out of the "head" section) or at least add special comments so that CSE HTML Validator ignores it (this would be the best solution):

Code: Select all
<!--cseignore--><noscript><div>You need to enable javascript for this functionality</div></noscript><!--/cseignore-->


There is no flag that you can use to disable that message but you could use the 'Disable using Exact Text Match' function (available when you right-click on the message in the Results Window), but that would disable the message for any situation.

You are probably also getting this message: "Text is contained in a "head" element. Because it is contained here, it must also be contained in a "title" element.", and you could also disable this message using the 'Disable using Exact Text Match' function as well.

One final solution, which is more complex and requires v11 pro or higher, would be to use the new "user functions" file and write some functions to disable these messages, but only under the desired circumstances. I can help you with this if you'd like to try it this way.
Image
Albert Wiersch
User avatar
Albert Wiersch
Site Admin
Site Admin
 
Posts: 2361
Joined: Sat Dec 11, 2004 10:23 am
Location: Near Dallas, TX

Re: which flag to stop <noscript> errors

Postby jscar » Thu Nov 24, 2011 4:33 am

Thanks Albert

can't get to the CMS output :(
Haven't got v11

Will try the 'Disable using Exact text Match' function. If you don't hear assume back it's worked :)

Cheers

Julian
jscar
Rank II - Novice
Rank II - Novice
 
Posts: 47
Joined: Mon Jul 16, 2007 3:12 am

Re: which flag to stop <noscript> errors

Postby jscar » Thu Nov 24, 2011 4:44 am

Should have mentioned that I'm using Batch Wizard. I can't see anywhere to get to a results window from that. I've only got tyeh batch progress and the final html report.
jscar
Rank II - Novice
Rank II - Novice
 
Posts: 47
Joined: Mon Jul 16, 2007 3:12 am

Re: which flag to stop <noscript> errors

Postby Albert Wiersch » Thu Nov 24, 2011 11:00 am

jscar wrote:Should have mentioned that I'm using Batch Wizard. I can't see anywhere to get to a results window from that. I've only got tyeh batch progress and the final html report.


Hello,

Please try to reproduce the results in the editor so that the messages display in the Results Window, then you can disable them. You'll probably just need to paste the source of one of the documents into the editor then validate it.
Image
Albert Wiersch
User avatar
Albert Wiersch
Site Admin
Site Admin
 
Posts: 2361
Joined: Sat Dec 11, 2004 10:23 am
Location: Near Dallas, TX


Return to CSE Tech Support

Who is online

Users browsing this forum: MSN [Bot] and 2 guests

cron