Hi Andrew,
I agree that the structure of your proposal is better, the Font object
is not really needed.
However, I think getAscent() is not sufficient, we should also add
getLeading() and getDescent():
This would allow us to determine the total line height
(leading+ascent+descent) and the
Most modern browsers support the following:
a href=javascript:alert(123)foo/a
AFAICS javascript:alert(123) is not a valid IRI according to RFC 3987
(it should be javascript:alert%28123%29 instead) and is thus not
allowed in an input type=url field. This is somewhat surprising to
me, and I
* Christian Schmidt wrote:
AFAICS javascript:alert(123) is not a valid IRI according to RFC 3987
(it should be javascript:alert%28123%29 instead) and is thus not
allowed in an input type=url field.
You are mistaken.
This is somewhat surprising to me, and I think it will confuse users
that they
Alfonso Baqueiro wrote:
The canvas component is very promising, but the lack of drawString
method could be a great error for its success, this lack is a huge
limitation, how could you resolve this problem?
I've suggested this in the past as a solution to this problem: why not
have a
On Wed, 18 Oct 2006 20:52:35 +0200, Gervase Markham [EMAIL PROTECTED]
wrote:
Alfonso Baqueiro wrote:
The canvas component is very promising, but the lack of drawString
method could be a great error for its success, this lack is a huge
limitation, how could you resolve this problem?
I've
Some comments and questions:
5.5.1
Is the DragEvent supposed to inherit from Event? Wouldn't at least
UIEvent be more reasonable?
I'm not familiar with accessibility for drag and drop. Do platforms
actually have a means of performing drag and drop that aren't mapped to
mouse events?
The
