On Wed, 20 Sep 2006, Hallvord R M Steen wrote:
Opera has a serious usability problem for keyboard- and device-users
when pages do the following:
a href= onfocus=this.blur()
This coding is very common because IE adds a small outline border to
focused links. Authors who do not like this
The HTML5 draft says that authors should not use EBCDIC-based
encodings. This is more lax than saying that authors must not use and
user agents must not support CESU-8, UTF-7, BOCU-1 and SCSU.
In general, now that UTF-8 exists and is ubiquitously supported,
proliferation of encodings is
* Henri Sivonen wrote:
This makes me wonder: Do the top browsers support any EBCDIC-based
encodings but just without exposing them in the UI? If not, can there
be any notable EBCDIC-based Web content?
Internet Explorer should support any character encoding Windows supports
(see the advanced
On Jun 1, 2008, at 17:25, Bjoern Hoehrmann wrote:
* Henri Sivonen wrote:
This makes me wonder: Do the top browsers support any EBCDIC-based
encodings but just without exposing them in the UI? If not, can there
be any notable EBCDIC-based Web content?
Internet Explorer should support any
[just to whatwg]
2008/6/1 Henri Sivonen [EMAIL PROTECTED]:
Philip Taylor made a test case:
http://philip.html5.org/demos/charset/ebcdic/charsets.html
It shows that browsers that use general-purpose decoder libraries (IE and
Safari) support some EBCDIC flavors but browsers that roll their own
-Original Message-
From: Anne van Kesteren [EMAIL PROTECTED]
Sent: May 31, 2008 5:02 AM
To: Ernest Cline [EMAIL PROTECTED], WhatWG [EMAIL PROTECTED]
Subject: Re: [whatwg] Proposal for a link attribute to replace a href
On Sat, 31 May 2008 04:20:10 +0200, Ernest Cline
[EMAIL PROTECTED]
