On Wed, 30 Nov 2011 21:29:31 -0500, L. David Baron dba...@dbaron.org
wrote:
I changed my Firefox from the ISO-8859-1 default to UTF-8 years ago
(by changing the intl.charset.default preference)
Just to add, in Opera, you can goto Ctrl + F12 - General tab - Language
section - Details and
I guess I may be confused.
I see two ways of rendering VTT (at least):
1) the UA interprets only VTT, and chooses 'suitable' fonts etc.
2) the UA interprets VTT with class markups and an associated CSS style sheet
or sheets, and the author and the UA between them can go hog wild.
In case (2),
On Fri, 02 Dec 2011 01:34:15 +0100, Ian Hickson i...@hixie.ch wrote:
If we are to add language information to the language, there's four ways
to do it: inline, cue-level, block-level (a section of the file, e.g.
setting a default at different points in the file), and file-level.
Inline would
On Fri, 02 Dec 2011 01:34:15 +0100, Ian Hickson i...@hixie.ch wrote:
On Wed, 5 Oct 2011, Simon Pieters wrote:
I did some research on authoring errors in SRT timestamps to inform
whether WebVTT parsing of timestamps should be changed.
Thanks!
I sent a reply, but my message was too big for
On Fri, 02 Dec 2011 12:07:36 +0100, Simon Pieters sim...@opera.com wrote:
On Fri, 02 Dec 2011 01:34:15 +0100, Ian Hickson i...@hixie.ch wrote:
On Wed, 5 Oct 2011, Simon Pieters wrote:
I did some research on authoring errors in SRT timestamps to inform
whether WebVTT parsing of timestamps
Thanks for your advice. I have submitted :-
- https://www.w3.org/Bugs/Public/show_bug.cgi?id=15041 to request the
spec be clarified in this regard.
- https://www.w3.org/Bugs/Public/show_bug.cgi?id=15042 to request the
test to be updated to cope with higher resolution backing stores.
Should I cc
On Dec 2, 2011, at 11:58 , Simon Pieters wrote:
On Fri, 02 Dec 2011 01:34:15 +0100, Ian Hickson i...@hixie.ch wrote:
If we are to add language information to the language, there's four ways
to do it: inline, cue-level, block-level (a section of the file, e.g.
setting a default at different
On Fri, 02 Dec 2011 14:38:13 +0100, David Singer sin...@apple.com wrote:
On Dec 2, 2011, at 11:58 , Simon Pieters wrote:
On Fri, 02 Dec 2011 01:34:15 +0100, Ian Hickson i...@hixie.ch wrote:
If we are to add language information to the language, there's four
ways
to do it: inline,
On Thu, Dec 1, 2011 at 1:28 AM, Faruk Ates faruka...@me.com wrote:
My understanding is that all browsers* default to Western Latin (ISO-8859-1)
encoding by default (for Western-world downloads/OSes) due to legacy content
on the web.
As has already been pointed out, the default depends varies
On Thu, Dec 1, 2011 at 8:29 PM, Brett Zamir bret...@yahoo.com wrote:
How about a Compatibility Mode for the older non-UTF-8 character set
approach, specific to page?
That compatibility mode already exists: It's the default mode--just
like the quirks mode is the default for pages that don't have
On Fri, Dec 2, 2011 at 10:46 AM, Henri Sivonen hsivo...@iki.fi wrote:
Regarding your (and 16) remark, considering my personal happiness at
work, I'd prioritize the eradication of UTF-16 as an interchange
encoding much higher than eradicating ASCII-based non-UTF-8 encodings
that all major
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/12/11 05:38 AM, David Singer wrote:
Very. Correct rendering of some text requires that it be correctly
labelled with a BCP-47 tag, as I understand.
For me, file-level default/overall setting, with the possibility of
span-based
On Fri, Dec 2, 2011 at 4:03 AM, David Singer sin...@apple.com wrote:
I guess I may be confused.
I see two ways of rendering VTT (at least):
1) the UA interprets only VTT, and chooses 'suitable' fonts etc.
Without language metadata, this is impossible to do reliably for CJK text.
2) the UA
Hi all,
Currently HTML5 defines that a script src=... element that is
inserted into the DOM should always execute if the load succeeds. Even
the the element is removed from the Document before it is executed.
See
On Fri, Dec 2, 2011 at 11:27 AM, Jonas Sicking jo...@sicking.cc wrote:
The main use case for wanting to support scripts getting appears to be
wanting to abort JSONP loads. Potentially to issue it with new
parameters. This is a decent use case, but given the racyness
described above in webkit,
On 12/2/11 2:27 PM, Jonas Sicking wrote:
Gecko currently follows the spec, but is the only browser that does
so. We are not aware of any sites that break because of this.
To be more precise, the only issues we know of are
On Fri, Dec 2, 2011 at 2:27 PM, Jonas Sicking jo...@sicking.cc wrote:
The main use case for wanting to support scripts getting appears to be
wanting to abort JSONP loads. Potentially to issue it with new
parameters. This is a decent use case, but given the racyness
described above in webkit,
I include below, for posterity, some feedback to which I will not be
replying, as it relates to the PeerConnection and media streams section of
the specification which has since been moved to the WebRTC working group
at the W3C.
I encourage anyone who is interested in that particular topic to
Hi all,
Several days ago, we had a discussion about improving DOM performance on
#whatwg where I hypothesized that most of nodes inserted by methods like
insertBefore, appendChild, etc... don't have any children, and therefore we
can bypass checks for HIERARCHY_REQUEST_ERR by just checking the
19 matches
Mail list logo
