[Bug 23878] Define a fetch registry

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23878

Anne  changed:

   What|Removed |Added

 Resolution|--- |MOVED
  Flags|needinfo?(i...@hixie.ch) |
 Status|NEW |RESOLVED

--- Comment #22 from Anne  ---
https://github.com/whatwg/fetch/issues/81 is the successor to this issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 24072] Clarify handling of neutered objects

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24072

Anne  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|NEW |RESOLVED

--- Comment #14 from Anne  ---
The ArrayBuffer part of this bug are actually issues with IDL:

  https://github.com/heycam/webidl/issues/151
  https://www.w3.org/Bugs/Public/show_bug.cgi?id=28798

At this point I think we should not throw for detached buffers. That will
likely cause breakage.

The Blob's close() method does not appear to be implemented:

  https://github.com/w3c/FileAPI/issues/10

So I'm not sure what we're planning on doing there. But it seems that if it's
ever implemented, making all callsites throw is going to be difficult to get
right.

With that I'm closing this bug as I don't think there's anything to be done
here in Fetch and XMLHttpRequest.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 26153] Allow ArrayBuffer as argument to send()

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26153
Bug 26153 depends on bug 24072, which changed state.

Bug 24072 Summary: Clarify handling of neutered objects
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24072

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 26917] For any chunk, progress event should be fired at least in 50ms since the arrival of the chunk

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26917

Anne  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #9 from Anne  ---
If you still want to change this, let's discuss it on GitHub.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 12837] Define unloading document cleanup steps

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=12837

Anne  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|NEW |RESOLVED

--- Comment #22 from Anne  ---
Demos still work for me.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 25589] To improve readability, set response to null rather than network error

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25589

Anne  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|NEW |RESOLVED

--- Comment #1 from Anne  ---
No longer convinced this is worth it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 28505] Synchronous XHR removal makes patching Error.prepareStackTrace impossible

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28505

Anne  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|NEW |RESOLVED

--- Comment #2 from Anne  ---
If this continuous to be a problem, please contribute to this thread on GitHub:
https://github.com/whatwg/xhr/issues/20

Thanks!

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 20322] Upload progress events vs CORS

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=20322

Anne  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #22 from Anne  ---
I just went with what implementations do for now:
https://github.com/whatwg/xhr/commit/667d4f3604aaee4e24bde33ed487cf8a98274e70

Basically always require listeners upfront...

I also submitted a correction for Hallvord's test based on what implementations
do today: https://github.com/w3c/web-platform-tests/pull/3451

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 23780] Check XMLHttpRequest and Notification don' t break given the new script settings object stuff

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23780
Bug 23780 depends on bug 18242, which changed state.

Bug 18242 Summary: Not clear what "script that invoked the method" means 
exactly in the case of e.g. a.setTimeout(b.postMessage, 0) // called from c
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18242

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 13913] Attributes don't have an order

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=13913

Anne  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #4 from Anne  ---
Per bug 17871 they have a deterministic order, although it will take some time
for implementations to converge.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 13913] Attributes don't have an order

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=13913
Bug 13913 depends on bug 17871, which changed state.

Bug 17871 Summary: Element attributes should not be required to be stored in an 
ordered list
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17871

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 24732] Remove DOMError from FileAPI

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24732

Aryeh Gregor  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||a...@aryeh.name
 Resolution|--- |MOVED

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 24106] FKA: No defined way to get keyboard focus into and out of a shadow DOM component

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24106
Bug 24106 depends on bug 23870, which changed state.

Bug 23870 Summary: FKA: No defined way to get keyboard focus into and out of a 
shadow DOM component
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23870

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 9514] [Selection] Specify Selection.modify()

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=9514

Ryosuke Niwa  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |MOVED

--- Comment #10 from Ryosuke Niwa  ---
This is now tracked by https://github.com/w3c/selection-api/issues/37.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29506] Support for a system-wide configuration file to specify permissions for web-applications

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29506

Anne  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |INVALID

--- Comment #10 from Anne  ---
There's no such thing as an installable web application. Also, please stop
reopening the bug. This is not an issue with XMLHttpRequest.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29506] Support for a system-wide configuration file to specify permissions for web-applications

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29506

sworddrag...@aol.com changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |---

--- Comment #9 from sworddrag...@aol.com ---
Shops are no requirements especially for desktop-PC's but I'm seeing what you
are pointing to. But that means that you are telling me that there is no
intention to make installable web-applications competitive to native system
applications. This is a valid decision but I want to go sure that I'm not
missing something here.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29506] Support for a system-wide configuration file to specify permissions for web-applications

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29506

Anne  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |INVALID
  Flags|needinfo?(ann...@annevk.nl) |

--- Comment #8 from Anne  ---
The problem with that model is that it requires installation. And if something
requires installation and needs to be trusted it needs to be distributed
through a store. And stores are antithetical to the web.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29506] Support for a system-wide configuration file to specify permissions for web-applications

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29506

sworddrag...@aol.com changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 CC||ann...@annevk.nl
 Resolution|INVALID |---
  Flags||needinfo?(ann...@annevk.nl)

--- Comment #7 from sworddrag...@aol.com ---
A small ping, since I would really like to try to enhance something here. Based
on the post above can you give me a use-case why this would be a problem? So I
could think about it and maybe propose another solution or give up if I don't
see another one. Or have I maybe indeed found a way to make this at least for
trusted file:// applications possible?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 26365] [Shadow]: Need an equivalent definition of 'in a Document' for shadow trees

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26365
Bug 26365 depends on bug 27406, which changed state.

Bug 27406 Summary: Update HTML to take into account shadow DOM implications
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27406

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 28841] Incorporate changes suggested by Mixed Content

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28841

Anne  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 CC||ann...@annevk.nl
 Resolution|--- |MOVED

--- Comment #3 from Anne  ---
See https://github.com/whatwg/fetch/issues/235 for a new solution.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 21652] Should structured clone support FormData?

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21652

Anne  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #4 from Anne  ---
https://github.com/whatwg/xhr/issues/55

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 28841] Incorporate changes suggested by Mixed Content

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28841

Domenic Denicola  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|MOVED   |---

--- Comment #2 from Domenic Denicola  ---
Turns out this is part of a larger problem and can't be solved with a simple
HTML pull request; see https://github.com/whatwg/html/pull/222 discussion.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29506] Support for a system-wide configuration file to specify permissions for web-applications

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29506

Anne  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |INVALID

--- Comment #3 from Anne  ---
That is intentional. Please study the web's security model.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29506] Support for a system-wide configuration file to specify permissions for web-applications

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29506

sworddrag...@aol.com changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WONTFIX |---

--- Comment #2 from sworddrag...@aol.com ---
It is not only about XMLHttpRequest (there was just no suitable component so I
have choosen XHR from the list). This feature is about to make web applications
more competitive to native applications as currently they are very limited. For
example it is not possible to do network requests to fetch any data (and CORS
does not solve this problem as it gives the control to the service provider).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29506] Support for a system-wide configuration file to specify permissions for web-applications

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29506

Anne  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #1 from Anne  ---
We won't be adding new features to XMLHttpRequest. Certainly none that complex.
Sorry.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29506] New: Support for a system-wide configuration file to specify permissions for web-applications

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29506

Bug ID: 29506
   Summary: Support for a system-wide configuration file to
specify permissions for web-applications
   Product: WebAppsWG
   Version: unspecified
  Hardware: All
OS: All
Status: NEW
  Severity: enhancement
  Priority: P2
 Component: XHR
  Assignee: ann...@annevk.nl
  Reporter: sworddrag...@aol.com
QA Contact: public-webapps-bugzi...@w3.org
CC: m...@w3.org, public-webapps@w3.org
  Target Milestone: ---

Initially I have reported this here (
https://github.com/w3c-webmob/installable-webapps/issues/52 ) but since the
group has closed I'm forwarding it to here. Here is a copy of the original
report:



At Mozilla's bugzilla a discussion woke up (
https://bugzilla.mozilla.org/show_bug.cgi?id=424875 ) to make XMLHttpRequest
useable for web-applications on the file-protocol without requiring the server
to enable CORS. At the end of the current discussion I got the idea of a
system-wide configuration file to solve this issue:

- It contains permissions it grants to web-applications (for example
specific/all permissions on specific files/directories).
- Installer invoked by the user can write the required permissions for their
web-application to this file. Also the user can enter manually entries if he
wants.
- A site launched unintentionally on the file-protocol can't do evil things
since it wouldn't be listed in this file.


This would help to make web-applications launched on the file-protocol (for
example installed by upstream-installers on desktop-PC's) to be more
competitive.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29397] [imports]: Typo: s/altorighm/algorithm

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29397

Domenic Denicola  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||d...@domenic.me
 Resolution|--- |MOVED

--- Comment #1 from Domenic Denicola  ---
HTML imports tracks their issues at https://github.com/w3c/webcomponents/

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 28373] FilePropertyBag can inherit from BlobPropertyBag

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28373

Simon Pieters  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 22059] Composition dictionary should be changed

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=22059

Arthur Barstow  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 CC||art.bars...@gmail.com
 Resolution|--- |MOVED

--- Comment #17 from Arthur Barstow  ---
This bug was moved to 

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 14828] Import Hixie's tests?

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=14828

Arthur Barstow  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||art.bars...@gmail.com
 Resolution|--- |MOVED

--- Comment #3 from Arthur Barstow  ---
This bug has been duplicated as
https://github.com/w3c/web-platform-tests/issues/2230

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 15279] Update WebSockets tests to remove support for MozWebSocket

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=15279

Ms2ger  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 19771] Need way to determine what keys are supported on device.

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=19771

Gary Kacmarcik  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #3 from Gary Kacmarcik  ---
Tracking as github issue: https://github.com/w3c/uievents/issues/8

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 26813] Removing parent of element that's full screen

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26813

Anne  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||ann...@annevk.nl
 Resolution|--- |MOVED

--- Comment #13 from Anne  ---
https://github.com/whatwg/html/pull/230

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 21083] Proposal key names for Android

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21083

Gary Kacmarcik  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #9 from Gary Kacmarcik  ---
Now tracking as: https://github.com/w3c/uievents/issues/9

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 21121] Define mobile phone related keys

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21121

Gary Kacmarcik  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #3 from Gary Kacmarcik  ---
Now tracking as: https://github.com/w3c/uievents/issues/11

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 21083] Proposal key names for Android

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21083
Bug 21083 depends on bug 21121, which changed state.

Bug 21121 Summary: Define mobile phone related keys
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21121

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 21083] Proposal key names for Android

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21083
Bug 21083 depends on bug 21137, which changed state.

Bug 21137 Summary: Define key names for game controller of Android
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21137

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 22569] MouseEvent should have DOMString pseudoElement property like TransitionEvent

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=22569

Gary Kacmarcik  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #5 from Gary Kacmarcik  ---
Now tracking as: https://github.com/w3c/uievents/issues/15

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 22891] Mechanism to differentiate pointer input from multiple users/devices missing

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=22891

Gary Kacmarcik  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #3 from Gary Kacmarcik  ---
Now tracking as: https://github.com/w3c/uievents/issues/16

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 23259] Expose ticks in wheel events

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23259

Gary Kacmarcik  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #2 from Gary Kacmarcik  ---
Now tracking as: https://github.com/w3c/uievents/issues/17

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 25485] D3E and corelation with DOM4(W3C)/DOM(WHATWAG) and DOM3 Core

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25485

Gary Kacmarcik  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||gary...@google.com
 Resolution|--- |MOVED

--- Comment #7 from Gary Kacmarcik  ---
Now tracking as: https://github.com/w3c/uievents/issues/19

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 21120] Define TV or A/V remote controller's keys

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21120

Gary Kacmarcik  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #6 from Gary Kacmarcik  ---
Now tracking as: https://github.com/w3c/uievents/issues/10

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 21083] Proposal key names for Android

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21083
Bug 21083 depends on bug 21120, which changed state.

Bug 21120 Summary: Define TV or A/V remote controller's keys
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21120

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 21136] Define Home key and Back key of Android smartphone

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21136

Gary Kacmarcik  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #3 from Gary Kacmarcik  ---
Now tracking as: https://github.com/w3c/uievents/issues/12

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 21083] Proposal key names for Android

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21083
Bug 21083 depends on bug 21136, which changed state.

Bug 21136 Summary: Define Home key and Back key of Android smartphone
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21136

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 21137] Define key names for game controller of Android

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21137

Gary Kacmarcik  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #10 from Gary Kacmarcik  ---
Now tracking as: https://github.com/w3c/uievents/issues/13

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 21830] KeyboardEvent.locale is too general.

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21830

Gary Kacmarcik  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #5 from Gary Kacmarcik  ---
Now tracking as: https://github.com/w3c/uievents/issues/14

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 23907] How do web apps distinguish if a keydown event causes text input?

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23907

Gary Kacmarcik  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #2 from Gary Kacmarcik  ---
Now tracking as: https://github.com/w3c/uievents/issues/18

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 23575] The paragraph about patent policy is duplicated.

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23575

Arthur Barstow  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||art.bars...@gmail.com
 Resolution|--- |FIXED

--- Comment #4 from Arthur Barstow  ---
This is fixed via
https://github.com/w3c/websockets/commit/8ca812f5f28694e1c148e46062b3a74c3beb4be4

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 27108] Push API should be allowed without dependency on service worker

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27108

Arthur Barstow  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #6 from Arthur Barstow  ---
This bug has been moved to a Github issue
.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 14214] missing definition of Transferable

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=14214

Arthur Barstow  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Arthur Barstow  ---
The 24-Sept-2015 WD of Web Workers
 has two references to the
Transferable object as defined in HTML5
. Given
this, I think we can consider this bug as fixed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 28823] Course of action even after Event Source retry failure.

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28823

Anne  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #4 from Anne  ---
https://github.com/whatwg/html/pull/226

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 27915] Clients of WebSockets are not NTP synced (and there is no NTP-alike spec)

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27915

Domenic Denicola  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||d...@domenic.me
 Resolution|--- |WORKSFORME

--- Comment #2 from Domenic Denicola  ---
Markings as resolved per comment 1's

> Browsers rely on the system clock. Most (all?) systems I deal with these days 
> have system clocks driven by NTP. What systems don't?

and

> You can replace Date.now by saying:

Let us know if you disagree and we can reopen.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 28841] Incorporate changes suggested by Mixed Content

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28841

Domenic Denicola  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||d...@domenic.me
 Resolution|--- |MOVED

--- Comment #1 from Domenic Denicola  ---
https://github.com/whatwg/html/pull/222

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 25097] Update HTTP and HTTPAUTH references to new HTTPbis specs

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25097

Anne  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

--- Comment #8 from Anne  ---
Still does not seem obsoleted. Please file an issue on GitHub once it is.
Leaving this as fixed per comment 6.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29136] New: Keyboard events should specify their target when more than 1 document exists

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29136

Bug ID: 29136
   Summary: Keyboard events should specify their target when more
than 1 document exists
   Product: WebAppsWG
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P2
 Component: UI Events
  Assignee: gary...@google.com
  Reporter: jyass...@gmail.com
QA Contact: public-webapps-bugzi...@w3.org
CC: m...@w3.org, public-webapps@w3.org
  Target Milestone: ---

https://w3c.github.io/uievents/#event-type-keydown defines Event.target as
"focused element processing the key event or if no element focused, then the
body element if available, otherwise the root element". However, "the body
element" and "the root element" aren't uniquely defined within a UA. The UA may
have multiple browsing contexts, and each browsing context can contain multiple
documents.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24632
Bug 24632 depends on bug 24637, which changed state.

Bug 24637 Summary: [imports] "style sheet that is blocking scripts" should be 
generalized to support HTML Imports
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24637

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |LATER

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29103] New: MediaStream Recording API: MediaRecorderErrorEvent is a NoInterfaceObject, consider removing

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29103

Bug ID: 29103
   Summary: MediaStream Recording API: MediaRecorderErrorEvent is
a NoInterfaceObject, consider removing
   Product: WebAppsWG
   Version: unspecified
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P2
 Component: Streams API
  Assignee: tyosh...@google.com
  Reporter: mca...@chromium.org
QA Contact: public-webapps-bugzi...@w3.org
CC: m...@w3.org, public-webapps@w3.org
  Target Milestone: ---

MediaRecorderErrorEvent [1] idl says it's  NoInterfaceObject,
consider removing it.

[1] http://www.w3.org/TR/mediastream-recording/#MediaRecorderErrorEvent

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29104] New: BlobEvent is defined in both MediaStream Recorder and MediaStream ImageCapture, consider factoring them out.

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29104

Bug ID: 29104
   Summary: BlobEvent is defined in both MediaStream Recorder and
MediaStream ImageCapture, consider factoring them out.
   Product: WebAppsWG
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P2
 Component: Streams API
  Assignee: tyosh...@google.com
  Reporter: mca...@chromium.org
QA Contact: public-webapps-bugzi...@w3.org
CC: m...@w3.org, public-webapps@w3.org
  Target Milestone: ---

In [1] and [2], respectively.

[1] http://www.w3.org/TR/mediastream-recording/#blob-event
[2] http://www.w3.org/TR/image-capture/#blobevent

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29105] New: MediaStream Recording API: Consider not using BlobEvent, using Blob and FileReader instead

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29105

Bug ID: 29105
   Summary: MediaStream Recording API: Consider not using
BlobEvent, using Blob and FileReader instead
   Product: WebAppsWG
   Version: unspecified
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P2
 Component: Streams API
  Assignee: tyosh...@google.com
  Reporter: mca...@chromium.org
QA Contact: public-webapps-bugzi...@w3.org
CC: m...@w3.org, public-webapps@w3.org
  Target Milestone: ---

MS Recording API defines a certain BlobEvent as a way to
read the recorded data [1]. 

Since BlobEvent is just a convenience wrapper around a 
Blob [2], consider using the latter for extracting recorded
data.

[1] http://www.w3.org/TR/mediastream-recording/#blob-event
[2] http://www.w3.org/TR/FileAPI/#blob

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29102] MediaStream Recording API: remove RecordingErrorNameEnum and use DomException instead

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29102

Miguel Casas-Sanchez  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29103] MediaStream Recording API: MediaRecorderErrorEvent is a NoInterfaceObject, consider removing

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29103

Miguel Casas-Sanchez  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29104] BlobEvent is defined in both MediaStream Recorder and MediaStream ImageCapture, consider factoring them out.

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29104

Miguel Casas-Sanchez  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29105] MediaStream Recording API: Consider not using BlobEvent, using Blob and FileReader instead

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29105

Miguel Casas-Sanchez  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Miguel Casas-Sanchez  ---
Dup'ed in https://github.com/w3c/mediacapture-record/issues/17

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 29068] New: Should not reocmmend DocumentEvent.createEvent

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29068

Bug ID: 29068
   Summary: Should not reocmmend DocumentEvent.createEvent
   Product: WebAppsWG
   Version: unspecified
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: normal
  Priority: P2
 Component: UI Events
  Assignee: gary...@google.com
  Reporter: d...@domenic.me
QA Contact: public-webapps-bugzi...@w3.org
CC: m...@w3.org, public-webapps@w3.org
  Target Milestone: ---

To create an instance of the KeyboardEvent interface, use the
DocumentEvent.createEvent(KeyboardEvent) method call. 

You should recommend using new KeyboardEvent instead. DocumentEvent doesn't
even exist.

This problem also occurs with CompositionEvent.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 28967] New: Legacy appendices should be normative

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28967

Bug ID: 28967
   Summary: Legacy appendices should be normative
   Product: WebAppsWG
   Version: unspecified
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P2
 Component: UI Events
  Assignee: gary...@google.com
  Reporter: ms2...@gmail.com
QA Contact: public-webapps-bugzi...@w3.org
CC: m...@w3.org, public-webapps@w3.org

Browsers need to implement them, so there's no reason to make them informative.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 27674] requestFullscreen should return a promise

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27674

Anne ann...@annevk.nl changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #33 from Anne ann...@annevk.nl ---
https://github.com/whatwg/fullscreen/commit/fd19ec7a0f35e09b0cc4de0f676d37f6bd480560
https://github.com/whatwg/fullscreen/commit/d316cce76a5a5dad073425b973dd529dfa0d2a1a

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 28459] Algorithm of exitFullscreen() doesn't work correctly when there are nested fullscreen element

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28459

Anne ann...@annevk.nl changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Anne ann...@annevk.nl ---
https://github.com/whatwg/fullscreen/commit/67fb879087d646178857fd5fc7312b662b9a8999

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26676

Anne ann...@annevk.nl changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #7 from Anne ann...@annevk.nl ---
https://github.com/whatwg/fullscreen/commit/3dba602d0f0864e0058a29a9cb88c8471a593789

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 27162] Browser differences in graphical layout of fullscreen mode.

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27162

Anne ann...@annevk.nl changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 28614] Weaken the requirement of the time of running async steps

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28614

Anne ann...@annevk.nl changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #7 from Anne ann...@annevk.nl ---
Yeah, Philip is correct. Resize can already take any amount of time.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[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

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 27865] Merge fullscreen element stack into top layer

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27865

Anne ann...@annevk.nl changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #12 from Anne ann...@annevk.nl ---
https://github.com/whatwg/fullscreen/commit/766dc872bcf26c012549f7bdfde21c46bebba40c
was the last commit needed here I think.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[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

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 26677] Clarify when :fullscreen applies

[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
 Resolution|--- |FIXED

--- Comment #4 from Philip Jägenstedt phil...@opera.com ---
The spec now says what I asked for: The :fullscreen pseudo-class must match
any element that is that element's node document's fullscreen element.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

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
  Severity: normal
  Priority: P2
 Component: UI Events
  Assignee: gary...@google.com
  Reporter: rby...@chromium.org
QA Contact: public-webapps-bugzi...@w3.org
CC: m...@w3.org, public-webapps@w3.org

Concrete proposal: http://rbyers.github.io/InputDevice/inputdevice.html

There's been a bit of support on www-dom for this (including from Gary):
https://lists.w3.org/Archives/Public/www-dom/2015JanMar/0120.html, but not much
discussion.

We're pretty close to doing an intent-to-ship for blink on this, so it would be
great if we could decide whether there is interest in adding this to UI Events
(or possibly some other spec).

If there's interest, I'm happy to create a pull request.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

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
  Severity: normal
  Priority: P2
 Component: UI Events
  Assignee: gary...@google.com
  Reporter: b...@pettay.fi
QA Contact: public-webapps-bugzi...@w3.org
CC: m...@w3.org, public-webapps@w3.org

It is not clear how CompositionEvent should behave per current draft.
Should it have .locale property which is then initialized for example using
the legacy initCompositionEvent?
And should the dictionary for ctor have locale too?

Some version of some spec (I'm getting lost with D3E, UIEvents and
UIEventsExtensions) had .locale in KeyboardEvent.


Anyhow, since .locale is there for initCompositionEvent, I'll add it to the
dictionary too in Gecko. Guess work here.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24848

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #5 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/223

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25563

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #3 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/183

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27835

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #2 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/156

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25916

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #1 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/208

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=22409

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |MOVED

--- Comment #3 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/225

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25470

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #6 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/218

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24876

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #4 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/224

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28543

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #1 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/137

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

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

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28544

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #9 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/134

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25319

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #3 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/141

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26852

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #1 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/167

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 28545] Declarative syntax for custom elements

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28545

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #1 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/136

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 27611] [Custom]: SVG diagram accessibility

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27611

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #2 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/170

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26643

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #9 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/199

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 26065] [Explainer]:

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26065

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #1 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/206

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27016

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #5 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/189

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27325

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #7 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/184

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 26213] Need a shadowRoots MutationObserver option

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26213

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #5 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/204

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24603

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #6 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/187

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27751

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #1 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/166

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24178

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #12 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/168

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 26233] [imports]: Typo: overnride

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26233

Hayato Ito hay...@chromium.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #1 from Hayato Ito hay...@chromium.org ---
Moved to https://github.com/w3c/webcomponents/issues/205

-- 
You are receiving this mail because:
You are on the CC list for the bug.