[Bug 27986] New: Specify exact length of array returned by Navigator.getGamepads()

2015-02-09 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27986 Bug ID: 27986 Summary: Specify exact length of array returned by Navigator.getGamepads() Product: WebAppsWG Version: unspecified Hardware: PC OS: All

RE: Minimum viable custom elements

2015-02-09 Thread Jonathan Bond-Caron
On Wed Feb 4 02:08 PM, Ryosuke Niwa wrote: > > > step="5"> > To me this seems like a winning pattern at least when it comes to input. This did a good job a describing the two approaches: https://wiki.whatwg.org/wiki/Behavior_Attachment Where does the decorator pattern/approach stand?

Violation of mail list policy [Was: Fwd: Re: do not deprecate synchronous XMLHttpRequest]

2015-02-09 Thread Arthur Barstow
Michaela, Some of the language you used in [1] is offensive. Per the group's mail list etiquette policy ([2]), please do not use such language on WebApps' mail lists. -Regards, AB [1] https://lists.w3.org/Archives/Public/public-webapps/2015JanMar/0538.html [2] https://www.w3.org/2008/webapp

Re: Violation of mail list policy [Was: Fwd: Re: do not deprecate synchronous XMLHttpRequest]

2015-02-09 Thread Michaela Merz
I do apologize for the unfortunate selection of some words in this posting. It was not my intention to attack, to insult or to offend anybody. Michaela On 02/09/2015 12:53 PM, Arthur Barstow wrote: > Michaela, > > Some of the language you used in [1] is offensive. Per the group's mail list etiq

Re: do not deprecate synchronous XMLHttpRequest

2015-02-09 Thread George Calvert
I third Michaela and Gregg. It is the app and site developers' job to decide whether the user should wait on the server - not the standard's and, 99.9% of the time, not the browser's either. I agree a well-designed site avoids synchronous calls. BUT - there still are plenty of real-world case