W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2010

[whatwg] Validator.nu Bug: "Error: XHTML element noscript not allowed as child of XHTML element head in this context."

From: Hugh Guiney <hugh.guiney@gmail.com>
Date: Fri, 27 Aug 2010 06:32:17 -0400
Message-ID: <AANLkTi=xeRmFzyYhp_TJO4vyKwUSQKSa6_yMAtY8+jOp@mail.gmail.com>
Ah, thanks. I guess the error is just confusing then in that it calls
it "XHTML element noscript", which led me to think that it was indeed
part of XHTML. I think some indication otherwise might prove
beneficial to users.

But, I thought XHTML5 was just an XML serialization of HTML5, so why
is this the case? I just read the rationale behind it, but despite not
being best practice shouldn't it be at the very least allowed?

On Fri, Aug 27, 2010 at 5:26 AM, Anne van Kesteren <annevk at opera.com> wrote:
> On Fri, 27 Aug 2010 11:10:44 +0200, Hugh Guiney <hugh.guiney at gmail.com>
> wrote:
>>
>> I am using noscript as permitted, "In a head element of an HTML
>> document, if there are no ancestor noscript elements." but still
>> getting an error from Validator.nu saying it's not allowed.
>
> <noscript> is HTML-only. I.e. not allowed in XHTML.
>
>
> --
> Anne van Kesteren
> http://annevankesteren.nl/
>
Received on Friday, 27 August 2010 03:32:17 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:00 UTC