Ian Hickson wrote :
On Sat, 12 May 2007, Jordan OSETE wrote:
It can be done with a wrapper, but it seems overhead, when the UA can
just return something easier to read.
Well, the overhead is the same, it's just a matter of who does it, the UA
or the author.
Though we would need
On Sat, 12 May 2007, Jordan OSETE wrote:
It can be done with a wrapper, but it seems overhead, when the UA can
just return something easier to read.
Well, the overhead is the same, it's just a matter of who does it, the UA
or the author.
In that case, why not always return an array, like
Ian Hickson wrote :
On Mon, 16 Apr 2007, Jordan OSETE wrote:
In that case, we could detect if the application tries to set an array
to the properties fillStyle or strokeStyle, and if it is the case, then
it means that the given application is more recent than the change from
string to
On Sat, 12 May 2007 10:52:39 +0200, Jordan OSETE
[EMAIL PROTECTED] wrote:
It can be done with a wrapper, but it seems overhead, when the UA can
just return something easier to read.
In that case, why not always return an array, like Philip Taylor
suggested?
This would complicate setting
On 12/05/07, Anne van Kesteren [EMAIL PROTECTED] wrote:
On Sat, 12 May 2007 10:52:39 +0200, Jordan OSETE
[EMAIL PROTECTED] wrote:
It can be done with a wrapper, but it seems overhead, when the UA can
just return something easier to read.
In that case, why not always return an array, like
On Sun, 15 Apr 2007, Jordan OSETE wrote:
Reading colors can be complex. Right now it returns a string either in
the form #xx or rgba(...), depending on the alpha value. It means
the reader must be able to parse both, because he never knows if the
color's alpha is 255 or less. Maybe
