Hi,
Sorry for the archaeologically late response. I'm currently documenting
FileHandle and am trying to understand how it works, so I have a couple
of questions.
I don't think this particular message received a response and I have an
unanswered interogation about it.
On Wed, Feb 29, 2012
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14842
Bug 14842 depends on bug 14591, which changed state.
Bug 14591 Summary: Get rid of Range.detach()
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14591
What|Removed |Added
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14842
Anne ann...@annevk.nl changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
It's been a month since we talked about the next publication steps for
the IDB spec (#Mins). Since then, I am not aware of any work on the
#LC-comments tracking. As such, here is a straw man proposal to move v1
forward: ...
* Forget about processing #LC-comments
* Mark all open #Bugsfor
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14694
Rafael Weinstein rafa...@chromium.org changed:
What|Removed |Added
Status|NEW |RESOLVED
As of http://dvcs.w3.org/hg/webcomponents/rev/0714c60f265d, there's now an
API to traverse the shadow trees:
http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html#api-shadow-aware-shadow-root
Does this support the previously discussed mechanism of allowing either public
or private components? I'm not able to tell from the referenced sections.
- Maciej
On Nov 28, 2012, at 1:17 PM, Dimitri Glazkov dglaz...@chromium.org wrote:
As of
On Wed, Nov 28, 2012 at 2:51 PM, Maciej Stachowiak m...@apple.com wrote:
Does this support the previously discussed mechanism of allowing either
public or private components? I'm not able to tell from the referenced
sections.
There's no private flag in place yet, I filed the bug to make
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20148
Bug ID: 20148
Summary: URLQuery interface does not handle query parameter
ordering
Classification: Unclassified
Product: WebAppsWG
Version: unspecified
Hardware: PC
