i can concurr the issue, i have been trying to down it for ffew time even click provive broughser https download, then viewsource didnt seem right too many padding around the link,
Errors found while checking this document as XHTML 1.0 Transitional!
<form id="form" action="check" enctype="application/x-www-form-urlencoded" method="get">
Result: |
25 Errors, 26 warning(s) |
<label title="Address of Page to Validate" for="uri">Address</label>: |
<input id="uri" name="uri" size="50" type="text" value="http://technet.microsoft.com/en-us/ee390821.aspx" /> |
Modified: |
(undefined) |
Server: |
Microsoft-IIS/7.5 |
Size: |
9666 |
Content-Type: |
text/html |
<label title="Character Encoding" for="charset">Encoding</label>: |
utf-8 |
<select id="charset" name="charset"> <option selected="selected" value="(detect automatically)">(detect automatically)</option> <option value="utf-8">utf-8 (Unicode, worldwide)</option> <option value="utf-16">utf-16 (Unicode, worldwide)</option> <option
value="iso-8859-1">iso-8859-1 (Western Europe)</option> <option value="iso-8859-2">iso-8859-2 (Central Europe)</option> <option value="iso-8859-3">iso-8859-3 (Southern Europe)</option> <option value="iso-8859-4">iso-8859-4 (North European)</option> <option
value="iso-8859-5">iso-8859-5 (Cyrillic)</option> <option value="iso-8859-6-i">iso-8859-6-i (Arabic)</option> <option value="iso-8859-7">iso-8859-7 (Greek)</option> <option value="iso-8859-8">iso-8859-8 (Hebrew, visual)</option> <option value="iso-8859-8-i">iso-8859-8-i
(Hebrew, logical)</option> <option value="iso-8859-9">iso-8859-9 (Turkish)</option> <option value="iso-8859-10">iso-8859-10 (Latin 6)</option> <option value="iso-8859-11">iso-8859-11 (Latin/Thai)</option> <option value="iso-8859-13">iso-8859-13 (Latin 7, Baltic
Rim)</option> <option value="iso-8859-14">iso-8859-14 (Latin 8, Celtic)</option> <option value="iso-8859-15">iso-8859-15 (Latin 9)</option> <option value="iso-8859-16">iso-8859-16 (Latin 10)</option> <option value="us-ascii">us-ascii (basic English)</option>
<option value="euc-jp">euc-jp (Japanese, Unix)</option> <option value="shift_jis">shift_jis (Japanese, Win/Mac)</option> <option value="iso-2022-jp">iso-2022-jp (Japanese, email)</option> <option value="euc-kr">euc-kr (Korean)</option> <option value="gb2312">gb2312
(Chinese, simplified)</option> <option value="gb18030">gb18030 (Chinese, simplified)</option> <option value="big5">big5 (Chinese, traditional)</option> <option value="big5-HKSCS">Big5-HKSCS (Chinese, Hong Kong)</option> <option value="tis-620">tis-620 (Thai)</option>
<option value="koi8-r">koi8-r (Russian)</option> <option value="koi8-u">koi8-u (Ukrainian)</option> <option value="iso-ir-111">iso-ir-111 (Cyrillic KOI-8)</option> <option value="macintosh">macintosh (MacRoman)</option> <option value="windows-1250">windows-1250
(Central Europe)</option> <option value="windows-1251">windows-1251 (Cyrillic)</option> <option value="windows-1252">windows-1252 (Western Europe)</option> <option value="windows-1253">windows-1253 (Greek)</option> <option value="windows-1254">windows-1254
(Turkish)</option> <option value="windows-1255">windows-1255 (Hebrew)</option> <option value="windows-1256">windows-1256 (Arabic)</option> <option value="windows-1257">windows-1257 (Baltic Rim)</option></select> |
<label title="Document Type" for="doctype">Doctype</label>: |
XHTML 1.0 Transitional |
<select id="doctype" name="doctype"> <option selected="selected" value="Inline">(detect automatically)</option> <option value="HTML5">HTML5 (experimental)</option> <option value="XHTML 1.0 Strict">XHTML 1.0 Strict</option> <option value="XHTML 1.0 Transitional">XHTML
1.0 Transitional</option> <option value="XHTML 1.0 Frameset">XHTML 1.0 Frameset</option> <option value="HTML 4.01 Strict">HTML 4.01 Strict</option> <option value="HTML 4.01 Transitional">HTML 4.01 Transitional</option> <option value="HTML 4.01 Frameset">HTML
4.01 Frameset</option> <option value="HTML 3.2">HTML 3.2</option> <option value="HTML 2.0">HTML 2.0</option> <option value="ISO/IEC 15445:2000 ("ISO HTML")">ISO/IEC 15445:2000 ("ISO HTML")</option> <option value="XHTML 1.1">XHTML 1.1</option> <option value="XHTML
+ RDFa">XHTML + RDFa</option> <option value="XHTML Basic 1.0">XHTML Basic 1.0</option> <option value="XHTML Basic 1.1">XHTML Basic 1.1</option> <option value="XHTML Mobile Profile 1.2">XHTML Mobile Profile 1.2</option> <option value="XHTML-Print 1.0">XHTML-Print
1.0</option> <option value="XHTML 1.1 plus MathML 2.0">XHTML 1.1 plus MathML 2.0</option> <option value="XHTML 1.1 plus MathML 2.0 plus SVG 1.1">XHTML 1.1 plus MathML 2.0 plus SVG 1.1</option> <option value="MathML 2.0">MathML 2.0</option> <option value="SVG
1.0">SVG 1.0</option> <option value="SVG 1.1">SVG 1.1</option> <option value="SVG 1.1 Tiny">SVG 1.1 Tiny</option> <option value="SVG 1.1 Basic">SVG 1.1 Basic</option> <option value="SMIL 1.0">SMIL 1.0</option> <option value="SMIL 2.0">SMIL 2.0</option></select> |
Root Element: |
html |
Root Namespace: |
http://www.w3.org/1999/xhtml |
The
W3C CSS validator is developed with assistance from the Mozilla Foundation, and supported by community donations.
Donate and help us build better tools for a better web.
<fieldset id="revalidate_opts"><legend>Options</legend>
<input id="ss" name="ss" type="checkbox" value="1" /><label title="Show Page Source" for="ss">Show Source</label> |
<input id="outline" name="outline" type="checkbox" value="1" /><label title="Show an Outline of the document" for="outline">Show Outline</label> |
<input id="group_no" checked="checked" name="group" type="radio" value="0" /><label for="group_no">List Messages Sequentially</label> <input id="group_yes" name="group" type="radio" value="1" /><label for="group_yes">Group Error Messages by Type</label> |
<input id="No200" name="No200" type="checkbox" value="1" /><label title="Validate also pages for which the HTTP status code indicates an error" for="No200">Validate error pages</label> |
<input id="verbose" checked="checked" name="verbose" type="checkbox" value="1" /><label title="Show Verbose Output" for="verbose">Verbose Output</label> |
<input id="st" name="st" type="checkbox" value="1" /><label for="st">Clean up Markup with HTML Tidy</label> |
Help on the options is available.
<input id="user-agent" name="user-agent" type="hidden" value="W3C_Validator/1.1" /> <input title="Validate this document again" type="submit" value="Revalidate" />
</fieldset> </form>
Notes and Potential Issues
The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation
results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
-
No Character encoding declared at document level
No character encoding information was found within the document, either in an HTMLmeta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the
document will be read from or saved to disk, CD, etc.
See
this tutorial on character encoding for techniques and explanations.
↑ Top
Validation Output: 25 Errors
- Line 39, Column 56:
marked section end not in marked section declaration
var omni_guid='1cfb1e25-a026-413d-ba3f-747e64089824';//]]>
✉
- Line 69, Column 252:
there is no attribute "border"
…rch" src="http://i.technet.microsoft.com/Global/Images/clear.gif" border="0" />
✉
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 71, Column 162:
cannot generate system identifier for general entity "btnid"
…d=ctl00_Masthead_Search_SearchTextBox&btnid=ctl00_Masthead_Search_SearchButton…
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;).The most common cause of this
error is unencoded ampersands in URLs as described by theWDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity
reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code,this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
- Line 71, Column 162:
general entity "btnid" not defined and no default entity
…d=ctl00_Masthead_Search_SearchTextBox&btnid=ctl00_Masthead_Search_SearchButton…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
- Line 71, Column 167:
reference not terminated by REFC delimiter
…00_Masthead_Search_SearchTextBox&btnid=ctl00_Masthead_Search_SearchButton&bran…
✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
- Line 71, Column 167:
reference to external entity in attribute value
…00_Masthead_Search_SearchTextBox&btnid=ctl00_Masthead_Search_SearchButton&bran…
✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
- Line 71, Column 167:
reference to entity "btnid" for which no system identifier could be generated
…00_Masthead_Search_SearchTextBox&btnid=ctl00_Masthead_Search_SearchButton&bran…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
- Line 71, Column 161:
entity was defined here
…id=ctl00_Masthead_Search_SearchTextBox&btnid=ctl00_Masthead_Search_SearchButto…
- Line 71, Column 203:
cannot generate system identifier for general entity "brand"
…id=ctl00_Masthead_Search_SearchButton&brand=TechNet&loc=en-us&focusOnInit=true…
✉
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;).The most common cause of this
error is unencoded ampersands in URLs as described by theWDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity
reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code,this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
- Line 71, Column 203:
general entity "brand" not defined and no default entity
…id=ctl00_Masthead_Search_SearchButton&brand=TechNet&loc=en-us&focusOnInit=true…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
- Line 71, Column 208:
reference not terminated by REFC delimiter
…l00_Masthead_Search_SearchButton&brand=TechNet&loc=en-us&focusOnInit=true" id=…
✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
W3C CSS Validator results for https://www.microsoft.com/betaexperience/pd/Visio2010RTM/enus/ (CSS level 2)
Sorry! We found the following errors (21)
URI :
http://i3.technet.microsoft.com/Platform/MasterPages/TechnetPage2/TechnetPage2-bn20101102.css
3 |
.bottomleftcorner |
Value Error :
background Too many values or values are not recognized : transparent url('/platform/masterpages/technetpage2/contentpane.png') 0 -17px no-repeattransparent url('/platform/masterpages/technetpage2/contentpane.png') 0 -17px no-repeat |
3 |
.bottomrightcorner |
Value Error :
background Too many values or values are not recognized : transparent url('/platform/masterpages/technetpage2/contentpane.png') 100% -17px no-repeattransparent url('/platform/masterpages/technetpage2/contentpane.png') 100% -17px no-repeat |
3 |
.RightAdRail .BostonPostCard h3, .RightAdRail .BostonPostCard h4, .RightAdRail .BostonPostCard h6 |
Value Error :
background Too many values or values are not recognized : #37648f url('/platform/masterpages/TechnetPage2/headers.gif') -1px -66px no-repeat#37648f url('/platform/masterpages/TechnetPage2/headers.gif') -1px -66px no-repeat |
3 |
.rssfeed |
Value Error :
background Too many values or values are not recognized : transparent url('/platform/masterpages/technetpage2/RSS_OFF.png') 0 0 no-repeattransparent url('/platform/masterpages/technetpage2/RSS_OFF.png') 0 0 no-repeat |
3 |
.opmlfeed |
Value Error :
background Too many values or values are not recognized : transparent url('/platform/masterpages/technetpage2/OPML_OFF.gif') 0 0 no-repeattransparent url('/platform/masterpages/technetpage2/OPML_OFF.gif') 0 0 no-repeat |
3 |
.rssfeed:hover |
Value Error :
background Too many values or values are not recognized : transparent url('/platform/masterpages/technetpage2/RSS_OFF.png') 0 0 no-repeattransparent url('/platform/masterpages/technetpage2/RSS_OFF.png') 0 0 no-repeat |
3 |
.opmlfeed:hover |
Value Error :
background Too many values or values are not recognized : transparent url('/platform/masterpages/technetpage2/OPML_OFF.gif') 0 0 no-repeattransparent url('/platform/masterpages/technetpage2/OPML_OFF.gif') 0 0 no-repeat |
3 |
Div.miniRatings |
Parse Error ;*padding-bottom: 0 !important; |
3 |
* |
Parse Error *padding-top: 0 !important} |