This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7597 - Markup "loaded" by validator differs from the markup loaded by public browser
Summary: Markup "loaded" by validator differs from the markup loaded by public browser
Alias: None
Product: Validator
Classification: Unclassified
Component: Website (show other bugs)
Version: HEAD
Hardware: PC Windows 2000
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
Depends on:
Reported: 2009-09-13 08:59 UTC by Chris Rasmussen
Modified: 2009-09-13 22:51 UTC (History)
0 users

See Also:


Description Chris Rasmussen 2009-09-13 08:59:28 UTC
I'm not sure if this is a bug or not but this is the only place I could find to report something like this.

I'm trying to validate at the moment.  If I load the page and validate the source by direct input the page validates without any errors (XHTML 1.0 Strict).

However, if I validate by URI the validator fails with 3 errors, all of which relate to markup that does not show in the source when viewing the URL in a browser.
Comment 1 Ville Skyttä 2009-09-13 09:20:00 UTC
Validator checks what it gets served, you can see what it got using the "Show Source" checkbox in validator's options.

Looks like the site is using ASP.Net; if it is, this might be helpful:
(see "Configuring Browser Capabilities for Markup Validation")

The user-agent query string parameter for the validator can be used to set a custom User-Agent header, that might affect the markup it gets served.
Comment 2 Chris Rasmussen 2009-09-13 11:51:57 UTC
Yes I understand that and I've already done all that but I don't see why the validator would get different markup than a 'normal' browser.  One of the errors I get is:

Line 20, Column 16: Attribute "name" exists, but can not be used for this element.
<form name="aspnetForm" method="post" action="Default.aspx" id="aspnetForm">

When I view the source in a browser that attribute isn't there.  It's only there when I view the source received by the validator.

Isn't that a bit strange?
Comment 3 Ville Skyttä 2009-09-13 21:23:01 UTC
Perhaps, but there's nothing the validator can do about that, it needs to be addressed at the server serving the document.  Or as said, you can try the user-agent (and accept, accept-language, and accept-charset) query string parameters to make the validator appear as a different "browser".
Comment 4 Chris Rasmussen 2009-09-13 22:50:54 UTC
Ok, understood.  Thank you everyone!
Comment 5 Chris Rasmussen 2009-09-13 22:51:51 UTC
Ok, understood.  Thank you everyone!