https://www.w3.org/Bugs/Public/show_bug.cgi?id=23772
Bug ID: 23772
Summary: Just return read result when there's data
synchronously readable
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
Please see here https://github.com/whatwg/streams/issues/33, I realized
that this would apply to operations like textDecoder too without the
need of an explicit stream option, so that's no more WebCrypto only related.
Regards
Aymeric
Le 07/11/2013 11:25, Aymeric Vitte a écrit :
Le
Here’s the updated draft we’ll be discussing in Monday’s meeting. FWIW, It’s a
ground-up rewrite since last week, so it’s still loaded with todos and
editorial notes.
https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-context.html#toc
I know many of you are traveling, so if you don’t
On Fri, Nov 8, 2013 at 5:38 PM, Aymeric Vitte vitteayme...@gmail.comwrote:
Please see here https://github.com/whatwg/streams/issues/33, I realized
that this would apply to operations like textDecoder too without the need
of an explicit stream option, so that's no more WebCrypto only related.
Sorry. I've cut the input at wrong position.
textDecoderStream.write(arraybuffer of 0xd0 0xa0 0xd0 0xbe 0xd1 0x81 0xd1);
textDecoderStream.stop();
textDecoderStream.write(arraybuffer of 0x81 0xd0 0xb8 0xd1 0x8f)
I would expect Poc (stop, keep 0xd1 for the next data) and сия
It can be seen a bit different indeed, while with crypto you expect the
finalization of the operation since the begining (but only by computing
the latest bytes), here you can not expect the string since the begining
of course.
On Fri, Nov 8, 2013 at 8:54 PM, Aymeric Vitte vitteayme...@gmail.comwrote:
I would expect Poc (stop, keep 0xd1 for the next data) and сия
It can be seen a bit different indeed, while with crypto you expect the
finalization of the operation since the begining (but only by computing the
latest
Hi Art,
On Nov 7, 2013, at 9:40 AM, Arthur Barstow wrote:
Since it appears you will not be at WebApps' f2f meeting next week, I would
appreciate it if you would please summarize the status of the comment
processing, your next steps, etc. I am especially interested in whether or
not you
Hi all,
We have been discussing cross-orign use case and declarative syntax of web
components internally at Apple, and here are our straw man proposal to amend
the existing Web Components specifications to support it.
1. Modify HTML Imports to run scripts in the imported document itself
This