On Tue, Jul 20, 2010 at 9:48 PM, Philip Jägenstedt phil...@opera.com wrote:
I'd like to hear from Mozilla, Google and Apple which of these (or other)
solutions they would find acceptable.
You'll probably get different responses depending on who in Mozilla
responds. For example, I prefer option
On Tue, 20 Jul 2010 12:00:41 +0200, Chris Double
chris.dou...@double.co.nz wrote:
On Tue, Jul 20, 2010 at 9:48 PM, Philip Jägenstedt phil...@opera.com
wrote:
I'd like to hear from Mozilla, Google and Apple which of these (or
other)
solutions they would find acceptable.
You'll probably
Hi,
At the moment, three form elements are barred from constraint
validation: object, fieldset and output. I can understand why object and
fieldset are barred from constraint validation but I think output could
use the constraint validation.
Indeed, it could be nice to be able to use
Hi,
I'm wondering why there is no categories for elements candidate for
constraint validation. In the current state of the specs, all listed
elements are candidate for constraint validation except when they are
barred from constraint validation. Barring an element from constraint
validation when
On Tue, 20 Jul 2010 15:47:32 +0200, Mounir Lamouri
mounir.lamo...@gmail.com wrote:
Hi,
I'm wondering why there is no categories for elements candidate for
constraint validation. In the current state of the specs, all listed
elements are candidate for constraint validation except when they
On Tue, 20 Jul 2010 12:00:41 +0200, Chris Double
chris.dou...@double.co.nz wrote:
You'll probably get different responses depending on who in Mozilla
responds. For example, I prefer option (1) and am against content
sniffing. Other's at Mozilla disagree I'm sure.
On Tue, Jul 20, 2010 at 1:28
On 07/20/2010 06:00 PM, Tab Atkins Jr. wrote:
On Tue, Jul 20, 2010 at 6:37 AM, Mounir Lamouri
mounir.lamo...@gmail.com wrote:
Hi,
At the moment, three form elements are barred from constraint
validation: object, fieldset and output. I can understand why object and
fieldset are barred from
Nick wrote:
Canvas would benefit from a way to set stroke alignment. With the only
available alignment being center, which is not very useful, custom paths
have to be drawn to mimic inside and outside stroke alignment. That
workaround may give unwanted transparency on pixels between a path and
I agree with that in general, however it makes things harder that this
is an issue that might have security implications.
The security implication being that authors might get confused about what
the origin actually means and whom they can expect messages from, right?
More precisely who they
I would like to speak up for sniffing because I believe in the
robustness principle. I don't know why people who are capable of
coding hundreds of lines of dense, uncommented javascript can't get
their web servers to declare the correct type of their media files,
but it happens so often that I
10 matches
Mail list logo