Re: [whatwg] input element list attribute and filtering suggestions

2011-08-01 Thread Bjartur Thorlacius
Þann mán 1.ágú 2011 15:28, skrifaði Aryeh Gregor: > On Fri, Jul 29, 2011 at 7:24 PM, Ian Hickson wrote: > The overarching counterpoint is that in-page UI *is* an authoring > issue, because authors want to control exactly how their page looks > and behaves. Browser/chrome UI issues shouldn't be

Re: [whatwg] input element list attribute and filtering suggestions

2011-08-01 Thread Bjartur Thorlacius
Þann mán 1.ágú 2011 15:28, skrifaði Aryeh Gregor: On Fri, Jul 29, 2011 at 7:24 PM, Ian Hickson wrote: The overarching counterpoint is that in-page UI *is* an authoring issue, because authors want to control exactly how their page looks and behaves. Browser/chrome UI issues shouldn't be standar

Re: [whatwg] ... restrict reading value from JS?

2011-08-01 Thread Bjartur Thorlacius
Þann mán 1.ágú 2011 15:25, skrifaði Aryeh Gregor: If you're doing useful password strength checks, regular expressions won't cut it. For instance, you'll want to check against dictionaries. Regex is only useful for crude and ineffective checks like "must be at least six characters long with mi

Re: [whatwg] Canvas 2d: proposal to add path(DOMString)

2011-08-01 Thread Tab Atkins Jr.
On Fri, Jul 29, 2011 at 1:44 PM, Charles Pritchard wrote: > Having spoken to several developers, I think that we're clear to add a new > method to the canvas 2d api; > though there is some question about how it should be added. > > The method would take a DOMString using SVG path semantics. > > I'

Re: [whatwg] link.sizes and [PutForwards=value]

2011-08-01 Thread Cameron McCormack
On 2/08/11 6:29 AM, Tab Atkins Jr. wrote: It's a confusion shared by all objects, though: var x = [1,2]; var y = [1,2]; alert([x,y,x==y).join(' '); This alerts "1,2 1,2 false". That is true, but I get the impression that some authors don't know that the Location object is actually an object

Re: [whatwg] Why children of datalist elements are barred from constraint validation?

2011-08-01 Thread Jonas Sicking
On Sun, Jul 31, 2011 at 11:45 AM, Jeremy Keith wrote: > The way that datalist is currently designed (and implemented) is exemplary. > The fact that (by design) it allows authors to nest a select element within > it that shares the same option elements means that authors can safely begin > to us

Re: [whatwg] Proposal to extend registerProtocolHandler

2011-08-01 Thread Ian Hickson
On Tue, 26 Jul 2011, James Kozianski wrote: > > Here are the use cases I had in mind: > > 1. Allow sites to conditionally show UI to promote the advantages of > registering the site as a handler. >(requires isRegistered) > > 2. Allow sites to provide settings screens which allow users to reg

Re: [whatwg] link.sizes and [PutForwards=value]

2011-08-01 Thread Tab Atkins Jr.
On Sat, Jul 30, 2011 at 12:51 AM, Cameron McCormack wrote: > There is a disadvantage.  In JS, doing a comparison between two objects, > regardless of whether they have custom stringification behaviour, will > compare based on object identity and not the string. > > > > > > window.onload = func

Re: [whatwg] input element list attribute and filtering suggestions

2011-08-01 Thread Aryeh Gregor
On Fri, Jul 29, 2011 at 7:24 PM, Ian Hickson wrote: > My overarching point, however, is that this is a UI issue, and not an > authoring issue. The overarching counterpoint is that in-page UI *is* an authoring issue, because authors want to control exactly how their page looks and behaves. Browse

Re: [whatwg] ... restrict reading value from JS?

2011-08-01 Thread Aryeh Gregor
On Fri, Jul 29, 2011 at 9:53 PM, Bjartur Thorlacius wrote: > So there are two use cases for reading user passwords: >  * client side password strength indicators >  ** telling users if their passwords conform to site specific password > restrictions >  - arguably bad practice >  - IMO better achie