Re: [whatwg] video application/octet-stream

2010-07-20 Thread Chris Double
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

Re: [whatwg] video application/octet-stream

2010-07-20 Thread Philip Jägenstedt
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

[whatwg] output should not be barred from constraint validation

2010-07-20 Thread Mounir Lamouri
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

[whatwg] Why not creating a category for elements candidate for constraint validation?

2010-07-20 Thread Mounir Lamouri
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

Re: [whatwg] Why not creating a category for elements candidate for constraint validation?

2010-07-20 Thread Simon Pieters
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

Re: [whatwg] video application/octet-stream

2010-07-20 Thread timeless
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

Re: [whatwg] output should not be barred from constraint validation

2010-07-20 Thread Mounir Lamouri
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

Re: [whatwg] Canvas stroke alignment

2010-07-20 Thread David Flanagan
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

Re: [whatwg] postMessage's target origin argument can be a full URL in some implementations

2010-07-20 Thread Hallvord R M Steen
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

Re: [whatwg] video application/octet-stream

2010-07-20 Thread James Salsman
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