W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2010

[Bug 10315] please allow "command" and "base" in "in head noscript" insertion mode so all void elements that might be handled in head-related insertion modes are treated in the same manner, which would simplify parser implementation a little

From: <bugzilla@jessica.w3.org>
Date: Fri, 10 Sep 2010 19:25:52 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Ou9EO-0002gh-BH@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10315


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |eric@webkit.org,
                   |                            |hsivonen@iki.fi,
                   |                            |ian@hixie.ch,
                   |                            |w3c@adambarth.com
         Resolution|                            |WONTFIX




--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-09-10 19:25:51 ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale:

<base> is not allowed because having all the URLs in the document have
different meanings based on whether you're scripted or not is a debugging
nightmare.

<command> is not allowed because it makes no sense when scripts are disabled.

I suppose we could handle them in the parser while making them still
non-conforming, but would it really help all that much in the parser's
development?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 10 September 2010 19:25:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:24 UTC