Cross-page locking mechanism for indexedDB/web storage/FileHandle ?

Hi all, I'm developing an web-based editor which can edit HTML documents locally (stored in indexedDB). An issue I encountered is that there is no reliable way to ensure that at most one editor instance (an instance is a web page) can open a document at the same time. * An editor instance

Re: Cross-page locking mechanism for indexedDB/web storage/FileHandle ?

Based on similar feedback, I've been noodling on this too. Here are my current thoughts: https://gist.github.com/inexorabletash/a53c6add9fbc8b9b1191 Feedback welcome - I was planning to send this around shortly anyway. On Wed, Jul 15, 2015 at 3:07 AM, 段垚 duan...@ustc.edu wrote: Hi all, I'm

[Bug 26676] Non-fullscreen documents can end up with non-empty fullscreen element stacks

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26676 Bug 26676 depends on bug 27865, which changed state. Bug 27865 Summary: Merge fullscreen element stack into top layer https://www.w3.org/Bugs/Public/show_bug.cgi?id=27865 What|Removed |Added

[Bug 27865] Merge fullscreen element stack into top layer

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27865 Anne ann...@annevk.nl changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27863] Not need to specify moving element in top layer and fullscreen stack

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27863 Bug 27863 depends on bug 27865, which changed state. Bug 27865 Summary: Merge fullscreen element stack into top layer https://www.w3.org/Bugs/Public/show_bug.cgi?id=27865 What|Removed |Added

Re: Informal Service Worker working session

On Sat, Jul 4, 2015 at 7:26 AM, Alex Russell slightly...@google.com wrote: As many SW participants are going to be in town for the WebApps F2F on the 21st, Google San Francisco is hosting a working day, 9am-5pm PST on July 20th to work through open issues and discuss future work. If you're

Re: Cross-page locking mechanism for indexedDB/web storage/FileHandle ?

Yeah, I think a standalone primitive for asynchronous atomics. The big risk is of course that deadlocks can occur, but there's no real way to completely avoid that while keeping a flexible platform. These deadlocks would be asynchronous, so no thread will hang, but you can easily end up with two

[Bug 26677] Clarify when :fullscreen applies

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26677 Philip Jägenstedt phil...@opera.com changed: What|Removed |Added Status|NEW |RESOLVED

HTML5 includes from within body

7 years ago the request to add body was blocked [1] body include src = header.html/ contentHTML5 body includes are unreadable/content /body The reason was that parser has to block while the document is loading. Is that still actual for 2015? From the user experience

[html-imports] Syntax is mystic and daunting [Was: Re: HTML5 includes from within body]

Hi Anatoly, Perhaps it would be helpful if you expanded on specific issues with the HTML Imports syntax, either on this list or using an Issue https://github.com/w3c/webcomponents/labels/html-imports. -Regards, ArtB On 7/14/15 3:32 AM, anatoly techtonik wrote: 7 years ago the request to

Re: [html-imports] Syntax is mystic and daunting [Was: Re: HTML5 includes from within body]

Hi Arthur, What is not clear in my previous mail? The non-mystic syntax is included there at the top. On Tue, Jul 14, 2015 at 1:43 PM, Arthur Barstow art.bars...@gmail.com wrote: Hi Anatoly, Perhaps it would be helpful if you expanded on specific issues with the HTML Imports syntax, either

Re: [html-imports] Syntax is mystic and daunting [Was: Re: HTML5 includes from within body]

Added an issue: https://github.com/w3c/webcomponents/issues/280 On Tue, Jul 14, 2015 at 4:48 PM, anatoly techtonik techto...@gmail.com wrote: Hi Arthur, What is not clear in my previous mail? The non-mystic syntax is included there at the top. On Tue, Jul 14, 2015 at 1:43 PM, Arthur

Re: Custom Elements: createdCallback cloning

On 07/13/2015 09:22 AM, Anne van Kesteren wrote: On Sun, Jul 12, 2015 at 9:32 PM, Olli Pettay o...@pettay.fi wrote: Well, this printing case would just clone the final flattened tree without the original document knowing any cloning happened. (scripts aren't suppose to run in Gecko's static

Re: Custom Elements: createdCallback cloning

On Jul 12, 2015, at 11:30 PM, Anne van Kesteren ann...@annevk.nl wrote: On Mon, Jul 13, 2015 at 1:10 AM, Dominic Cooney domin...@google.com wrote: Yes. I am trying to interpret this in the context of the esdiscuss thread you linked. I'm not sure I understand the problem with private state,

Re: Custom Elements: createdCallback cloning

On Sun, Jul 12, 2015 at 9:32 PM, Olli Pettay o...@pettay.fi wrote: Well, this printing case would just clone the final flattened tree without the original document knowing any cloning happened. (scripts aren't suppose to run in Gecko's static clone documents, which print preview on linux and

Re: Custom Elements: createdCallback cloning

On Mon, Jul 13, 2015 at 1:10 AM, Dominic Cooney domin...@google.com wrote: Yes. I am trying to interpret this in the context of the esdiscuss thread you linked. I'm not sure I understand the problem with private state, actually. Private state is allocated for DOM wrappers in Chromium today

Re: Custom Elements: createdCallback cloning

On 07/12/2015 08:09 PM, Anne van Kesteren wrote: On Fri, Jul 10, 2015 at 10:11 AM, Dominic Cooney domin...@google.com wrote: I think the most important question here, though, is not constructors or prototype swizzling. I guess that depends on what you want to enable. If you want to recreate

Re: Custom Elements: createdCallback cloning

On Mon, Jul 13, 2015 at 4:32 AM, Olli Pettay o...@pettay.fi wrote: On 07/12/2015 08:09 PM, Anne van Kesteren wrote: On Fri, Jul 10, 2015 at 10:11 AM, Dominic Cooney domin...@google.com wrote: I think the most important question here, though, is not constructors or prototype swizzling. I

Re: Custom Elements: createdCallback cloning

On Fri, Jul 10, 2015 at 10:11 AM, Dominic Cooney domin...@google.com wrote: I think the most important question here, though, is not constructors or prototype swizzling. I guess that depends on what you want to enable. If you want to recreate existing elements in terms of Custom Elements, you

Re: Custom Elements: createdCallback cloning

On Thu, Jul 2, 2015 at 4:05 PM, Anne van Kesteren ann...@annevk.nl wrote: In the interest of moving forward I tried to more seriously consider Dmitry's approach. Based on es-discussion discussion https://esdiscuss.org/topic/will-any-new-features-be-tied-to-constructors it seems likely new

[Bug 28938] New: Consider adding sourceDevice property to UIEvent

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28938 Bug ID: 28938 Summary: Consider adding sourceDevice property to UIEvent Product: WebAppsWG Version: unspecified Hardware: PC OS: Linux Status: NEW

Re: Custom Elements: is=

On Thu, Jul 2, 2015 at 3:59 PM, Ryosuke Niwa rn...@apple.com wrote: On Jun 13, 2015, at 4:49 PM, Léonie Watson lwat...@paciellogroup.com wrote: From: Bruce Lawson [mailto:bru...@opera.com] Sent: 13 June 2015 16:34 On 13 June 2015 at 15:30, Léonie Watson lwat...@paciellogroup.com

Re: Components F2F

Hi Mark, Mark Giffin m1...@earthlink.net, 2015-07-07 23:17 -0700: Archived-At: http://www.w3.org/mid/559cc079.6080...@earthlink.net Dimitri, this page says the F2F is on Monday July 21, but July 21 is a Tuesday. Is July 21 the correct date? Yeah, July 21 is the correct date. I changed that

Re: Components F2F

Dimitri, this page says the F2F is on Monday July 21, but July 21 is a Tuesday. Is July 21 the correct date? Mark On 7/7/2015 11:23 AM, Dimitri Glazkov wrote: Hi folks! I just updated the meeting wiki [1] with the meeting location information. tl;dr: it's the same room that we had in April.

[Bug 28924] New: Is CompositionEvent supposed to have .locale?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28924 Bug ID: 28924 Summary: Is CompositionEvent supposed to have .locale? Product: WebAppsWG Version: unspecified Hardware: PC OS: Linux Status: NEW

WBS Reminder - Registration for the F2F meeting of the Web Applications Working Group (2015-07-21/2015-07-21 in Bay Area, CA US) responses due 2015-07-14

Hello, This is an automated reminder that the following questionnaire is open until 2015-07-14: Registration for the F2F meeting of the Web Applications Working Group (2015-07-21/2015-07-21 in Bay Area, CA US) http://www.w3.org/2002/09/wbs/42538/WebComponents21July2015 W3C Staff

Re: Components F2F

Hi folks! I just updated the meeting wiki [1] with the meeting location information. tl;dr: it's the same room that we had in April. [1]: https://www.w3.org/wiki/Webapps/WebComponentsJuly2015Meeting :DG On Thu, Jul 2, 2015 at 6:01 AM, cha...@yandex-team.ru wrote: Google had offered to host

Re: Async Image - ImageData conversion

On Mon, Jul 6, 2015 at 2:38 PM, Ashley Gullen ash...@scirra.com wrote: I thought it would be more confusing to have separate competing proposals in one document? They are more like three revisions of the same document anyway, the latest one including all feedback and rationale so far:

Re: Async Image - ImageData conversion

I'm new to writing specs and when I first looked ReSpec had templates and a guide - is there something similar for the HTML standard style spec? I changed toBlob to use a dictionary (still at https://www.scirra.com/labs/specs/imagedata-conversion-extensions.html). Ashley On 7 July 2015 at

Re: Async Image - ImageData conversion

On Tue, Jul 7, 2015 at 12:24 PM, Ashley Gullen ash...@scirra.com wrote: I'm new to writing specs and when I first looked ReSpec had templates and a guide - is there something similar for the HTML standard style spec? I think you can tweak ReSpec to do the right thing, though most new

[Bug 24848] [imports]: ES6 module loader should be aware modules in HTML Imports

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24848 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 25563] [Shadow]: Define the impact of ordering on relevant HTML elements

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25563 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27835] registerElement() should be scoped to modules

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27835 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 25916] [Explainer]: Custom pseudo elements are still used in the examples.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25916 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 22409] Custom elements need da (microtask) hookup

https://www.w3.org/Bugs/Public/show_bug.cgi?id=22409 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|REOPENED|RESOLVED

[Bug 25470] [imports]: improve description of async to clarify execution order

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25470 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 24876] [Custom Elements]: Custom elements should be display: block by default

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24876 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 28543] Custom elements should call user defined constructor synchronously

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28543 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 24578] [Custom]: define registry primitive; (namespace support needed?)

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24578 Bug 24578 depends on bug 27835, which changed state. Bug 27835 Summary: registerElement() should be scoped to modules https://www.w3.org/Bugs/Public/show_bug.cgi?id=27835 What|Removed |Added

[Bug 28544] Custom elements should not upgrade elements by setting prototype

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28544 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 25319] [imports]: Want some kind of imperative API

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25319 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 26852] [Custom]: Specify preference of localName and typeExtension in createElement

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26852 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 28545] Declarative syntax for custom elements

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28545 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27611] [Custom]: SVG diagram accessibility

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27611 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[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.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26643 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

Re: [admin] Moving Custom Elements bugs to Github [Was: Re: Custom Elements bugs will be also migrated]

On 6 Jul, 2015, at 5:18 pm, Hayato Ito hay...@google.com wrote: I've finished the migration. All 141 bugs have been migrated [1]. I'll triage the migrated bugs manually later. I'm sorry that public-webapps@ has received the mass flood of bugspam mail again this time. That's

[Bug 26065] [Explainer]:

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26065 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27016] [Custom]: Custom element constructor behavior makes no sense

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27016 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27325] [Shadow]: Figure out how session history should work for iframes in shadow DOM

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27325 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 26213] Need a shadowRoots MutationObserver option

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26213 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 24603] [Custom]: Need callback for form submit data

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24603 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27751] [Custom]: suggest note on requirements

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27751 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 24178] [Custom]: No way to differentiate attribute namespaces in attributeChanged callback

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24178 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 26233] [imports]: Typo: overnride

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26233 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27366] Define how shadow DOM should be handled when host is adopted to a new document

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27366 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 28546] document.registerElement should take a template as an argument

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28546 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 25830] [Custom]: What should be the name of the generated constructor returned by registerElement?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25830 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|REOPENED|RESOLVED

[Bug 27643] [Custom]: Section 10 prototype is not defined

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27643 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 25007] [imports]: Want New LinkImport method to return a promise.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25007 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27538] [Custom]: Tone of note doesn't reflect severity

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27538 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 24398] [Explainer]: typo : should be =

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24398 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 28541] Custom elements should use ES6 class constructor

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28541 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27977] [Custom]: mixin pattern: custom elements should be able to extend any base tag with is=

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27977 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 28542] [Shadow] Replace node distribution mechanism by the named slot proposal

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28542 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27260] [Custom]: Need to define global/Realm handling for registerElement

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27260 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 24570] [Custom]: Callback for cloneNode/importNode

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24570 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27496] [Explainer]: mispell on inherifance

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27496 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 26846] [Shadow] it is unclear how elements in older shadow trees should work in case the newer shadow tree lacks shadow

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26846 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 25566] [imports]: Supporting more than just the script-src CSP directive in imports.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25566 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 24632] [meta][imports]: The spec should have fewer monkey patches

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24632 Bug 24632 depends on bug 25566, which changed state. Bug 25566 Summary: [imports]: Supporting more than just the script-src CSP directive in imports. https://www.w3.org/Bugs/Public/show_bug.cgi?id=25566 What|Removed

[Bug 24087] [Custom]: Rename document.registerElement to document.define or document.defineElement

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24087 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|REOPENED|RESOLVED

[Bug 27379] [Shadow] How should element.requestFullscreen(); work in shadow dom

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27379 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 24579] [Custom]: make callbacks more explicit

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24579 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 28051] [imports]: showing dialog from import

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28051 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 28086] [Shadow] (assuming iframes should work inside shadow DOM) Should the contentWindow objects of iframes in shadow DOM show up in window.frames?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28086 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27762] [Custom]: Make unresolved state an explicit flag.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27762 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27440] [Custom]: callbacks don't deal with exceptions

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27440 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 25669] [Custom]: Make ES6 prose normative when ES6 ships

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25669 Bug 25669 depends on bug 27405, which changed state. Bug 27405 Summary: [Custom]: Convert all ES5 references to ES6 https://www.w3.org/Bugs/Public/show_bug.cgi?id=27405 What|Removed |Added

[Bug 27405] [Custom]: Convert all ES5 references to ES6

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27405 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27914] [Custom]: Typo instantation --- instantiation

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27914 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 26656] Figure out how form owner should work in shadow dom

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26656 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 25669] [Custom]: Make ES6 prose normative when ES6 ships

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25669 Bug 25669 depends on bug 24020, which changed state. Bug 24020 Summary: [Custom]: A tag name should be associated with the constructor and not the prototype https://www.w3.org/Bugs/Public/show_bug.cgi?id=24020 What|Removed

[Bug 26583] [Custom]: Add the possibility to extend the custom element

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26583 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27375] [Shadow]: Define whether styles in shadow trees are loaded

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27375 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27768] [Custom]: Make Parsing Custom Elements section more explicit

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27768 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 25696] [imports]: link media

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25696 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 26934] [Shadow]: How should Element.requestPointerLock() work in shadow DOM?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26934 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 26898] [imports]: link rel=import shouldn't be active when added by innerHTML

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26898 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 26576] [Custom]: Add informative text about importNode

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26576 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 25669] [Custom]: Make ES6 prose normative when ES6 ships

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25669 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 26638] [Custom]: sorted element queue definition is not in sync with Imports

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26638 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 26713] DOMFocusIn/DOMFocusOut in ShadowDOM spec should be renamed to focusin/focusout

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26713 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 24042] [imports]: Parser should not wait on external resources inside imports

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24042 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|REOPENED|RESOLVED

[Bug 25610] [imports]: Want an informative section about implications of how CSP + Imports is defined

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25610 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 28449] [Shadow]: Allow certain pseudo-classes in content selectors

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28449 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 28158] [Custom]: inflexible extends as fixed element type

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28158 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 27976] [Custom]: type extensions should be available as custom tags, not only through baseTag is=...

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27976 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 26682] [imports]: The relationship between import and browsing context should be stated more clearly

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26682 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 25568] [imports]: Respect the crossOrigin attribute

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25568 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 24577] [Custom]: Need adopted callback

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24577 Hayato Ito hay...@chromium.org changed: What|Removed |Added Status|NEW |RESOLVED

<    5   6   7   8   9   10   11   12   13   14   >