This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24803 - <option> when it has no @label or @value must have content and has text as content model. Isn't it "escapable raw text"?
Summary: <option> when it has no @label or @value must have content and has text as co...
Status: RESOLVED WORKSFORME
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-25 16:30 UTC by contributor
Modified: 2014-02-25 19:16 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2014-02-25 16:30:09 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#elements-0
Complete: http://www.whatwg.org/c#elements-0
Referrer: 

Comment:
<option> when it has no @label or @value must have content and has text as
content model. Isn't it "escapable raw text"?

Posted from: 84.220.11.90
User agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.117 Safari/537.36
Comment 1 Ian 'Hixie' Hickson 2014-02-25 18:25:35 UTC 
No? Why would it be? If you write <select><option><em>text, the "<em>" part is dropped on the floor, it's not treated as literal characters.
Comment 2 Andrea Rendine 2014-02-25 19:16:10 UTC 
Derived from how other text-content elements treat tags. Understood (and tested). Thanks.