On Wed, 28 May 2008, Martin Atkins wrote:
[regarding link rel=stylesheet and .disabled]
I wonder what use-case motivated that attribute that couldn't have been
satisfied by merely removing the LINK element from the DOM. Or, if you
wish to attack it from the other direction, why a generic
On Wed, 26 Nov 2008, Jim Jewett wrote:
I would name the question mark character aqt least once, so that it
can't be mistaken for a placeholder in the spec (rather than in the
SQL):
Where it now says:
Parse the first argument to the method (sqlStatement) as a SQL
statement, with the
On Fri, 27 Jun 2008, Adam Barth wrote:
In http://www.whatwg.org/specs/web-apps/current-work/#resolving, the
spec says:
If the URL to be resolved was passed to an API
The base URL is the document base URL of the script's script
document context.
I believe browsers differ on this
FWIW, in nightly Gecko builds we have an implementation of canPlayType per
spec. It parses the codecs parameter of the provided MIME type, so we can
answer no, maybe or probably depending on what's in the type. E.g.:
I've commented out the Notifications API, since there was little interest
in it, and what little interest there was was in the form of requests for
a rather complete overhaul (changing from strings to arbitary documents).
Since notifications are mostly independent of HTML anyway, I encourage
On Fri, 22 Aug 2008, Shannon wrote:
I was going to suggest the spec define unsigned integers as a value
between 1 and MAX_INT inclusive when I realised the spec doesn't define
the range of integer values at all. Is this deliberate?
Yes. The range is likely to differ based on the platform
