[Bug 15972] New: On step 6, it says that the single U+002F SOLIDUS xharacter (/) me be present in void and foreign element. It says on to behave then, but I didn't found any specification on how to behave if it is found on other elements. Should it be ignored or generate

https://www.w3.org/Bugs/Public/show_bug.cgi?id=15972

           Summary: On step 6, it says that the single U+002F SOLIDUS
                    xharacter (/) me be present in void and foreign
                    element. It says on to behave then, but I didn't found
                    any specification on how to behave if it is found on
                    other elements. Should it be ignored or generate
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#sta
                    rt-tags
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: other Hixie drafts (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, alexandre.morgaut@4d.com


Specification:
http://www.whatwg.org/specs/web-apps/current-work/multipage/syntax.html
Multipage: http://www.whatwg.org/C#start-tags
Complete: http://www.whatwg.org/c#start-tags

Comment:
On step 6, it says that the single U+002F SOLIDUS xharacter (/) me be present
in void and foreign element. It says on to behave then, but I didn't found any
specification on how to behave if it is found on other elements. Should it be
ignored or generate a parse error? I often see code like "<td />" or "<script
(...) />.

Posted from: 31.35.10.21 by alexandre.morgaut@4d.com
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/534.52.7
(KHTML, like Gecko) Version/5.1.2 Safari/534.52.7

-- 
Configure bugmail: https://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 Monday, 13 February 2012 09:37:25 UTC