On Mon, 26 Oct 2009, Shumpei Shiraishi wrote:
I'm sorry for delay of replying and thanks for your post very much.
Here you want to put the preventDefault() after the for() loop, so
that it cancels the event only if the type was not found.
Mmm, it seems my mistake about understanding
On Mon, 26 Oct 2009, Simon Pieters wrote:
Web Workers has the following in some example (twice):
// support being used as a shared worker as well as a dedicated worker
if (this.onmessage) // dedicated worker
This ought to be doing something like (typeof this.onmessage !=
Ian Hickson schrieb:
On Sun, 25 Oct 2009, Markus Ernst wrote:
The spec says in 3.2.3: The following event handler content attributes
may be specified on any HTML element - with my quite trivial
understanding, I would actually expect something to happen if I do this.
The note The attributes
On Tue, 27 Oct 2009, Honza Bambas wrote:
The spec says:
When the |setItem()
http://dev.w3.org/html5/webstorage/#dom-storage-setitem|, |removeItem()
http://dev.w3.org/html5/webstorage/#dom-storage-removeitem|, and |clear()
http://dev.w3.org/html5/webstorage/#dom-storage-clear| methods are
On Tue, 27 Oct 2009, Markus Ernst wrote:
Thank you. In this table
http://www.whatwg.org/specs/web-apps/current-work/multipage/section-index.html#events-0
there is now the error event left with no indication where the event is fired,
but only when it is fired.
Fixed.
--
Ian Hickson
On Tue, 27 Oct 2009 00:06:41 +0100, Honza Bambas hon...@allpeers.com
wrote:
Maybe I read something wrong, but as a sessionStorage object is always
unique to its document (it is cloned when a new document with the same
origin is created and then independent from the original document's
object)
Hi, all
I'd like to talk about the author requirements of the progress element.
http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#the-progress-element
There are some cases in the requirements.
But one case is dropped.
The value attribute is specified but the
On Fri, Oct 23, 2009 at 4:36 AM, Ian Hickson i...@hixie.ch wrote:
I think less rigid styles are good, and are what made the Web the success
that it is. Authors are welcome to use validators that complain about this
kind of markup, but we should enforce this style on everyone. Some people
(e.g.
Jonas Sicking wrote:
On Mon, Oct 26, 2009 at 4:06 PM, Honza Bambas hon...@allpeers.com wrote:
The spec says:
When the setItem(), removeItem(), and clear() methods are called on a
Storage object x that is associated with a session storage area, if the
methods did something, then in every
Ian Hickson wrote:
On Tue, 27 Oct 2009, Honza Bambas wrote:
The spec says:
When the |setItem()
http://dev.w3.org/html5/webstorage/#dom-storage-setitem|, |removeItem()
http://dev.w3.org/html5/webstorage/#dom-storage-removeitem|, and |clear()
On Tue, Oct 27, 2009 at 01:17, Ian Hickson i...@hixie.ch wrote:
The connection might get closed at any point, e.g. between the script
checking if the connection might be closed and the script calling the
send() method. Because of this, if we raised an exception when the
connection was
On Tue, 27 Oct 2009, Futomi Hatano wrote:
I'd like to talk about the author requirements of the progress element.
http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#the-progress-element
There are some cases in the requirements.
But one case is dropped.
On Tue, 27 Oct 2009, Eduard Pascual wrote:
On Fri, Oct 23, 2009 at 4:36 AM, Ian Hickson i...@hixie.ch wrote:
I think less rigid styles are good, and are what made the Web the success
that it is. Authors are welcome to use validators that complain about this
kind of markup, but we should
On Tue, Oct 13, 2009 at 4:07 AM, Ian Hickson i...@hixie.ch wrote:
I've edited the latter text to indicate that the expiration should only be
done at user option.
On a device with limited storage, is the user option of having a
device that still boots and operates a sufficient option?
I'm
On Tue, 27 Oct 2009, timeless wrote:
On Tue, Oct 13, 2009 at 4:07 AM, Ian Hickson i...@hixie.ch wrote:
I've edited the latter text to indicate that the expiration should
only be done at user option.
On a device with limited storage, is the user option of having a device
that still boots
For a brief period today, there were no outstanding e-mails or bugs on the
specs, and so I took that opportunity to transition us here at the WHATWG
to the next stage of HTML5's development: Last Call! This affects three
specs at the WHATWG:
* HTML5
G'day list,
I've been working on my first HTML5 frontend, which is using the video
element, and I've run into a part of the spec that I disagree with
(and would like to understand its justification):
Content may be provided inside the video element. User agents should
not show this
On Mon, 5 Oct 2009, tjeddo wrote:
I believe that the current HTML5 spec is heading in the right direction
by narrowing the meaning of the cite element compared to its ambiguous
use in HTML documents in the past. Overloading the meaning of the cite
element further by using it to
On Tue, Oct 27, 2009 at 7:40 PM, Kit Grose k...@iqmultimedia.com.au wrote:
[snip]
I expected (incorrectly, in this case) that if I only produced one
source element (an MP4), Firefox would drop down to use the fallback
content, as it does if I include an object element for a format not
(CCing DOM list just in case anyone there has any comments)
With:
pinput onkeypress=this.nextSibling.focus()input/p
, if you type a character in the first field, should the character be
entered in the second field or the first?
In Firefox and Safari, it's the first field. In IE and Opera,
G'day Gregory,
Thanks for the explanation. While I understand the issue you present
with precedence of JS and fallback content, I can't off the top of my
head come up with any necessary uses for the canPlayType function
(maybe as a nice-to-have, of course) had the behaviour worked more
On Tue, Oct 27, 2009 at 7:40 PM, Kit Grose k...@iqmultimedia.com.au wrote:
Can I get some sort of an understanding on why this behaviour (non-
descript error in supported UAs rather than using the fallback content
that can provide alternate access methods) would be preferred?
Suppose browsers
Thanks for the really in-depth reply; you make some excellent points
(particularly defining a video source file with the src attribute). I
think it all boils down to the fact that canPlayType() can return
maybe; and in those cases the expected behaviour I mention isn't
easily definable.
Hi, all.
Congratulations on Last Call!
I'm administrator of HTML5 community in Japan
(http://translate.google.co.jp/translate?prev=hphl=jajs=yu=http://blog.livedoor.jp/kotesaki/archives/1290508.htmlsl=jatl=enhistory_state0=).
I would like to make known an act to celebrate the occasion.
Today,
24 matches
Mail list logo
