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 18234 - Invalid IDL of SelectionMode
Summary: Invalid IDL of SelectionMode
Status: CLOSED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 17:46 UTC by contributor
Modified: 2012-09-07 14:18 UTC (History)
5 users (show)

See Also:


Attachments

Description contributor 2012-07-18 17:46:49 UTC
This was was cloned from bug 17508 as part of operation convergence.
Originally filed: 2012-06-16 11:07:00 +0000

================================================================================
 #0   contributor@whatwg.org                          2012-06-16 11:07:21 +0000 
--------------------------------------------------------------------------------
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:
Invalid IDL of SelectionMode

Posted from: 84.182.211.110
User agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.34 Safari/536.11
================================================================================
 #1   Wolfgang Keller                                 2012-06-16 11:16:23 +0000 
--------------------------------------------------------------------------------
If we look at http://www.whatwg.org/specs/web-apps/current-work/#selectionmode we'll see the following IDL of SelectionMode

enum SelectionMode {
  // ...
  'preserve',
};

This is not allowed according to WebIDL http://dev.w3.org/2006/webapi/WebIDL/

Let's look why:

The nonterminal EnumValueList (what is between the { }) is defined (using EnumValues) as

[21]	EnumValueList	→	string EnumValues
[22]	EnumValues	→	"," string EnumValues 
 | ε

Thus if there is a comma a string has to follow. This string 'preserve' (which is also an invalid string according to WebIDL since string terminals have to be enclosed in double quotes - see bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=17507 - but this shall not mind here) is followed by a comma - but not by an additional string.

Thus we either have to change the WebIDL rules such that there is no need for a string after a comma or fix this IDL fragment by removing the , after 'preserve'.
================================================================================
Comment 1 Robin Berjon 2012-09-07 13:13:31 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: Accepted
Change Description: Deleted comma
Rationale: Trailing comma
Comment 2 Robin Berjon 2012-09-07 13:14:24 UTC
Forgot to include commit: https://github.com/w3c/html/commit/e478c2e990af647564e9d538033445ddc0c3e53f