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
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
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
Kinuko has made substantive changes  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
I meant eg, V1/dir1/file1, V2/dir1/file1.
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.
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: