Re: [whatwg] maincontent element spec updated and supporting data provided

2012-10-17 Thread Steve Faulkner
Hi Ian, Like the succinct and simple name of complementary content (aside), could we make the element name of the main content as succinct as aside? For instance, main? I have responded on the HTML WG list to a similar naming preference comment:

Re: [whatwg] Submitting contentEditable Content In A Form

2012-10-17 Thread Ian Hickson
On Fri, 7 Sep 2012, Hugh Guiney wrote: I'm developing a CMS and would like to be able to submit user-edited content back to the server, but at present, it's not possible to do this without copying the contents of the edited element with JavaScript into, say, a hidden form field. I think

Re: [whatwg] Should editable elements have placeholder attribute?

2012-10-17 Thread Ian Hickson
On Thu, 6 Sep 2012, Aryeh Gregor wrote: It should never be possible to make a contenteditable element contain nothing, once it has something in it, because then it would collapse to zero height and you wouldn't be able to click on it. [...] On Thu, 6 Sep 2012, Ojan Vafai wrote: While

[whatwg] Usability issues with input type=url validation

2012-10-17 Thread Mikey Clarke
Hi all, I'd like a little information on the motivation for using absolute URLs on input type=url validation. Currently input type=url is to be validated using absolute URLs. Thus, 'http://www.mysite.com' validates but 'www.mysite.com' does not. I consider this to be a huge usability issue.

Re: [whatwg] Usability issues with input type=url validation

2012-10-17 Thread Ian Hickson
On Thu, 18 Oct 2012, Mikey Clarke wrote: I'd like a little information on the motivation for using absolute URLs on input type=url validation. Currently input type=url is to be validated using absolute URLs. Thus, 'http://www.mysite.com' validates but 'www.mysite.com' does not. I

Re: [whatwg] Submitting contentEditable Content In A Form -- also in SVG and audio contexts

2012-10-17 Thread David Dailey
I don't know if this matters or not, but at some point in time, other standards than HTML like svg or audio might receive sensible proposals to allow other media (than just text) to be contentEditable. Just as it makes sense to have built in text editors (imagine the spectrum ranging from

Re: [whatwg] Submitting contentEditable Content In A Form -- also in SVG and audio contexts

2012-10-17 Thread Ian Hickson
On Wed, 17 Oct 2012, David Dailey wrote: I don't know if this matters or not, but at some point in time, other standards than HTML like svg or audio might receive sensible proposals to allow other media (than just text) to be contentEditable. Just as it makes sense to have built in text

Re: [whatwg] Submitting contentEditable Content In A Form -- also in SVG and audio contexts

2012-10-17 Thread David Dailey
No I had nothing at all in mind that might be inconsistent with what is being discussed -- just sort of a free association I suppose. Cheers David -Original Message- From: Ian Hickson [mailto:i...@hixie.ch] Sent: Wednesday, October 17, 2012 9:27 PM To: David Dailey Cc: 'whatwg';

Re: [whatwg] Features for responsive Web design

2012-10-17 Thread Fred Andrews
This is good point. Could I just clarify my understanding with an example: Given a thumbnail image with srcset: srcset=low.jpg 20w, hi.jpg 40w, huge.jpg 80w The webpage may want to have the browser scale the 20w image to say 50px without the browser deciding that the 40w image is more

Re: [whatwg] maincontent element spec updated and supporting data provided

2012-10-17 Thread Ian Yang
On Thu, Oct 18, 2012 at 1:31 AM, Steve Faulkner faulkner.st...@gmail.comwrote: Hi Ian, Like the succinct and simple name of complementary content (aside), could we make the element name of the main content as succinct as aside? For instance, main? I have responded on the HTML WG list to a