On Wed, 14 Mar 2012 01:01:42 +0100, Ian Hickson i...@hixie.ch wrote:
Seems reasonable. If we have specific use cases for non-UTF-8 encodings,
I agree we should support them; if that's the case, we should survey
those
use cases to work out what the set of encodings we need is, and add just
Hi,
On Wed, Mar 14, 2012 at 06:49, Jonas Sicking jo...@sicking.cc wrote:
Something that has come up a couple of times with content authors
lately has been the desire to convert an ArrayBuffer (or part thereof)
into a decoded string. Similarly being able to encode a string into an
ArrayBuffer
On 03/14/2012 12:38 AM, Tab Atkins Jr. wrote:
On Tue, Mar 13, 2012 at 4:11 PM, Glenn Maynardgl...@zewt.org wrote:
The API on that wiki page is a reasonable start. For the same reasons that
we discussed in a recent thread (
On Wed, 14 Mar 2012 00:50:43 +0100, Joshua Bell jsb...@chromium.org
wrote:
For both of the above: initially suggested use cases included parsing
data as esoteric as ID3 tags in MP3 files, where encoding unspecified
and is
guessed at by decoders, and includes non-Unicode encodings. It was
Hi,
AFAIK, WebRTC intends to setup P2P communication between browsers, then
carry video/audio/text media, etc.
Why we need WebRTC? Firstly, Web is the most popular network app, secondly,
video/voice brings the best user experience.
But, the problem is that HTTP runs on TCP by now, while P2P runs
On Mon, 20 Feb 2012 11:01:06 +0100, Simon Pieters sim...@opera.com wrote:
...
The draft is now in a more complete state: all quirks have been specified.
http://simon.html5.org/specs/quirks-mode
--
Simon Pieters
Opera Software
On 2012-03-14 13:10, tom wrote:
Hi,
AFAIK, WebRTC intends to setup P2P communication between browsers, then
carry video/audio/text media, etc.
Why we need WebRTC? Firstly, Web is the most popular network app, secondly,
video/voice brings the best user experience.
But, the problem is that HTTP
We're having great luck in Chrome with link rel=prerender href=foo. If
that element with that rel attribute is in your document, Chrome launches a
hidden tab that we swap in and stitch into history if the user navigates
there. Navigation is as quick as switching tabs, you either join an
On Wed, 14 Mar 2012 15:35:14 -, Gavin Peters (蓋文彼德斯)
gav...@chromium.org wrote:
We're having great luck in Chrome with link rel=prerender href=foo. If
Does link rel=next href=doc2 not trigger this feature?
On 14 March 2012 14:40, Bjartur Thorlacius svartma...@gmail.com wrote:
On Wed, 14 Mar 2012 15:35:14 -, Gavin Peters (蓋文彼德斯)
gav...@chromium.org wrote:
We're having great luck in Chrome with link rel=prerender href=foo. If
Does link rel=next href=doc2 not trigger this feature?
No,
Bjartur Thorlacius skrev 2012-03-09 10:43:
I argue that putting user interface hints into a file transfer
protocol does cause problems
Would it be better if the Window-Target was somehow specified in the
head of the destination page, or is that just another way of doing the
same?
In
On Wed, 14 Mar 2012 19:59:50 -, Christian Schmidt whatwg@chsc.dk
wrote:
Bjartur Thorlacius skrev 2012-03-09 10:43:
I argue that putting user interface hints into a file transfer
protocol does cause problems
Would it be better if the Window-Target was somehow specified in the
head of
FYI, I've updated http://wiki.whatwg.org/wiki/StringEncoding
* Rewritten in terms of Anne's Encoding spec and WebIDL, for algorithms,
encodings, and encoding selection, which greatly simplifies the spec. This
implicitly adds support for all of the other encodings defined therein - we
may still
On Tue, Mar 13, 2012 at 9:47 PM, John Tamplin j...@google.com wrote:
I am fine with strongly suggesting that only UTF8 be used for new things,
but leaving out legacy support will severely limit the utility of this
library.
Not all limitations are bad, and I'd disagree with seriously.
At a
On Wed, Mar 14, 2012 at 3:53 PM, Glenn Maynard gl...@zewt.org wrote:
It's more than a naming problem. With this string API, one side of the
conversion is always a DOMString. Base64 conversion wants
ArrayBuffer-ArrayBuffer conversions, so it would belong in a separate API.
Huh. The
On 3/14/12 3:59 PM, Christian Schmidt wrote:
Bjartur Thorlacius skrev 2012-03-09 10:43:
I argue that putting user interface hints into a file transfer
protocol does cause problems
Would it be better if the Window-Target was somehow specified in the
head of the destination page
That's pretty
16 matches
Mail list logo
