On Tue, Jul 30, 2013 at 10:27 PM, Takeshi Yoshino tyosh...@google.com wrote:
On Tue, Jul 30, 2013 at 12:07 PM, Jonas Sicking jo...@sicking.cc wrote:
could contain an encoding. Then when stream.readText is called, if
there's an explicit encoding, it would use that encoding when
Do you
On Tue, 30 Jul 2013, Marcos Caceres wrote:
On Tuesday, July 30, 2013 at 2:20 PM, Yves Lafon wrote:
Yes, that would be helpful (hence the report), thanks.
Done. Spec now sez:
Implementations that use ECMAScript to implement the APIs defined in this
specification must implement them in a
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21083
Bug 21083 depends on bug 21139, which changed state.
Bug 21139 Summary: Define key name for Hankaku-Zenkaku key and
Katakana-Hiragana key
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21139
What|Removed
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21083
Bug 21083 depends on bug 21119, which changed state.
Bug 21119 Summary: Define 'ZoomIn' key and 'ZoomOut' key
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21119
What|Removed |Added
On Wednesday, July 31, 2013 at 1:07 PM, Yves Lafon wrote:
Thanks, indeed the CR-PR transition was made with a test suite that was
linked to this WebIDL reference, and not the other one.
That said, if you have tests and better, a report for a stricter
conformance to WebIDL, it would be
Hey all, I was directed here by Anne helpfully posting to public-script-coord
and es-discuss. I would love it if a summary of what proposal is currently
under discussion: is it [1]? Or maybe some form of [2]?
[1]: https://rawgithub.com/tyoshino/stream/master/streams.html
[2]:
From: Anne van Kesteren [ann...@annevk.nl]
Stream.prototype.readType takes an enumerated string value which is
arraybuffer (default) or text.
Stream.prototype.read returns a promise fulfilled with the type of value
requested.
I believe this is somewhat similar to how Node streams have
On Wed, Jul 31, 2013 at 5:03 PM, Domenic Denicola
dome...@domenicdenicola.com wrote:
In this way, the encoding is a stateful aspect of the stream itself. I don't
think there's a way to get around this, without ending up with dangling
half-character bytes hanging around.
It seems though that
From: Anne van Kesteren [ann...@annevk.nl]
It seems though that if you can change the way bytes are consumed while
reading a stream you will end up with problematic scenarios. E.g. you consume
2 bytes of a 4-byte utf-8 sequence. Then switch to reading code points...
Instantiating a
FYI, this is now moved here:
https://github.com/w3ctag/spec-reviews/blob/master/2013/07/OrientationLock.md
Mounir has already addressed some of the feedback.
--
Marcos Caceres
On Friday, July 26, 2013 at 3:36 PM, Marcos Caceres wrote:
On Friday, 26 July 2013 at 12:09, Arthur Barstow
On Wed, Jul 31, 2013 at 10:17 AM, Domenic Denicola
dome...@domenicdenicola.com wrote:
From: Anne van Kesteren [ann...@annevk.nl]
It seems though that if you can change the way bytes are consumed while
reading a stream you will end up with problematic scenarios. E.g. you
consume 2 bytes of a
Hi,
The LocalFileSystem interface [1] defines the TEMPORARY and PERSISTENT
constants and has the [NoInterfaceObject] extended attribute. It seems
that the intention behind that choice was to expose these constants on
the global object (see code snippets of [3] and the fact that these are
I read quickly the thread but it seems like this is exactly the issue I
had doing [1].
The use case was just decoding utf-8 html chunked buffers and modifying
the content on the fly to stream it somewhere else.
It had to work inside browsers and with node (which as far as I know
does not
The CSS WG has published a Last Call Working Draft of the
CSS Cascading and Inheritance Module Level 3:
http://www.w3.org/TR/css-cascade-3/
This CSS module describes how to collate style rules and assign
values to all properties on all elements by way of cascading
(choosing a winning
14 matches
Mail list logo
