Hi folks.
I just read through the HTML5 spec for the first time. It looks
great, and I appreciate all the hard work that everyone has done.
While reading through, I noticed a few edits that might improve
clarity. I'm posting them here in a take 'em or leave 'em fashion
-- take what you
Pressing a button when the user agent is in paused state should
cause the
button to remain pressed until the user agent wakes up and
execution of the
associated event handlers should be deferred.
So, if I had N buttons in a page, does that mean that all N could
potentially end up in a
Safari 3 for Windows raises this exception:
For the record, I've just now changed Safari (WebKit) to stop throwing
that exception, which matches Safari 2.
Geoff
We can certainly fix it, I'm just wondering what makes the most
sense to do so. Like I said, there's a patch sitting in our
(Mozilla's) bugzilla that implements the spec-compatible behaviour.
I'd be happy to fix it and relnote that it was fixed, while
providing a simple workaround (which
perhaps it would be prudent to change the spec to at least suggest
that if a database becomes known to be corrupt, operations on all
open handles to that database should start throwing
INVALID_STATE_ERR exceptions.
I think this is already specified:
3. If transaction has been marked as
perhaps it would be prudent to change the spec to at least suggest
that if a database becomes known to be corrupt, operations on
all open handles to that database should start throwing
INVALID_STATE_ERR exceptions.
I think this is already specified:
3. If transaction has been marked as
It would be nice to have a way to indicate to the script There was
a catastrophic event and we reset your database, assume you're
starting over from scratch.
In general, I'm not sure how useful it is to know that you're
starting over from scratch, since any database query needs to check
It seems to be a natural idea to save Web application state from an
unload event handler. But is it guaranteed that client-side database
API is still functional at this point? And if it is - can one queue
up more statements and/or transactions from statement callbacks?
I see two options
Since postMessage API is looking more an more like the Gears worker
messaging API (or better), can we go one step further and introduce
workers into the HTML5, defined as invisible windows with limited
capabilities:
Why call these windows at all? They seem to have no relationship
physical
Hi.
The current working draft of the XMLHttpRequest spec says the
following about responseXML and responseText.
responseText:
If the state is not LOADING or DONE raise an INVALID_STATE_ERR
exception and terminate these steps.
responseXML:
If the state is not DONE raise an
To me it just seems wrong to prevent this. This is in theory no
different than a recursive call and just like recursion it can end up
in an infinite loop.
You're right, it is no different *in theory*. It is, however,
different in practice. If we allow click() to re-enter itself, popular
I think an exception should be thrown when ApplicationCache add/
remove is called with invalid URLs.
Can you be more specific about what you mean by invalid?
URL not found in the cache?
Malformed URL?
Something else?
Geoff
My instinct is that if the community decides it is just kind of
weird, then it is a useful shorthand that we wouldn't lose anything
from standardizing on.
It is *very* weird, and therefore not a useful shorthand.
In JavaScript, delete means remove this property / interface from
this
>> This question came up in WebKit because ECMA-402’s DefaultLocale()
>> incorporates both language and locale and, to avoid confusion, we
>> wanted navigator.language, HTTP Accept-Language, and ECMA-402
>> DefaultLocale() to agree with each other.
>
> It confuses me why you would want to have
> I'm afraid that bind regional setting to interface language is not
> correct. For example, I prefer the English language interface (it's
> easier to write bug reports, search in Google documentation), but I
> need the russian regional settings (number format, date format and
> time format) for
Hi folks.
Should navigator.language and/or HTTP Accept-Language include my locale in
addition to my language — even if the combination is exotic?
For example, if I speak English but I like Polish number formatting, should
navigator.language report “en-pl”?
This question came up in WebKit
16 matches
Mail list logo
