Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time

2013-10-29 Thread Simon Pieters
On Tue, 29 Oct 2013 00:54:05 +0100, Anne van Kesteren ann...@annevk.nl wrote: We are considering not throwing in XML. Only on getting innerHTML, though, right? -- Simon Pieters Opera Software

Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time

2013-10-29 Thread Anne van Kesteren
On Tue, Oct 29, 2013 at 7:34 AM, Simon Pieters sim...@opera.com wrote: On Tue, 29 Oct 2013 00:54:05 +0100, Anne van Kesteren ann...@annevk.nl wrote: We are considering not throwing in XML. Only on getting innerHTML, though, right? Oh I missed that. In that case throwing if you include text

Re: CfC: publish WD of Streams API; deadline Nov 3

2013-10-29 Thread Aymeric Vitte
I have suggested some additions/changes in my latest reply to the Overlap thread. The list of streams producers/consumers is not final but obviously WebSockets are missing. Who is coordinating each group that should get involved? MediaStream for example should be based on the Stream

CfC: publish new WD of Quota Management API; deadline November 3

2013-10-29 Thread Arthur Barstow
Kinuko has made substantive changes [1] to the Quota Management API since the FPWD was published. As such, this is a Call for Consensus to publish a new Working Draft using the ED as the basis: https://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html Agreement to this CfC: a) indicates

Re: Polished FileSystem API proposal

2013-10-29 Thread Brian Stell
I meant eg, V1/dir1/file1, V2/dir1/file1.

Re: Polished FileSystem API proposal

2013-10-29 Thread Brendan Eich
Hard links are peculiar to Unix filesystems. Not interoperable across all OSes. Symbolic links, OTOH... /be Brian Stell mailto:bst...@google.com October 29, 2013 4:53 PM I meant eg, V1/dir1/file1, V2/dir1/file1.

Re: Shadow DOM and Fallback contents for images

2013-10-29 Thread Boris Zbarsky
On 10/14/13 12:11 AM, Ryosuke Niwa wrote: If I'm not mistaken, how alternative text is presented is up to UA vendors. You're mistaken. The HTML spec actually defines the behavior here, in standards mode: it's presented as text inside a non-replaced inline (effectively as if content: