bugzilla@jessica.w3.org
- [Bug 28109] Inconsistent argument naming in createElementNS and  createAttributeNS (Friday, 27 February)
 
- [Bug 28109] Inconsistent argument naming in createElementNS and  createAttributeNS (Friday, 27 February)
 
- [Bug 28109] Inconsistent argument naming in createElementNS and  createAttributeNS (Friday, 27 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Friday, 27 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Friday, 27 February)
 
- [Bug 28109] New: Inconsistent argument naming in createElementNS and  createAttributeNS (Thursday, 26 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Thursday, 26 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Thursday, 26 February)
 
- [Bug 28107] New: TreeWalker nextNode never ascends the tree (Thursday, 26 February)
 
- [Bug 27965] [Shadow]: Shadow host with tabindex=-1, all descendent  tree should be ignored for tab navigation (Thursday, 26 February)
 
- [Bug 27965] [Shadow]: Shadow host with tabindex=-1, all descendent  tree should be ignored for tab navigation (Thursday, 26 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Wednesday, 25 February)
 
- [Bug 28093] Consider using namespaceURI in the IDL (Wednesday, 25 February)
 
- [Bug 28097] surroundContents should check host-inclusive (Wednesday, 25 February)
 
- [Bug 28067] DOMStringList has been removed from DOM (Wednesday, 25 February)
 
- [Bug 28067] DOMStringList has been removed from DOM (Wednesday, 25 February)
 
- [Bug 28097] New: surroundContents should check host-inclusive (Wednesday, 25 February)
 
- [Bug 27333] Most user agents (Chrome, Firefox) seem to distinguish  between space and enter. Enter submits the form, even for radio buttons,  space selects the checkbox. (Wednesday, 25 February)
 
- [Bug 26225] Normative requirement about click event in a note (Wednesday, 25 February)
 
- [Bug 27210] DOM3 key Values reference is incorrectly pointing to  code Values document (Wednesday, 25 February)
 
- [Bug 27131] [D3E-key]: (Wednesday, 25 February)
 
- [Bug 27130] [D3E-key]: (Wednesday, 25 February)
 
- [Bug 27129] [D3E-key]: Separator (Wednesday, 25 February)
 
- [Bug 27948] [D3E-code]: FLock vs. FnLock (Wednesday, 25 February)
 
- [Bug 26019] No way to initialize modifier states except "Alt",  "Control", "Shift" and "Meta" at constructing DOM event with constructor (Wednesday, 25 February)
 
- [Bug 27903] keyModifierState* of SharedKeyboardAndMouseEventInit are  too long names (Wednesday, 25 February)
 
- [Bug 26019] No way to initialize modifier states except "Alt",  "Control", "Shift" and "Meta" at constructing DOM event with constructor (Wednesday, 25 February)
 
- [Bug 27902] SharedKeyboardAndMouseEventInit isn't a good name (Wednesday, 25 February)
 
- [Bug 27902] SharedKeyboardAndMouseEventInit isn't a good name (Wednesday, 25 February)
 
- [Bug 27828] Rename D3E -> UIEvents (Wednesday, 25 February)
 
- [Bug 26455] Please add a link to open bugs to the spec header (Wednesday, 25 February)
 
- [Bug 28093] Consider using namespaceURI in the IDL (Tuesday, 24 February)
 
- [Bug 28093] Consider using namespaceURI in the IDL (Tuesday, 24 February)
 
- [Bug 28093] Consider using namespaceURI in the IDL (Tuesday, 24 February)
 
- [Bug 28093] New: Consider using namespaceURI in the IDL (Tuesday, 24 February)
 
- [Bug 14968] [Meta]: Specify how custom elements work (Tuesday, 24 February)
 
- [Bug 28092] New: [Custom]: Clarify in informative note that  cloning/importing also enqueues created callback (Tuesday, 24 February)
 
- [Bug 28067] DOMStringList has been removed from DOM (Tuesday, 24 February)
 
- [Bug 28067] DOMStringList has been removed from DOM (Tuesday, 24 February)
 
- [Bug 28086] [Shadow] (assuming iframes should work inside shadow  DOM) Should the contentWindow objects of iframes in shadow DOM show up in  window.frames? (Tuesday, 24 February)
 
- [Bug 28086] [Shadow] (assuming iframes should work inside shadow  DOM) Should the contentWindow objects of iframes in shadow DOM show up in  window.frames? (Tuesday, 24 February)
 
- [Bug 27401] [Shadow]: Fully explore composition (Tuesday, 24 February)
 
- [Bug 17761] Consider a src/href-like attribute for easy integration? (Tuesday, 24 February)
 
- [Bug 27401] [Shadow]: Fully explore composition (Tuesday, 24 February)
 
- [Bug 17761] Consider a src/href-like attribute for easy integration? (Tuesday, 24 February)
 
- [Bug 21149] [Shadow]: Shadow DOM-based components could benefit from  a way to detect when light DOM contents change (Tuesday, 24 February)
 
- [Bug 17761] Consider a src/href-like attribute for easy integration? (Tuesday, 24 February)
 
- [Bug 28086] New: [Shadow] (assuming iframes should work inside  shadow DOM) Should the contentWindow objects of iframes in shadow DOM show up  in window.frames? (Monday, 23 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Monday, 23 February)
 
- [Bug 28067] DOMStringList has been removed from DOM (Monday, 23 February)
 
- [Bug 28079] New: [Shadow]: inappropriate reference to CSS3-UI  nav-index spec in focus navigation order (Monday, 23 February)
 
- [Bug 14978] [Meta]: Specify how shadow DOM works (Monday, 23 February)
 
- [Bug 28068] Should ProcessingInstruction implement LinkStyle? (Sunday, 22 February)
 
- [Bug 14978] [Meta]: Specify how shadow DOM works (Saturday, 21 February)
 
- [Bug 28069] New: [Shadow]: Should  Text.getDestinationInsertionPoints() be specified? (Saturday, 21 February)
 
- [Bug 28068] New: Should ProcessingInstruction implement LinkStyle? (Saturday, 21 February)
 
- [Bug 28067] New: DOMStringList has been removed from DOM (Saturday, 21 February)
 
- [Bug 26609] AttrExodus: investigate child nodes of attributes and  attributes being nodes (Saturday, 21 February)
 
- [Bug 28065] New: WebIDL: Grammar for readonly requires 2 token  lookahead in some cases (Friday, 20 February)
 
- [Bug 26440] Allow fullscreenchange events to be synchronized with  animation frames (Friday, 20 February)
 
- [Bug 27865] Merge fullscreen element stack into top layer (Friday, 20 February)
 
- [Bug 26676] Non-fullscreen documents can end up with non-empty  fullscreen element stacks (Friday, 20 February)
 
- [Bug 26676] Non-fullscreen documents can end up with non-empty  fullscreen element stacks (Friday, 20 February)
 
- [Bug 26440] Allow fullscreenchange events to be synchronized with  animation frames (Friday, 20 February)
 
- [Bug 26440] Allow fullscreenchange events to be synchronized with  animation frames (Friday, 20 February)
 
- [Bug 28061] Description of before/after/replace only mentions single  node (Friday, 20 February)
 
- [Bug 28061] Description of before/after/replace only mentions single  node (Friday, 20 February)
 
- [Bug 28061] Description of before/after/replace only mentions single  node (Friday, 20 February)
 
- [Bug 28061] New: "The before(nodes) method must run these steps:  ..." (Friday, 20 February)
 
- [Bug 28057] New: Support Promise subclass (Thursday, 19 February)
 
- [Bug 20019] Support subclassing ES6 Map (Thursday, 19 February)
 
- [Bug 27965] [Shadow]: Shadow host with tabindex=-1, all descendent  tree should be ignored for tab navigation (Thursday, 19 February)
 
- [Bug 28054] Focus on shadow host should slide to its inner focusable  node (Thursday, 19 February)
 
- [Bug 27976] [Custom]: type extensions should be available as custom  tags, not only through <baseTag is="..."> (Thursday, 19 February)
 
- [Bug 28051] [imports]: showing <dialog> from import (Thursday, 19 February)
 
- [Bug 28054] New: Focus on shadow host should slide to its inner  focusable node (Thursday, 19 February)
 
- [Bug 28051] [imports]: showing <dialog> from import (Wednesday, 18 February)
 
- [Bug 28051] [imports]: showing <dialog> from import (Wednesday, 18 February)
 
- [Bug 20683] [Imports]: Write HTML Imports spec (Wednesday, 18 February)
 
- [Bug 28051] New: [imports]: showing <dialog> from import (Wednesday, 18 February)
 
- [Bug 25473] [Custom]: Add support for focus navigation similar to  input type=date (Wednesday, 18 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Tuesday, 17 February)
 
- [Bug 28029] Mouse coordinates represented in CSS pixels do not  account for retina displays with window.devicePixelRatio > 1. (Tuesday, 17 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Tuesday, 17 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Tuesday, 17 February)
 
- [Bug 28029] Mouse coordinates represented in CSS pixels do not  account for retina displays with window.devicePixelRatio > 1. (Monday, 16 February)
 
- [Bug 28029] Mouse coordinates represented in CSS pixels do not  account for retina displays with window.devicePixelRatio > 1. (Monday, 16 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Monday, 16 February)
 
- [Bug 27310] Virtual DOM and DOM diff (Monday, 16 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Monday, 16 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Monday, 16 February)
 
- [Bug 26813] Removing parent of element that's full screen (Monday, 16 February)
 
- [Bug 27990] [D3E-key][D3E-code] "#" and "*" button of feature phones  should be defined (Monday, 16 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Monday, 16 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Monday, 16 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Monday, 16 February)
 
- [Bug 28031] Does the destination insertion points include Shadow IP  without older trees? (Monday, 16 February)
 
- [Bug 28031] Does the destination insertion points include Shadow IP  without older trees? (Monday, 16 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Monday, 16 February)
 
- [Bug 28031] Does the destination insertion points include Shadow IP  without older trees? (Monday, 16 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Monday, 16 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Monday, 16 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Monday, 16 February)
 
- [Bug 28031] Does the destination insertion points include Shadow IP  without older trees? (Monday, 16 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Monday, 16 February)
 
- [Bug 28031] New: Does the destination insertion points include  Shadow IP without older trees? (Monday, 16 February)
 
- [Bug 22141] [Shadow]: Need mechanism to tell if an element in a  ShadowRoot has been inserted into the Document (Sunday, 15 February)
 
- [Bug 28029] Mouse coordinates represented in CSS pixels do not  account for retina displays with window.devicePixelRatio > 1. (Sunday, 15 February)
 
- [Bug 28029] Mouse coordinates represented in CSS pixels do not  account for retina displays with window.devicePixelRatio > 1. (Sunday, 15 February)
 
- [Bug 28029] Mouse coordinates represented in CSS pixels do not  account for retina displays with window.devicePixelRatio > 1. (Sunday, 15 February)
 
- [Bug 28029] Mouse coordinates represented in CSS pixels do not  account for retina displays with window.devicePixelRatio > 1. (Saturday, 14 February)
 
- [Bug 28029] New: Mouse coordinates represented in CSS pixels do not  account for retina displays with window.devicePixelRatio > 1. (Saturday, 14 February)
 
- [Bug 27865] Merge fullscreen element stack into top layer (Saturday, 14 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Friday, 13 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Friday, 13 February)
 
- [Bug 20247] [Shadow]: Update constraints around stopping events (Friday, 13 February)
 
- [Bug 20247] [Shadow]: Update constraints around stopping events (Friday, 13 February)
 
- [Bug 28008] [Shadow] Should "Events that are Always Stopped" include  destination insertion points? (Friday, 13 February)
 
- [Bug 28008] [Shadow] Should "Events that are Always Stopped" include  destination insertion points? (Friday, 13 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Friday, 13 February)
 
- [Bug 28008] [Shadow] Should "Events that are Always Stopped" include  destination insertion points? (Friday, 13 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Friday, 13 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Friday, 13 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Friday, 13 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Friday, 13 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Friday, 13 February)
 
- [Bug 28008] [Shadow] Should "Events that are Always Stopped" include  destination insertion points? (Friday, 13 February)
 
- [Bug 28008] New: [Shadow] Should "Events that are Always Stopped"  include destination insertion points? (Friday, 13 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Thursday, 12 February)
 
- [Bug 26440] Allow fullscreenchange events to be synchronized with  animation frames (Thursday, 12 February)
 
- [Bug 27865] Merge fullscreen element stack into top layer (Thursday, 12 February)
 
- [Bug 27674] requestFullscreen should return a promise (Thursday, 12 February)
 
- [Bug 27931] Override 'flex' and 'transform' styling (Thursday, 12 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Thursday, 12 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Thursday, 12 February)
 
- [Bug 27775] [Shadow]: Define the behavior of *closed* shadow trees. (Thursday, 12 February)
 
- [Bug 27948] [D3E-code]: FLock vs. FnLock (Wednesday, 11 February)
 
- [Bug 27990] [D3E-key][D3E-code] "#" and "*" button of feature phones  should be defined (Wednesday, 11 February)
 
- [Bug 26019] No way to initialize modifier states except "Alt",  "Control", "Shift" and "Meta" at constructing DOM event with constructor (Wednesday, 11 February)
 
- [Bug 27991] [D3E-code] What's the good value of 0 key - 9 key of  feature phones? (Wednesday, 11 February)
 
- [Bug 27991] [D3E-code] What's the good value of 0 key - 9 key of  feature phones? (Wednesday, 11 February)
 
- [Bug 27990] [D3E-key][D3E-code] "#" and "*" button of feature phones  should be defined (Wednesday, 11 February)
 
- [Bug 27996] New: [D3E-code] KeyboardEvent code spec should have  featurephone section (Wednesday, 11 February)
 
- [Bug 27990] [D3E-key][D3E-code] "#" and "*" button of feature phones  should be defined (Wednesday, 11 February)
 
- [Bug 27991] [D3E-code] What's the good value of 0 key - 9 key of  feature phones? (Wednesday, 11 February)
 
- [Bug 27991] [D3E-code] What's the good value of 0 key - 9 key of  feature phones? (Wednesday, 11 February)
 
- [Bug 27991] [D3E-code] What's the good value of 0 key - 9 key of  feature phones? (Wednesday, 11 February)
 
- [Bug 27990] [D3E-key][D3E-code] "#" and "*" button of feature phones  should be defined (Wednesday, 11 February)
 
- [Bug 27990] [D3E-key][D3E-code] "#" and "*" button of feature phones  should be defined (Wednesday, 11 February)
 
- [Bug 27990] [D3E-key][D3E-code] "#" and "*" button of feature phones  should be defined (Tuesday, 10 February)
 
- [Bug 27991] [D3E-code] What's the good value of 0 key - 9 key of  feature phones? (Tuesday, 10 February)
 
- [Bug 27995] New: Consider adding some sort of shorthand for  resolving a promise with an IDL value (Tuesday, 10 February)
 
- [Bug 27994] [Shadow]: Distribution result usage examples (Tuesday, 10 February)
 
- [Bug 27994] [Shadow]: Distribution result usage examples (Tuesday, 10 February)
 
- [Bug 14978] [Meta]: Specify how shadow DOM works (Tuesday, 10 February)
 
- [Bug 27994] New: [Shadow]: Distribution result usage examples (Tuesday, 10 February)
 
- [Bug 27775] [Shadow]: Define the behavior of *closed* shadow trees. (Tuesday, 10 February)
 
- [Bug 27986] Specify exact length of array returned by  Navigator.getGamepads() (Tuesday, 10 February)
 
- [Bug 27986] Specify exact length of array returned by  Navigator.getGamepads() (Tuesday, 10 February)
 
- [Bug 23134] [Shadow]: createShadowRoot() should receive dictionary  to initialize flags (Tuesday, 10 February)
 
- [Bug 20144] [Shadow]: Add "closed" flag to createShadowRoot (Tuesday, 10 February)
 
- [Bug 20144] [Shadow]: Add "closed" flag to createShadowRoot (Tuesday, 10 February)
 
- [Bug 23134] [Shadow]: createShadowRoot() should receive dictionary  to initialize flags (Tuesday, 10 February)
 
- [Bug 20144] [Shadow]: Add "closed" flag to createShadowRoot (Tuesday, 10 February)
 
- [Bug 27775] [Shadow]: Define the behavior of *closed* shadow trees. (Tuesday, 10 February)
 
- [Bug 20144] [Shadow]: Add "closed" flag to createShadowRoot (Tuesday, 10 February)
 
- [Bug 20144] [Shadow]: Add "closed" flag to createShadowRoot (Tuesday, 10 February)
 
- [Bug 27775] [Shadow]: Define the behavior of *closed* shadow trees. (Tuesday, 10 February)
 
- [Bug 27991] New: [D3E-code] What's the good value of 0 key - 9 key  of feature phones? (Tuesday, 10 February)
 
- [Bug 27990] [D3E-key][D3E-code] "#" and "*" button of feature phones  should be defined (Tuesday, 10 February)
 
- [Bug 27990] [D3E-key][D3E-code] "#" and "*" button of feature phones  should be defined (Tuesday, 10 February)
 
- [Bug 27990] New: [D3E-key][D3E-code] "#" and "*" button of feature  phones should be defined (Tuesday, 10 February)
 
- [Bug 27775] [Shadow]: Define the behavior of *closed* shadow trees. (Tuesday, 10 February)
 
- [Bug 25025] Named creators with [OverrideBuiltins] don't work right  as the spec is written now (Monday,  9 February)
 
- [Bug 26521] [[GetOwnProperty]] behavior for named properties is not  web-compatible (Monday,  9 February)
 
- [Bug 26521] [[GetOwnProperty]] behavior for named properties is not  web-compatible (Monday,  9 February)
 
- [Bug 27988] Get rid of the separate concepts of "setters" and  "creators" (Monday,  9 February)
 
- [Bug 27988] New: Get rid of the separate concepts of "setters" and  "creators" (Monday,  9 February)
 
- [Bug 22808] Throw if object is constructed without new (Monday,  9 February)
 
- [Bug 22808] Throw if object is constructed without new (Monday,  9 February)
 
- [Bug 22808] Throw if object is constructed without new (Monday,  9 February)
 
- [Bug 22808] Throw if object is constructed without new (Monday,  9 February)
 
- [Bug 22808] Throw if object is constructed without new (Monday,  9 February)
 
- [Bug 22808] Throw if object is constructed without new (Monday,  9 February)
 
- [Bug 22808] Throw if object is constructed without new (Monday,  9 February)
 
- [Bug 27863] Not need to specify moving element in top layer and  fullscreen stack (Monday,  9 February)
 
- [Bug 27865] Merge fullscreen element stack into top layer (Monday,  9 February)
 
- [Bug 21434] Need to spec liveness of Gamepad objects (Monday,  9 February)
 
- [Bug 27986] Specify exact length of array returned by  Navigator.getGamepads() (Monday,  9 February)
 
- [Bug 21434] Need to spec liveness of Gamepad objects (Monday,  9 February)
 
- [Bug 27986] New: Specify exact length of array returned by  Navigator.getGamepads() (Monday,  9 February)
 
- [Bug 26181] Spec should specify the presentation of the array  returned by navigator.getGamepads() w.r.t "holes" (Monday,  9 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Monday,  9 February)
 
- [Bug 27978] [Custom]: attachedCallback has no protocol for  indicating that the custom tag is not applicable in this context (Monday,  9 February)
 
- [Bug 27976] [Custom]: type extensions should be available as custom  tags, not only through <baseTag is="..."> (Sunday,  8 February)
 
- [Bug 27976] [Custom]: type extensions should be available as custom  tags, not only through <baseTag is="..."> (Sunday,  8 February)
 
- [Bug 27975] [Custom]: No way to unregister a component (Sunday,  8 February)
 
- [Bug 27975] [Custom]: No way to unregister a component (Sunday,  8 February)
 
- [Bug 27976] [Custom]: type extensions should be available as custom  tags, not only through <baseTag is="..."> (Saturday,  7 February)
 
- [Bug 14968] [Meta]: Specify how custom elements work (Saturday,  7 February)
 
- [Bug 27978] New: [Custom]: attachedCallback has no protocol for  indicating that the custom tag is not applicable in this context (Saturday,  7 February)
 
- [Bug 14968] [Meta]: Specify how custom elements work (Saturday,  7 February)
 
- [Bug 27977] New: [Custom]: mixin pattern: custom elements should be  able to extend any base tag with is= (Saturday,  7 February)
 
- [Bug 27975] [Custom]: No way to unregister a component (Saturday,  7 February)
 
- [Bug 24578] [Custom]: define registry primitive; ("namespace"  support needed?) (Saturday,  7 February)
 
- [Bug 27975] [Custom]: No way to unregister a component (Saturday,  7 February)
 
- [Bug 27976] New: [Custom]: type extensions should be available as  custom tags, not only through <baseTag is="..."> (Saturday,  7 February)
 
- [Bug 14968] [Meta]: Specify how custom elements work (Saturday,  7 February)
 
- [Bug 14968] [Meta]: Specify how custom elements work (Saturday,  7 February)
 
- [Bug 27975] New: [Custom]: No way to unregister a component (Saturday,  7 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Saturday,  7 February)
 
- [Bug 18429] [Shadow]: Specify imperative API for node distribution (Saturday,  7 February)
 
- [Bug 24578] [Custom]: define registry primitive; ("namespace"  support needed?) (Friday,  6 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Friday,  6 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Friday,  6 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Friday,  6 February)
 
- [Bug 27775] [Shadow]: Define the behavior of *closed* shadow trees. (Friday,  6 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Thursday,  5 February)
 
- [Bug 14978] [Meta]: Specify how shadow DOM works (Thursday,  5 February)
 
- [Bug 27965] New: [Shadow]: Shadow host with tabindex=-1, all  descendent tree should be ignored for tab navigation (Thursday,  5 February)
 
- [Bug 23887] [Shadow] Put only the final destination insertion point  to the event path (Wednesday,  4 February)
 
- [Bug 27953] Dictionaries with required properties shouldn't need to  be optional (Wednesday,  4 February)
 
- [Bug 27953] Dictionaries with required properties shouldn't need to  be optional (Wednesday,  4 February)
 
- [Bug 27953] New: Dictionaries with required properties shouldn't  need to be optional (Wednesday,  4 February)
 
- [Bug 27948] New: [D3E-code]: FLock vs. FnLock (Tuesday,  3 February)
 
- [Bug 27829] [Shadow]: Update ShadowRoot to have elementsFromPoint  and caretPositionFromPoint (Monday,  2 February)
 
- [Bug 27829] [Shadow]: Update ShadowRoot to have elementsFromPoint  and caretPositionFromPoint (Monday,  2 February)
 
Last message date: Friday, 27 February 2015 15:04:11 UTC