RE: The key custom elements question: custom constructors?

2015-07-15 Thread Travis Leithead
I've discussed this issue with some of Edge's key parser developers. From a technical ground, we do not have a problem with stopping the parser to callout to author code in order to run a constructor, either during parsing or cloning. For example, in parsing, I would expect that the callout

Re: The key custom elements question: custom constructors?

2015-07-15 Thread Olli Pettay
On 07/16/2015 03:45 AM, Domenic Denicola wrote: Hi all, Ahead of next week's F2F, I'm trying to pull together some clarifying and stage-setting materials, proposals, lists of open issues, etc. In the end, they all get blocked on one key question: **Is it OK to run author code during

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

2015-07-15 Thread 段垚
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 ?

2015-07-15 Thread Joshua Bell
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

2015-07-15 Thread bugzilla
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

2015-07-15 Thread bugzilla
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

2015-07-15 Thread bugzilla
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

2015-07-15 Thread Benjamin Kelly
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 ?

2015-07-15 Thread Jonas Sicking
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

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