Hi, all
I found an odd example in the meter element section of the spec.
http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#the-meter-element
metermax: 100; current: 75/meter
According to steps for finding one or two numbers of a ratio in a string,
does it
Futomi Hatano wrote:
Hi, all
I found an odd example in the meter element section of the spec.
http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#the-meter-element
metermax: 100; current: 75/meter
According to steps for finding one or two numbers of a ratio
On Thu, 29 Oct 2009 10:58:17 +0100
Magnus Kristiansen magnusrk+wha...@pvv.org wrote:
No, the larger number is always used as the max, and the smaller as
current. In the meter section: (...) if there were two numbers parsed
out of the textContent, then the maximum is the higher of those two
On Thu, Oct 15, 2009 at 10:53 PM, Markus Ernst derer...@gmx.ch wrote:
From a performance point of view it might even be worth thinking about the
contrary: Allow UAs to stop the execution of scripts on non-visible windows
or elements by default, and provide a method to explicitly specify if the
On Fri, Oct 30, 2009 at 12:23 AM, timeless timel...@gmail.com wrote:
On Thu, Oct 15, 2009 at 10:53 PM, Markus Ernst derer...@gmx.ch wrote:
From a performance point of view it might even be worth thinking about
the
contrary: Allow UAs to stop the execution of scripts on non-visible
windows
Nikita Popov wrote:
In the spec the use of the rp-tag is shown like this:
ruby
漢 rp(/rprtかん/rtrp)/rp
字 rp(/rprtじ/rtrp)/rp
/ruby
What semantic function has the rp-tag? No. It is only styling for
browsers not supporting ruby-text.
So I think this element musn't be in the HTML5 spec. You can add
On Wed, 28 Oct 2009 10:57:43 -0400, Jacob Rossi ro...@gatech.edu wrote:
On Wed, Oct 28, 2009 at 2:43 AM, Michael A. Puls II
On 10/29/09 9:20 AM, Michael A. Puls II wrote:
Despite that though, preventDefault() still works in
Firefox and Safari inside a keypress handler to prevent the char from
being inserted. So, I'm not exactly sure what's they're doing behind the
scenes.
Last I checked in Gecko, things looked
On Thu, Oct 29, 2009 at 9:20 AM, Michael A. Puls II shadow2...@gmail.comwrote:
Safari and Firefox will allow focus() inside the handler to decide where
the character gets inserted, but only with keydown. With keypress (and
textInput in webkit) in Firefox and Safari, it appears that the char
Prior to r4177, the matching of tag names for exiting the RCDATA/RAWTEXT states
was done as follows:
...and the next few characters do no match the tag name of the last start tag
token emitted (compared in an ASCII case-insensitive manner)
However, the current revision doesn't include any
Apologies for the repost -- here is the original e-mail in plain text:
Prior to r4177, the matching of tag names for exiting the RCDATA/RAWTEXT states
was done as follows:
...and the next few characters do no match the tag name of the last start tag
token emitted (compared in an ASCII
Matt Hall wrote:
Apologies for the repost -- here is the original e-mail in plain text:
Prior to r4177, the matching of tag names for exiting the RCDATA/RAWTEXT states
was done as follows:
...and the next few characters do no match the tag name of the last start tag token
emitted (compared
Of course :-). Thanks a lot, Geoffrey!
-Matt
-Original Message-
From: Geoffrey Sneddon [mailto:gsned...@opera.com]
Sent: Thursday, October 29, 2009 8:59 AM
To: Matt Hall
Cc: whatwg@lists.whatwg.org
Subject: Re: [whatwg] Character casing for Appropriate End Tags and the
temporary buffer
On Thu, 29 Oct 2009 10:14:42 -0400, Boris Zbarsky bzbar...@mit.edu wrote:
On 10/29/09 9:20 AM, Michael A. Puls II wrote:
Despite that though, preventDefault() still works in
Firefox and Safari inside a keypress handler to prevent the char from
being inserted. So, I'm not exactly sure what's
Greetings,
I saw HTML5 was put into last call, and I wanted to add my request to
reconsider adding input minlength= to HTML5. With some searching,
I found the following threads on the topic:
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2006-February/005892.html
On Thu, Oct 29, 2009 at 3:03 PM, Ryan Cannon r...@ryancannon.com wrote:
In order to correctly report the error to the user, I would have to do a
second check of the value to figure out the problem. The only way to
determine that the error was caused by too few characters as opposed to
invalid
On 10/29/09 5:24 PM, Michael A. Puls II wrote:
I think so. The event target isn't changed by focus().
But, in Firefox, Safari and Opera, it's possible to change what element
the text is inserted into by changing the focus in 'keydown'.
Right; that happens because the keydown and keypress
On Thu, 29 Oct 2009 20:51:48 -0400, Boris Zbarsky bzbar...@mit.edu wrote:
On 10/29/09 5:24 PM, Michael A. Puls II wrote:
I think so. The event target isn't changed by focus().
But, in Firefox, Safari and Opera, it's possible to change what element
the text is inserted into by changing the
On Oct 29, 2009, at 5:51 PM, Boris Zbarsky wrote:
On 10/29/09 5:24 PM, Michael A. Puls II wrote:
I think so. The event target isn't changed by focus().
But, in Firefox, Safari and Opera, it's possible to change what
element
the text is inserted into by changing the focus in 'keydown'.
On 10/29/09 10:16 PM, Maciej Stachowiak wrote:
WebKit also makes typing take effect as the default action for
keypress, at least for normal typing. It's more complicated when
international text input methods are in play.
Yeah, when IME is involved I have no idea what events are fired in Gecko
On 10/29/09 9:58 PM, Michael A. Puls II wrote:
But, in Firefox, Safari and Opera, it's possible to change what element
the text is inserted into by changing the focus in 'keydown'.
Right; that happens because the keydown and keypress events need not
fire on the same element and because the
21 matches
Mail list logo
