[whatwg] Why isn't the pattern attribute applied to input type=number?

2012-02-10 Thread brenton strine
Regarding the an input with type in the number state, the spec states that the pattern attribute must not be specified and do[es] not applyhttp://dev.w3.org/html5/spec/common-input-element-attributes.html#do-not-apply to the element. (

Re: [whatwg] Why isn't the pattern attribute applied to input type=number?

2012-02-10 Thread Ms2ger
Hi Brenton, On 02/10/2012 11:39 AM, brenton strine wrote: Regarding the an input with type in the number state, the spec states that the pattern attribute must not be specified and do[es] not applyhttp://dev.w3.org/html5/spec/common-input-element-attributes.html#do-not-apply to the element. (

Re: [whatwg] Why isn't the pattern attribute applied to input type=number?

2012-02-10 Thread Jukka K. Korpela
2012-02-10 12:39, brenton strine wrote: Regarding the an input with type in the number state, the spec states that the pattern attribute must not be specified and do[es] not apply to the element. That’s because the pattern attribute is for constraining text data using a regular expression.

Re: [whatwg] Quirks Mode Standard

2012-02-10 Thread Boris Zbarsky
On 2/10/12 2:57 AM, Simon Pieters wrote: 1) I'm fairly certain the Images (img elements) without alt attributes sometimes display placeholder icons in quirks mode. quirk cannot be dropped. ... The HTML specification specifies this quirk in the Rendering section.

[whatwg] [Cross-document messaging] Restrictions on targetOrigin

2012-02-10 Thread João Eiras
Hi. Step 1 of the spec [1] for postMessage says: 1. If the value of the targetOrigin argument is neither a single U+002A ASTERISK character (*), a single U+002F SOLIDUS character (/), nor an absolute URL, then throw a SyntaxError exception and abort the overall set of steps. The

Re: [whatwg] Quirks Mode Standard

2012-02-10 Thread Aryeh Gregor
On Fri, Feb 10, 2012 at 10:37 AM, Boris Zbarsky bzbar...@mit.edu wrote: I agree that having the list for lengths reduces the scope of the problem somewhat.  But the color quirk means that any shorthand that includes colors will run into ambiguity issues if any keywords for any subproperty only

Re: [whatwg] Quirks Mode Standard

2012-02-10 Thread Boris Zbarsky
On 2/10/12 11:23 AM, Aryeh Gregor wrote: On Fri, Feb 10, 2012 at 10:37 AM, Boris Zbarskybzbar...@mit.edu wrote: I agree that having the list for lengths reduces the scope of the problem somewhat. But the color quirk means that any shorthand that includes colors will run into ambiguity issues

Re: [whatwg] RWD Heaven and responsive-images

2012-02-10 Thread Mathew Marquis
The above is just a my proposal in advancing this discussion, and until there is no feedback about this from people on the RWD Heaven: if browsers reported device capabilities in a request header and the add html-attribute for responsive images threads, and other developers concerned in

[whatwg] Character-encoding-related threads

2012-02-10 Thread Ian Hickson
On Mon, 6 Jun 2011, Boris Zbarsky wrote: You can detect other effects by seeing what unescape() does in the resulting document, iirc. Doesn't seem like it: http://junkyard.damowmow.com/499 http://junkyard.damowmow.com/500 In both cases, unescape() is assuming Win1252, even though in

Re: [whatwg] Using footer in blockquote for attribution

2012-02-10 Thread Ian Hickson
On Fri, 1 Jul 2011, Oli Studholme wrote: Over at http://html5doctor.com we�ve been using this pattern when quoting e.g. from the HTML5 spec: blockquote p[block quote]/p footer� citea href=�[title of work]/a/cite/footer /blockquote I wrote about our use of blockquote and footer in

[whatwg] Allow Fallback Text to Render Section Titles in Outlines

2012-02-10 Thread Hugh Guiney
Currently when I run markup like this through outliner programs, they return blank section titles: h1img src=/img/logo.png alt=Company Name //h1 h1 svg g titleCompany Name/title path / … /g /svg /h1 I feel that in both instances, Company Name should become the