Hi,
Suggestion: drop UTF-32 from the character encoding detection section of
HTML5, and even better, discourage of forbid user agents from
implementing support for UTF-32.
Why:
- It's not widely used. In fact, has UTF-32 ever been used at all,
outside of test suites?
- It's not widely
For all its worth, I'm in favor of this suggestion and most arguments
provided by Michael Day.
-Ivo
On Tue, 15 May 2007 13:02:51 +0200, Gervase Markham [EMAIL PROTECTED]
wrote:
I'd treat these two problems as equally important. A separate HTTP
request per forum comment on the page is completely unacceptable.
Would you really want separate security contexts for each comment?
I wouldn't
The OP probably meant that maintaining so many contexts would cause a
comparable deterioration in performance. All user comments should be put in
one security context.
With all comments grouped together in such a manner, you could even use an
inline frame.
Chris
-Original Message-
From:
A few random comments on the new text (though I'll try to look over
this section again in more detail in the not-too-far future):
If multiple stops are placed at the same place on a gradient, they
must be placed in the order added - that sounds a bit awkward with so
many 'place' with different
This may have already been asked (sounds familair) but I don't see it in
the archives. What if the min or max values for a meter is unbounded?
For example, the 7th member of the Fibonacci series? How does one
indicate that?
--
Elliotte Rusty Harold [EMAIL PROTECTED]
Java I/O 2nd Edition Just
On Tue, 15 May 2007 20:11:21 +0200, Elliotte Harold
[EMAIL PROTECTED] wrote:
This may have already been asked (sounds familair) but I don't see it in
the archives. What if the min or max values for a meter is unbounded?
For example, the 7th member of the Fibonacci series? How does one
On 5/15/07, Kristof Zelechovski [EMAIL PROTECTED] wrote:
The OP probably meant that maintaining so many contexts would cause a
comparable deterioration in performance. All user comments should be put
in
one security context.
With all comments grouped together in such a manner, you could even
On Tue, 15 May 2007 23:37:37 +0200, Jon Barnett [EMAIL PROTECTED]
wrote:
The OP probably meant that maintaining so many contexts would cause a
comparable deterioration in performance. All user comments should be
put in one security context.
With all comments grouped together in such a
On Sat, 5 May 2007, Darin Adler wrote:
c) changing width or height of canvas to the same value
I'd like the specification to mention what happens when the width
attribute is set to a value, but it's the same value as before. The
current text says, If the width and height attributes are
On Wed, 9 May 2007, David Flanagan wrote:
There are many styles that aren't supported -- dashes aren't an
exception. For example, there's no support for having defined markers
repeated around the stroke. Similarly, we don't havenative support for
rounded corners, or for many shapes
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
On Sat, 12 May 2007, Anne van Kesteren wrote:
These features are nice but I don't think authors will understand that
imagedata.height != canvas.height (likewise for width). Authors will
just make something that works in their browser and then assume it will
work everywhere else. Which
On Tue, 15 May 2007, Philip Taylor wrote:
var dataURL = canvas.toDataURL(); // dataURL is just a string
var img = new Image();
img.src = dataURL; // img is an image that was generated from a
data: URI found in this Document, so its origin is the origin of this
Document
On Tue, 15 May 2007, Philip Taylor wrote:
A few random comments on the new text (though I'll try to look over this
section again in more detail in the not-too-far future):
If multiple stops are placed at the same place on a gradient, they must
be placed in the order added - that sounds a
On Sat, 12 May 2007, Jordan OSETE wrote:
There's still no way to _get_ the transformation matrix, but you can
not _set_ the transformation matrix now, which should be of help here.
I'm not sure exactly what you mean. Isn't it the purpose of the setTransform
method?
Sorry, I meant you
On Sat, 20 May 2006, Anne van Kesteren wrote:
I think http://whatwg.org/specs/web-apps/current-work/#strokerect must
have no effect when it has a zero height or width (or both). Currently
Safari, Firefox and Opera act that way when they are both zero and
Safari acts that way for all cases.
On May 15, 2007, at 5:29 PM, Ian Hickson wrote:
On Sun, 13 May 2007, Maciej Stachowiak wrote:
(Given that you can create them yourself I'm not sure why ImageData
has readonly attributes, but maybe that would save some additional
checking...)
Ironically, due to the readonly attributes you
18 matches
Mail list logo
