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 14914 - This IDL doesn't parse. These IDL members are already in HTMLInputElement and HTMLTextAreaElement -- why do they need to be repeated here in a separate IDL fragment?
Summary: This IDL doesn't parse. These IDL members are already in HTMLInputElement an...
Status: CLOSED WONTFIX
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: 2011-11-23 17:40 UTC by contributor
Modified: 2012-07-18 18:42 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2011-11-23 17:40:19 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#textFieldSelection
Complete: http://www.whatwg.org/c#textFieldSelection

Comment:
This IDL doesn't parse.  These IDL members are already in HTMLInputElement and
HTMLTextAreaElement -- why do they need to be repeated here in a separate IDL
fragment?

Posted from: 68.175.61.233
User agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.8 (KHTML, like Gecko) Chrome/17.0.938.0 Safari/535.8
Comment 1 Ian 'Hixie' Hickson 2011-12-08 00:00:54 UTC 
Just to remind readers, the same way the URL decomposition attributes are listed again in their section.

Does it cause harm? The <pre> block has a class="idl extract" which is distinguishable from <pre class="idl"> so you can avoid automatically parsing it, if that's the issue.
Comment 2 Ian 'Hixie' Hickson 2011-12-09 22:22:48 UTC 
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: see comment 1
Comment 3 Aryeh Gregor 2011-12-27 14:44:59 UTC 
That workaround is good enough for me.