Re: VS 2005 XHTML Compliancy problem

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Cowboy \(Gregory A. Beamer\) (NoSpamMgbworld_at_comcast.netNoSpamM)
Date: 12/20/04 

Date: Sun, 19 Dec 2004 23:23:19 -0600

Before getting too concerned, I would wait until the product is out of beta.
If there is still a problem either complain or edit the schemas yourself, or
both. For now, the best bet is registering with the VS beta site on
msdn.microsoft.com and posting the issue; this will help MS get rid of the
bug before final release.

What version of VS 2005 are you testing right now? The latest build, in
wider release anyway, is the November CTP, which was released to MSDN
subscribers. 

-- 
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
*************************************************
Think outside the box!
*************************************************
"Walt Zydhek" <Walt Zydhek@discussions.microsoft.com> wrote in message 
news:3DBD347D-1F24-4B39-8243-847A04646547@microsoft.com...
> I'm testing Visual Studio 2005 for design of pages that are XHTML 1.1 
> Strict
> compliant and have found a few problems. Wondering if anyone can suggest a
> workaround or if it is an issue Microsoft will be correcting.
>
> First, My page <head> tag has the runat="server" attribute, and any <link>
> tags within it do not render the tag as auto-closing ( <tag /> ). In my
> source, I did write it as an auto-closing tag, and if I remove the
> runat="server" it renders correctly.
>
> Second, in the properties window (when I am located in the document
> section), I am able to add only 1 Stylesheet, whereas I know xhtml 
> supports
> more than one. I have to manaully add any additional <link> tags for the
> additional stylesheets.
>
> Lastly, the <form> tag (when runat="server") renders a name attribute, 
> which
> is not valid in xhtml 1.1 strict. javascripting should be using the id
> attribute instead.
>
> Neither the 1st or second problems show as an error or warning in Visual
> Studio's build in validator (which is set to validate xhtml 1.1 strict). 
> But
> I found them using w3.org's html validator.
>
> Any comments would be appreciated.

Relevant Pages

  • Anyone else noticed this issue?
    ... the correct declaration for calling an external ... I'm using Firefox 3.0 B3 and have noticed that the page is blank, despite it passing validation by the W3 validator. ... I'm learning JavaScript through a book that is using XHTML 1.0 Transitional and these are just scripts from that book. ... I changed the code to be Strict because I prefer to use it. ...
    (alt.html)
  • Anyone else noticed this issue?
    ... the correct declaration for calling an external ... I'm using Firefox 3.0 B3 and have noticed that the page is blank, despite it passing validation by the W3 validator. ... I'm learning JavaScript through a book that is using XHTML 1.0 Transitional and these are just scripts from that book. ... I changed the code to be Strict because I prefer to use it. ...
    (comp.lang.javascript)
  • Re: Tidy trimming empty tags
    ... "XHTML 1.0 Strict" by the W3C Validator. ... Document content looks like XHTML 1.0 Transitional ... (Note that neither Tidy nor AccessValet is a validator. ...
    (comp.infosystems.www.authoring.html)
  • VS 2005 XHTML Compliancy problem
    ... I'm testing Visual Studio 2005 for design of pages that are XHTML 1.1 Strict ... Studio's build in validator. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Javascript beim Laden =?UTF-8?B?YXVzZsO8aHJlbg==?= in KHTML
    ... Data state ... und XHTML 1.0 Strict deklariert wurde. ... HTML5 konformen Parser. ...
    (de.comp.lang.javascript)