L. David Baron on Wed Nov 30 18:29:31 PST 2011:
On Wednesday 2011-11-30 15:28 -0800, Faruk Ates 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. But how relevant
is that
(And HTML5 defines it the same.)
No. As far as I understand, HTML5 defines US-ASCII to be the default and
requires that any other encoding is explicitly declared. I do like this
approach.
We should also lobby for authoring tools (as recommended by HTML5) to
default their output to UTF-8 and
(And HTML5 defines it the same.)
No. As far as I understand, HTML5 defines US-ASCII to be the default and
requires that any other encoding is explicitly declared. I do like this
approach.
We are here discussing the default *user agent behaviour* - we are not
specifically discussing how web
I can't find a definitive answer for the following scenario:
1 - A page has a plug-in with fallback specified as follows:
object type=application/x-shockwave-flash
param name=movie value=Example.swf/
img src=Fallback.png
/object
2 - The page is loaded, the browser instantiates the plug-in,
On 12/5/11 12:42 PM, Leif Halvard Silli wrote:
Last I checked, some of those locales defaulted to UTF-8. (And HTML5
defines it the same.) So how is that possible?
Because authors authoring pages that users of those locales tend to use
use UTF-8 more than anything else?
Don't users of those
Boris Zbarsky Mon Dec 5 13:49:45 PST 2011:
On 12/5/11 12:42 PM, Leif Halvard Silli wrote:
Last I checked, some of those locales defaulted to UTF-8. (And HTML5
defines it the same.) So how is that possible?
Because authors authoring pages that users of those locales
tend to use use UTF-8
On Fri, 02 Dec 2011 15:50:31 -, Henri Sivonen hsivo...@iki.fi wrote:
That compatibility mode already exists: It's the default mode--just
like the quirks mode is the default for pages that don't have a
doctype. You opt out of the quirks mode by saying !DOCTYPE html. You
opt out of the
On Dec 5, 2011, at 4:10 PM, Kornel Lesiński wrote:
Could !DOCTYPE html be an opt-in to default UTF-8 encoding?
It would be nice to minimize number of declarations a page needs to include.
I like that idea. Maybe it’s not too late.
-- Darin
On 12/5/11 6:14 PM, Leif Halvard Silli wrote:
It is more likely that there is another reason, IMHO: They may have
tried it, and found that it worked OK
Where by it you mean open a text editor, type some text, and save.
So they get whatever encoding their OS and editor defaults to.
And yes,
On 12/5/11 6:14 PM, Leif Halvard Silli wrote:
It is more likely that there is another reason, IMHO: They may have
tried it, and found that it worked OK
Where by it you mean open a text editor, type some text, and save.
So they get whatever encoding their OS and editor defaults to.
If that
On 12/5/11 9:55 PM, Leif Halvard Silli wrote:
If that is all they tested, then I'd said they did not test enough.
That's normal for the web.
(For the record, reading a particular page in a language is a much
simpler task than reading the language; I can't read German, but I can
certainly
Boris Zbarsky Mon Dec 5 19:18:10 PST 2011:
On 12/5/11 9:55 PM, Leif Halvard Silli wrote:
I said I agreed with him that Faruk's solution was not good. However, I
would not be against treating DOCTYPE html as a 'default to UTF-8'
declaration
This might work, if there hasn't been too much
On Mon, 05 Dec 2011 22:19:33 +0100, Brady Eidson beid...@apple.com wrote:
I can't find a definitive answer for the following scenario:
1 - A page has a plug-in with fallback specified as follows:
object type=application/x-shockwave-flash
param name=movie value=Example.swf/
img
I wrote some somewhat goofy text in the CSP spec trying to integrate
the sandbox directive with HTML's iframe sandbox machinery. Hixie and
I chatted in #whatwg about how best to do the integration. I think
Hixie is going to refactor the machinery in the spec to be a bit more
generic and to call
Hi all,
I've added more examples to the document:
http://rniwa.com/editing/undomanager.html and also requested feedback on
public-webapps. As of this revision, I consider the specification is ready
for implementation feedback. I will start prototyping it for WebKit and
start writing tests.
I
15 matches
Mail list logo
