[Bug 28967] New: "Legacy" appendices should be normative
[Bug 26676] Non-fullscreen documents can end up with non-empty fullscreen element stacks
[Bug 27674] requestFullscreen should return a promise
[Bug 28459] Algorithm of exitFullscreen() doesn't work correctly when there are nested fullscreen element
[Bug 26676] Non-fullscreen documents can end up with non-empty fullscreen element stacks
[Bug 28460] Request fullscreen on both iframe and elements inside it could cause undesired result
[Bug 28460] Request fullscreen on both iframe and elements inside it could cause undesired result
[Bug 28460] Request fullscreen on both iframe and elements inside it could cause undesired result
[Bug 26676] Non-fullscreen documents can end up with non-empty fullscreen element stacks
[Bug 26813] Removing parent of element that's full screen
[Bug 28460] Request fullscreen on both iframe and elements inside it could cause undesired result
[Bug 19431] Namespace of elements made via .createElement() in XML documents must be null
[Bug 27301] Define context variables, such as "context object"
[Bug 27301] Define context variables, such as "context object"
[Bug 28614] Weaken the requirement of the time of running async steps
[Bug 27162] Browser differences in graphical layout of fullscreen mode.
[Bug 28459] Algorithm of exitFullscreen() doesn't work correctly when there are nested fullscreen element
[Bug 28459] Algorithm of exitFullscreen() doesn't work correctly when there are nested fullscreen element
[Bug 28798] Indicate BufferSource algorithms can throw
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 27674] requestFullscreen should return a promise
[Bug 26440] Allow fullscreenchange events to be synchronized with animation frames
[Bug 27674] requestFullscreen should return a promise
[Bug 26440] Allow fullscreenchange events to be synchronized with animation frames
[Bug 27674] requestFullscreen should return a promise
[Bug 26676] Non-fullscreen documents can end up with non-empty fullscreen element stacks
[Bug 26440] Allow fullscreenchange events to be synchronized with animation frames
[Bug 28460] Request fullscreen on both iframe and elements inside it could cause undesired result
[Bug 28459] Algorithm of exitFullscreen() doesn't work correctly when there are nested fullscreen element
[Bug 26677] Clarify when :fullscreen applies
[Bug 27674] requestFullscreen should return a promise
[Bug 26676] Non-fullscreen documents can end up with non-empty fullscreen element stacks
[Bug 27863] Not need to specify moving element in top layer and fullscreen stack
[Bug 26676] Non-fullscreen documents can end up with non-empty fullscreen element stacks
[Bug 27865] Merge fullscreen element stack into top layer
[Bug 27688] Odd comment in DOM spec about the new "Elements" class
[Bug 28943] New: avoid "nuked"
- [Bug 28943] avoid "nuked"
- [Bug 28943] avoid "nuked"
- [Bug 28943] avoid "nuked"
- [Bug 28943] avoid "nuked"
- [Bug 28943] avoid "nuked"
- [Bug 28943] avoid "nuked"
- [Bug 28943] avoid "nuked"
[Bug 27301] Define context variables, such as "context object"
[Bug 28938] New: Consider adding sourceDevice property to UIEvent
[Bug 27558] Specify MouseEvent.which
[Bug 27558] Specify MouseEvent.which
[Bug 27558] Specify MouseEvent.which
[Bug 27558] Specify MouseEvent.which
[Bug 27558] Specify MouseEvent.which
[Bug 27558] Specify MouseEvent.which
[Bug 27558] Specify MouseEvent.which
[Bug 27558] Specify MouseEvent.which
[Bug 27558] Specify MouseEvent.which
[Bug 28924] New: Is CompositionEvent supposed to have .locale?
- [Bug 28924] Is CompositionEvent supposed to have .locale?
- [Bug 28924] Is CompositionEvent supposed to have .locale?
[Bug 26611] [Proposal] Add "Zoom" event
[Bug 28797] Use IsDetachedBuffer() for BufferSource types consistently
[Bug 28797] Use IsDetachedBuffer() for BufferSource types consistently
[Bug 28797] Use IsDetachedBuffer() for BufferSource types consistently
[Bug 28797] Use IsDetachedBuffer() for BufferSource types consistently
[Bug 23076] Change "float" in examples to "double"
[Bug 27317] Provide explicit guidance on enum value naming
[Bug 27906] "If validThis is false, then return."
[Bug 28328] Bad color contrast for code in note
[Bug 28477] Warn against boolean arguments defaulting to true
[Bug 28602] Add additional restrictions for constants?
[Bug 28646] [WebIDL] conforming *set* of IDL fragments?
[Bug 28647] [WebIDL] error in TreatNullAs example
[Bug 25458] [Shadow]: The return type of Event.path should leverage WebIDL sequences
[Bug 21066] Provide an event path API
[Bug 24586] Remove FileList
[Bug 23682] Fix the current [ArrayClass], [] and sequence<T> mess
[Bug 20713] Consider defining window.event and Event.srcElement
[Bug 20713] Consider defining window.event and Event.srcElement
[Bug 20713] Consider defining window.event and Event.srcElement
[Bug 20713] Consider defining window.event and Event.srcElement
[Bug 26643] Figure out how "If a reflecting IDL attribute has the type HTMLElement, or an interface that descends from HTMLElement" should work in the context of shadow dom.
[Bug 23018] [Custom]: Consider creating registries for HTML documents created through DOMImplementation in some cases
[Bug 14973] [Meta]: Specify how decorators work
[Bug 14983] [Decorators]: Consider limiting decorator application by element type
[Bug 15479] [Decorators]: Alternative idea using CSS variables
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 25715] [imports]: Unify loading and dependency resolution model with ES6 modules
[Bug 25473] [Custom]: Add support for focus navigation similar to input type=date
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27769] [Custom]: ES6 section needs to be updated
[Bug 25669] [Custom]: Make ES6 prose normative when ES6 ships
[Bug 15013] [Meta] Provide simple bug-filing facilities for the deliverables.
[Bug 21914] bug-assist should include a URL in the bug description
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27440] [Custom]: callbacks don't deal with exceptions
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 20973] [Custom]: Restrict custom elements to NCName
[Bug 25669] [Custom]: Make ES6 prose normative when ES6 ships
[Bug 27405] [Custom]: Convert all ES5 references to ES6
[Bug 14972] [Meta]: Component Model Master Bug
[Bug 15013] [Meta] Provide simple bug-filing facilities for the deliverables.
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27768] [Custom]: Make "Parsing Custom Elements" section more explicit
[Bug 27375] [Shadow]: Define whether <style>s in shadow trees are loaded
[Bug 26934] [Shadow]: How should Element.requestPointerLock() work in shadow DOM?
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 26583] [Custom]: Add the possibility to extend the custom element
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 25696] [imports]: <link media>
[Bug 25669] [Custom]: Make ES6 prose normative when ES6 ships
[Bug 24020] [Custom]: A tag name should be associated with the constructor and not the prototype
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27914] [Custom]: Typo instantation ---> instantiation
[Bug 22056] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters?
[Bug 26656] Figure out how form owner should work in shadow dom
[Bug 14974] [Meta]: Provide a detailed overview of the component model
[Bug 14981] [Overview]: Add Productivity and Performance as general properties
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 26898] [imports]: <link rel=import> shouldn't be active when added by innerHTML
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27780] [Custom]: "All Algorithms in One Diagram"
[Bug 14972] [Meta]: Component Model Master Bug
[Bug 14949] [Meta]: Component Model needs an Explainer document
[Bug 26845] [Shadow] "All other HTML elements in the shadow trees must behave as if they were part of the document tree." does not deal with the case when the host is not in the document tree
[Bug 14973] [Meta]: Specify how decorators work
[Bug 15148] [Decorators]: Would there be any associated events fired when decorator gets unapplied?
[Bug 14956] [Meta]: Web Components needs code samples
[Bug 15501] [Samples]: Write a recipe for using CSS variables in shadow DOM subtrees
[Bug 25484] [Explainer]: Example querySelectors need to select IDs
[Bug 14949] [Meta]: Component Model needs an Explainer document
[Bug 25924] [Imports]: The spec. is not very specific about the edge cases of the load
[Bug 14949] [Meta]: Component Model needs an Explainer document
[Bug 24629] [Explainer]: attachedCallback / detachedCallback are now enteredView and leftView?
[Bug 14972] [Meta]: Component Model Master Bug
[Bug 14974] [Meta]: Provide a detailed overview of the component model
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 20567] Change [[Prototype]] for concept-node-adopt?
[Bug 24577] [Custom]: Need adopted callback
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 25568] [imports]: Respect the crossOrigin attribute
[Bug 14962] [Samples]: Write contacts widget sample
[Bug 14956] [Meta]: Web Components needs code samples
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 23278] [imports]: Things to Consider in the Future
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27611] [Custom]: SVG diagram accessibility
[Bug 15013] [Meta] Provide simple bug-filing facilities for the deliverables.
[Bug 21913] bug-assist doesn't support selection in Opera (Presto)
[Bug 28545] Declarative syntax for custom elements
[Bug 15013] [Meta] Provide simple bug-filing facilities for the deliverables.
[Bug 21915] bug-assist should set z-index
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 26852] [Custom]: Specify preference of localName and typeExtension in createElement
[Bug 14949] [Meta]: Component Model needs an Explainer document
[Bug 22836] Missing First Principle in overall Design
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 20567] Change [[Prototype]] for concept-node-adopt?
[Bug 24579] [Custom]: make callbacks more explicit
[Bug 14949] [Meta]: Component Model needs an Explainer document
[Bug 27496] [Explainer]: mispell on inherifance
[Bug 17761] Consider a src/href-like attribute for easy integration?
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27260] [Custom]: Need to define global/Realm handling for registerElement
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 24570] [Custom]: Callback for cloneNode/importNode
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 24087] [Custom]: Rename document.registerElement to document.define or document.defineElement
[Bug 27379] [Shadow] How should element.requestFullscreen(); work in shadow dom
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 28051] [imports]: showing <dialog> from import
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27762] [Custom]: Make unresolved state an explicit flag.
[Bug 23278] [imports]: Things to Consider in the Future
[Bug 21253] [Imports]: Consider changing component location to component identifier
[Bug 26846] [Shadow] it is unclear how elements in older shadow trees should work in case the newer shadow tree lacks <shadow>
[Bug 28086] [Shadow] (assuming iframes should work inside shadow DOM) Should the contentWindow objects of iframes in shadow DOM show up in window.frames?
[Bug 24632] [meta][imports]: The spec should have fewer monkey patches
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 25566] [imports]: Supporting more than just the script-src CSP directive in imports.
[Bug 28547] Remove the support for inherting from builtin subclasses of HTMLElement and SVGElement
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 28092] [Custom]: Clarify in informative note that cloning/importing also enqueues created callback
[Bug 14987] [Custom Elements]: When is "created" callback invoked?
[Bug 14972] [Meta]: Component Model Master Bug
[Bug 21499] [Meta]: Web Developers Feedback/Hotlist
[Bug 23861] [Shadow] The "Events that are Always Stopped" list looks rather random
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 24655] [Custom]: Consider turning processing stack + queues into its own primitive
[Bug 14972] [Meta]: Component Model Master Bug
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 14972] [Meta]: Component Model Master Bug
[Bug 14956] [Meta]: Web Components needs code samples
[Bug 14975] [Overview]: Migrate overview docs from whatwg.org
[Bug 14976] [Overview]: Rewrite property explanations to be less tangled with building blocks
[Bug 27380] [Shadow] How should various document internal references work when SVG is being used in shadow DOM
[Bug 26681] [imports]: Script execution order should be stated more clearly
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 27017] [Custom]: Constructor/prototype linkage needs to actually be defined, since it's dynamic, not static
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27836] Scripts in HTML Imports should be scoped to the import (treat imports as script modules)
[Bug 26943] [Custom] Should attachedCallback/detachedCallback callbacks be called when element is added to / removed from shadom dom which is attached to a in-document host?
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27978] [Custom]: attachedCallback has no protocol for indicating that the custom tag is not applicable in this context
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 20466] [Accessibility]: Custom element should allow declaration of default accessibility features, such as role and other ARIA attributes.
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 25818] [imports]: The dedup behavior with redirects should be clarified.
[Bug 14973] [Meta]: Specify how decorators work
[Bug 24578] [Custom]: define registry primitive; ("namespace" support needed?)
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 15058] Specify what happens when decorators infinitely loop
[Bug 27975] [Custom]: No way to unregister a component
[Bug 14972] [Meta]: Component Model Master Bug
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 26638] [Custom]: sorted element queue definition is not in sync with Imports
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 25669] [Custom]: Make ES6 prose normative when ES6 ships
[Bug 23864] [Shadow] "TouchEvent is not subject to this rule." in 6.7 doesn't make sense
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27976] [Custom]: type extensions should be available as custom tags, not only through <baseTag is="...">
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 28158] [Custom]: inflexible extends as fixed element type
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 26576] [Custom]: Add informative text about importNode
[Bug 22900] [Shadow]: clarify scoping node of styles in shadow trees
[Bug 28449] [Shadow]: Allow certain pseudo-classes in content selectors
[Bug 14956] [Meta]: Web Components needs code samples
[Bug 14963] [Samples]: Write Like/+1 Button sample
[Bug 14972] [Meta]: Component Model Master Bug
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 26682] [imports]: The relationship between import and browsing context should be stated more clearly
[Bug 26713] DOMFocusIn/DOMFocusOut in ShadowDOM spec should be renamed to focusin/focusout
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 25610] [imports]: Want an informative section about implications of how CSP + Imports is defined
[Bug 14949] [Meta]: Component Model needs an Explainer document
[Bug 24876] [Custom Elements]: Custom elements should be display: block by default
[Bug 25470] [imports]: improve description of async to clarify execution order
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 27016] [Custom]: Custom element constructor behavior makes no sense
[Bug 14973] [Meta]: Specify how decorators work
[Bug 15053] [Decorators]: Decorator changes should work with CSS Transitions and Animations
[Bug 23278] [imports]: Things to Consider in the Future
[Bug 24042] [imports]: Parser should not wait on external resources inside imports
[Bug 14975] [Overview]: Migrate overview docs from whatwg.org
[Bug 14977] [Overview]: Link use cases to samples and back
[Bug 22409] Custom elements need da (microtask) hookup
[Bug 14956] [Meta]: Web Components needs code samples
[Bug 14959] [Samples]: Write Layout Manager example
[Bug 28543] Custom elements should call user defined constructor synchronously
[Bug 25563] [Shadow]: Define the impact of ordering on relevant HTML elements
[Bug 17089] [Shadow]: activeElement adjustment adjusts activeElement to the shadow root itself
[Bug 24578] [Custom]: define registry primitive; ("namespace" support needed?)
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27835] registerElement() should be scoped to modules
[Bug 15013] [Meta] Provide simple bug-filing facilities for the deliverables.
[Bug 21916] bug-assist should use data-* attributes instead of <meta name>
[Bug 14949] [Meta]: Component Model needs an Explainer document
[Bug 25916] [Explainer]: Custom pseudo elements are still used in the examples.
[Bug 21169] [Imports]: Write introduction section
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 28544] Custom elements should not upgrade elements by setting prototype
[Bug 23278] [imports]: Things to Consider in the Future
[Bug 24848] [imports]: ES6 module loader should be aware modules in HTML Imports
[Bug 14981] [Overview]: Add Productivity and Performance as general properties
[Bug 14974] [Meta]: Provide a detailed overview of the component model
[Bug 14975] [Overview]: Migrate overview docs from whatwg.org
[Bug 23278] [imports]: Things to Consider in the Future
[Bug 25319] [imports]: Want some kind of imperative API
[Bug 24756] [imports]: Cascading order for stylesheets of imported documents should be stated more clearly
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 19685] [Shadow]: We need comment about "scope" for shadow reference combinator.
[Bug 14984] [Decorators]: Research the impact of the "projected DOM" system
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 24866] [Custom]: Consider adding inserted/removed callback
[Bug 24106] FKA: No defined way to get keyboard focus into and out of a shadow DOM component
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27437] [Custom]: Be clear about whether attached callback should be enqueued when setting prototype
[Bug 27770] [Custom]: Improve the wording in element upgrade algorithm
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27975] [Custom]: No way to unregister a component
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 20683] [Imports]: Write HTML Imports spec
[Bug 26233] [imports]: Typo: "overnride"
[Bug 27751] [Custom]: suggest note on requirements
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 14949] [Meta]: Component Model needs an Explainer document
[Bug 24398] [Explainer]: typo ":" should be "="
[Bug 28541] Custom elements should use ES6 class constructor
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 24178] [Custom]: No way to differentiate attribute namespaces in attributeChanged callback
[Bug 14949] [Meta]: Component Model needs an Explainer document
[Bug 26065] [Explainer]:
[Bug 15018] [Samples]: Write Media Controls for the Video Element Sample.
[Bug 14972] [Meta]: Component Model Master Bug
[Bug 14956] [Meta]: Web Components needs code samples
[Bug 14973] [Meta]: Specify how decorators work
[Bug 22038] Changing "href" attribute on <link> should trigger re-downloading hyperlink
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 25830] [Custom]: What should be the name of the generated constructor returned by registerElement?
[Bug 14956] [Meta]: Web Components needs code samples
[Bug 15478] [Samples]: Write a tab layout manager with tab overflow
[Bug 14961] [Samples]: Write form controls in SVG sample
[Bug 14956] [Meta]: Web Components needs code samples
[Bug 15013] [Meta] Provide simple bug-filing facilities for the deliverables.
[Bug 15012] [bug-assist]: Selection is lost when using acceskeys
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 24603] [Custom]: Need callback for form submit data
[Bug 26213] Need a shadowRoots MutationObserver option
[Bug 27977] [Custom]: mixin pattern: custom elements should be able to extend any base tag with is=
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27538] [Custom]: Tone of note doesn't reflect severity
[Bug 27366] Define how shadow DOM should be handled when host is adopted to a new document
[Bug 17591] [Shadow]: Should insertion point nodes have styles?
[Bug 28542] [Shadow] Replace node distribution mechanism by the named slot proposal
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27643] [Custom]: Section 10 prototype is not defined
[Bug 23278] [imports]: Things to Consider in the Future
[Bug 25007] [imports]: Want New LinkImport method to return a promise.
[Bug 27325] [Shadow]: Figure out how session history should work for <iframe>s in shadow DOM
[Bug 28546] document.registerElement should take a template as an argument
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27016] [Custom]: Custom element constructor behavior makes no sense
[Bug 14956] [Meta]: Web Components needs code samples
[Bug 14960] [Samples]: Write Widget Mix-and-Match example
[Bug 21120] Define TV or A/V remote controller's keys
[Bug 16153] [Templates]: Enable generated template elements to share a content docFrag
[Bug 15454] [Templates]: Consider pattern substitution
[Bug 16279] [Templates]: Add an example
[Bug 18710] [Templates]: Trigger parse errors when template content does not match the template context.
[Bug 21809] [Templates]: <template> should allow <body> as a child
[Bug 19486] [Templates]: Parsing spec defines "current table" in terms of the fragment case
[Bug 19487] [Templates]: Consider re-writing the foster-parenting as an algorithm
[Bug 23409] [Templates]: Typo: hierarhcy
[Bug 23628] [Templates]: Typo: "hierarhcy"
[Bug 23752] [Templates]:
[Bug 14972] [Meta]: Component Model Master Bug
[Bug 15476] [Templates]: Specify how templates work
[Bug 28902] New: [Shadow] How should mouse (&co) events be targeted in case user clicks on a text node
[Bug 28890] New: scroll should be a simple Event not a UIEvent
[Bug 27863] Not need to specify moving element in top layer and fullscreen stack
[Bug 27865] Merge fullscreen element stack into top layer
[Bug 27865] Merge fullscreen element stack into top layer
[Bug 27865] Merge fullscreen element stack into top layer
[Bug 27865] Merge fullscreen element stack into top layer
[Bug 27865] Merge fullscreen element stack into top layer
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 27865] Merge fullscreen element stack into top layer
[Bug 27865] Merge fullscreen element stack into top layer
[Bug 14968] [Meta]: Specify how custom elements work
[Bug 28878] New: [Custom]: A sample bug for test
[Bug 28875] New: [EnforceRange] accepts an odd set of input values
- [Bug 28875] [EnforceRange] accepts an odd set of input values
- [Bug 28875] [EnforceRange] accepts an odd set of input values
- [Bug 28875] [EnforceRange] accepts an odd set of input values
- [Bug 28875] [EnforceRange] accepts an odd set of input values
- [Bug 28875] [EnforceRange] accepts an odd set of input values
- [Bug 28875] [EnforceRange] accepts an odd set of input values