L. David Baron on 2007-03-14:
No, it's the *encoding* (conversion from characters to bytes) that should
be done as UTF-8, not the *decoding* (conversion from bytes to
characters).
Right. Sorry for the confusion. Perhaps it would be good to specify it, but
it needs to be specified in a way
Bjoern Hoehrmann wrote:
In case of video, there is no need to implement anything using style
sheets, behaviors, or scripting, you can use it directly, right now,
it's easy as pie,
html xmlns:t=urn:schemas-microsoft-com:time
?import namespace=t implementation=#default#time2
body
On Thu, 15 Mar 2007 02:02:46 +0100, Gareth Hay [EMAIL PROTECTED] wrote:
On 15 Mar 2007, at 00:30, Magnus Kristiansen wrote:
Mouseover/out events will trigger when elements contained inside the
EventTarget are hovered, and then bubble up. This is contrary to the
most obvious interpretation,
* Peter Karlsson wrote:
There is a setting in Opera to control the behaviour. Either we use UTF-8
for all URLs (the default), or we use the document encoding. The latter
setting is popular in some locales, especially Russia (IIRC).
That's Appendix B of HTML 4.01.
Having a real specification of
* Stuart Langridge wrote:
Of course, this only works with stuff that WMP can already play, which
will make backending a proposed video tag to this impractical (since
you can't mandate a format that Windows doesn't have, in particular
Ogg *, and there are doubtless issues with mandating formats
* Matthew Raymond wrote:
The following individuals may or may not have agreed to the W3C
Patent Policy regarding the Web Forms 2.0 specification:
If your name is on the list above, please agree to the license so we
can circumvent the patent policy issue in the HTML WG. Let me know if
you've
I'm not so sure it is a workaround though.
If you know that the event will bubble, you can make your handler
prevent bubbling.
I don't think we should be adding two new events to a spec, when the
existing events can work in the way you want, albeit with a line more
code. If we did, we'd
On Thu, 15 Mar 2007 20:10:33 +0100, Gareth Hay [EMAIL PROTECTED] wrote:
I'm not so sure it is a workaround though.
If you know that the event will bubble, you can make your handler
prevent bubbling.
I don't think we should be adding two new events to a spec, when the
existing events can
Spartanicus [EMAIL PROTECTED] wrote:
I'd much rather see different authors writing their own best authoring
guidelines using their own argumentation and have these compete for
adoption amongst peers.
Having said that I felt obliged to write something on the subject
myself. Part 1 is about
2007/3/15, Magnus Kristiansen [EMAIL PROTECTED]:
On Thu, 15 Mar 2007 20:10:33 +0100, Gareth Hay [EMAIL PROTECTED] wrote:
I'm not so sure it is a workaround though.
If you know that the event will bubble, you can make your handler
prevent bubbling.
I don't think we should be adding two new
I think I am clearly missing something.
If we take your example, a parent element and several child elements.
If you want to perform an action on mouseover of a child - attach
the event there and cancel bubble.
If you want to perform an action on parent mouseover - attach to
parent element
Wow, what a lot of feedback on video! I've added a video element, with
basic features, but really what we need is feedback from video experts.
In the meantime, here's replies to the comments I got. I haven't quoted
all the e-mails, since many said the same thing or went in circles (well,
they
At 19:52 + UTC, on 2007-03-15, Spartanicus wrote:
[...]
[...] I felt obliged to write something on the subject
myself. Part 1 is about heading usage:
http://codewallop.110mb.com/goodpractice/headingology.htm
NIce. I've linked to it from
Le 16 mars 2007 à 12:39, Ian Hickson a écrit :
Wow, what a lot of feedback on video! I've added a video element,
with
basic features, but really what we need is feedback from video
experts.
http://www.whatwg.org/specs/web-apps/current-work/#video
--
Karl Dubost -
14 matches
Mail list logo
