Maciej Stachowiak wrote:
OK, I'm sure the last thing that is needed is more syntax suggestions,
but here's an alternate proposal with no new attributes, specify size
info as additional rel keywords:
link rel=icon scalable type=application/svg href=whatwg.svg
link rel=icon 16x16 32x32
Maciej Stachowiak wrote:
This might require that existing browsers cope correctly (or exploit
duplication/error behaviors), but could a MIME parameter address this
without needing another attribute at all? That's the most narrowly
scoped change I can imagine that would address the need.
The question is related to the 'input' event on Web Forms 2.0.
The WF2 specification says:
This [input] event must be fired on a control whenever the value of
the control changes due to input from the user, and is otherwise
identical to the change event.
However, there are a few problems with
On May 2, 2008, at 12:24 AM, fantasai wrote:
Maciej Stachowiak wrote:
This might require that existing browsers cope correctly (or
exploit duplication/error behaviors), but could a MIME parameter
address this without needing another attribute at all? That's the
most narrowly scoped
I think it should be possible to embed rendered bit map images in SVG for
lower resolution, just as TrueTypeT fonts embed ideograms.
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Maciej Stachowiak
Sent: Friday, May 02, 2008 12:28 PM
To: fantasai
On 5/2/08, Rimvydas [EMAIL PROTECTED] wrote:
The question is related to the 'input' event on Web Forms 2.0.
The WF2 specification says:
This [input] event must be fired on a control whenever the value of
the control changes due to input from the user, and is otherwise
identical to the
Not sure why you're responding to a 3-month-old email or what Turing
complete has to do with anything (the QuickTime runtime is also Turing
complete), but feel free to ping me off-list if you have questions.
-- Charles
-Original Message-
From: Křištof Želechovski [mailto:[EMAIL
Hi Rich,
activedescendant:
Great. If it will work for us, I feel better relying on the user agent
for bringing active descendants into view. I thought we were going to
require the DHTML author to perform a scroll of some kind? If not,
great, and I agree it would appear to be a akin to
Replying to myself below...
David Bolter wrote:
Hi Rich,
activedescendant:
Great. If it will work for us, I feel better relying on the user agent
for bringing active descendants into view. I thought we were going to
require the DHTML author to perform a scroll of some kind? If not,
great,
I think if there is an attribute like this which also scrolls for you,
then it should be called activedescendant, not aria-activedescendant. I
don't see a problem if HTML 5 wants the attribute without aria- to drive
browser behavior. In that case perhaps it should style the active
descendant
http://web.mit.edu/jwalden/www/whatwg/postMessage-v3.zip
Same instructions as last time -- unzip, start an HTTP server on port serving
postMessage/ as its root directory, set up proxy autoconfig with a PAC URL of
http://localhost:/proxy.js, navigate to
11 matches
Mail list logo
