Re: [selectors-api] Consider backporting find() behavior to querySelector()

2012-06-19 Thread Simon Pieters
On Mon, 18 Jun 2012 16:57:17 +0200, Kang-Hao (Kenny) Lu kennyl...@csail.mit.edu wrote: (12/06/18 22:45), Simon Pieters wrote: I think we should instead either fix the old API (if it turns out to not Break the Web) or live with past mistake (if it turns out it does). To find out whether it

Re: CfC: publish a LCWD of Selectors API Level 1; deadline June 25

2012-06-19 Thread Charles McCathieNevile
On Mon, 18 Jun 2012 15:57:02 +0200, Arthur Barstow art.bars...@nokia.com wrote: Lachlan has made some changes to the Selectors API Level 1 spec (last published as a CR) and we consider the changes sufficient to require the spec be published as a Working Draft (see the [1] thread). As such,

Re: CfC: publish FPWD of Fullscreen spec; deadline May 24

2012-06-19 Thread Anne van Kesteren
On Tue, Jun 19, 2012 at 1:31 AM, fantasai fantasai.li...@inkedblade.net wrote: On 06/01/2012 05:02 AM, Anne van Kesteren wrote: On Wed, May 30, 2012 at 5:47 PM, fantasaifantasai.li...@inkedblade.net  wrote: Though it seems likely that 'fixed' is required here, no? The top layer concept is

Re: CfC: publish FPWD of Fullscreen spec; deadline May 24

2012-06-19 Thread Anne van Kesteren
On Tue, Jun 19, 2012 at 1:45 AM, fantasai fantasai.li...@inkedblade.net wrote: It looks like you missed #2. I think ::backdrop is clear enough. Not entirely sure what you would expect seeing there more than what it already says. -- Anne — Opera Software http://annevankesteren.nl/

Re: CfC: publish FPWD of Fullscreen spec; deadline May 24

2012-06-19 Thread Daniel Glazman
Le 19/06/12 09:41, Anne van Kesteren a écrit : On Tue, Jun 19, 2012 at 1:45 AM, fantasaifantasai.li...@inkedblade.net wrote: It looks like you missed #2. I think ::backdrop is clear enough. Not entirely sure what you would expect seeing there more than what it already says. Well, the

Re: CfC: publish FPWD of Fullscreen spec; deadline May 24

2012-06-19 Thread Daniel Glazman
Le 18/06/12 13:09, Arthur Barstow a écrit : On 5/30/12 10:38 AM, ext Daniel Glazman wrote: Le 30/05/12 14:43, Arthur Barstow a écrit : Chris, Daniel, Peter - when will the CSS WG make a decision on the FPWD? We'll try to make one today during our weekly conf-call. Please note that we're

Re: Browser Payments API proposal

2012-06-19 Thread Charles McCathieNevile
On Sat, 16 Jun 2012 06:05:35 +0200, Alex MacCaw macc...@gmail.com wrote: I've been working on a way of integrating one-click payments (and signup) into the browser, and I wanted to put it in front of a few people to get some feedback. The API I was playing about with was pretty simple, and is

Re: [manifest] screen sizes, Re: Review of Web Application Manifest Format and Management APIs

2012-06-19 Thread Charles McCathieNevile
On Wed, 06 Jun 2012 14:39:35 +0200, Henri Sivonen hsivo...@iki.fi wrote: On Sun, May 27, 2012 at 7:45 PM, Anant Narayanan an...@mozilla.com wrote: Well, we haven't received this request from developers explicitly yet, but one can imagine a situation in which a developer makes an app only

Fwd: IndieUI Call For Proposals

2012-06-19 Thread Arthur Barstow
The Independent User Interface WG (aka IndieUI) was started a few weeks ago [Charter] and they now have a CfP for the group's two specifications: IndieUI Events, and IndieUI User Context. Details below. -AB [Charter] http://www.w3.org/2012/05/indie-ui-charter Original Message

Re: CfC: Publish FPWD of Web Intents spec; deadline June 12

2012-06-19 Thread Arthur Barstow
On 5/29/12 2:45 PM, ext James Hawkins wrote: Dave Raggett (d...@w3.org) made a call [1] on April 10 to publish a first public working draft, and this is a Call for Consensus to do so, using the following document as the basis: dvcs.w3.org/hg/web-intents/raw-file/tip/spec/Overview.html I

Re: [selectors-api] Consider backporting find() behavior to querySelector()

2012-06-19 Thread Brian Kardell
I am very opposed to this, they do different things. Having abilities isn't a bad thing and numerous Web sites and libraries make use of qsa, not just because find was not available but because different APIs shapes interesting new possibilities, different ways of looking at problems, etc... We

Re: CfC: publish FPWD of Fullscreen spec; deadline May 24

2012-06-19 Thread Arthur Barstow
On 6/19/12 3:52 AM, ext Daniel Glazman wrote: Le 18/06/12 13:09, Arthur Barstow a écrit : On 5/30/12 10:38 AM, ext Daniel Glazman wrote: Le 30/05/12 14:43, Arthur Barstow a écrit : Chris, Daniel, Peter - when will the CSS WG make a decision on the FPWD? We'll try to make one today during

Re: CfC: publish FPWD of Fullscreen spec; deadline May 24

2012-06-19 Thread Daniel Glazman
Le 19/06/12 14:10, Arthur Barstow a écrit : Given this interpretation - and of course, please correct it if it is wrong - it appears the only remaining FPWD Showstopper is #2 in the first set of comments. Is that correct? Yes. /Daniel

Re: Browser Payments API proposal

2012-06-19 Thread Yaar Schnitman
Nice idea Alex! I have done some work on this in the past, but it didn't go very far. A few tips: 1. As long as many users don't have this, websites would still have to do form-based credit-card forms. But browsers and extensions are getting pretty good at auto-filling these forms. So you have a

Re: Browser Payments API proposal

2012-06-19 Thread Elliott Sprehn
I'm not sure this is a problem worth solving in the platform. In 5-10 years I doubt we'll be typing our card numbers into pages. You'll tap your phone to your laptop or use some kind of payment service like paypal/wallet/etc. There's so many security/privacy issues with exposing your payment

Re: CfC: publish FPWD of Fullscreen spec; deadline May 24

2012-06-19 Thread Arthur Barstow
On 6/19/12 3:49 AM, ext Daniel Glazman wrote: Le 19/06/12 09:41, Anne van Kesteren a écrit : On Tue, Jun 19, 2012 at 1:45 AM, fantasaifantasai.li...@inkedblade.net wrote: It looks like you missed #2. I think ::backdrop is clear enough. Not entirely sure what you would expect seeing there

Re: CfC: publish FPWD of Fullscreen spec; deadline May 24

2012-06-19 Thread fantasai
On 06/19/2012 12:40 AM, Anne van Kesteren wrote: On Tue, Jun 19, 2012 at 1:31 AM, fantasaifantasai.li...@inkedblade.net wrote: On 06/01/2012 05:02 AM, Anne van Kesteren wrote: On Wed, May 30, 2012 at 5:47 PM, fantasaifantasai.li...@inkedblade.net wrote: Though it seems likely that 'fixed'

Re: Should MutationObservers be able to observe work done by the HTML parser?

2012-06-19 Thread Adam Klein
On Sun, Jun 17, 2012 at 12:17 PM, Ryosuke Niwa rn...@webkit.org wrote: On Sun, Jun 17, 2012 at 5:03 AM, Jonas Sicking jo...@sicking.cc wrote: On Sat, Jun 16, 2012 at 7:04 AM, Rafael Weinstein rafa...@google.com wrote: I too thought we had intentionally spec'd them to not fire during load.

Re: [selectors-api] Consider backporting find() behavior to querySelector()

2012-06-19 Thread Tab Atkins Jr.
On Mon, Jun 18, 2012 at 10:59 PM, Simon Pieters sim...@opera.com wrote: On Mon, 18 Jun 2012 16:57:17 +0200, Kang-Hao (Kenny) Lu kennyl...@csail.mit.edu wrote: (12/06/18 22:45), Simon Pieters wrote: I think we should instead either fix the old API (if it turns out to not Break the Web) or

Re: CfC: publish FPWD of Fullscreen spec; deadline May 24

2012-06-19 Thread fantasai
On 06/19/2012 12:49 AM, Daniel Glazman wrote: Le 19/06/12 09:41, Anne van Kesteren a écrit : On Tue, Jun 19, 2012 at 1:45 AM, fantasaifantasai.li...@inkedblade.net wrote: It looks like you missed #2. I think ::backdrop is clear enough. Not entirely sure what you would expect seeing there

Re: Should MutationObservers be able to observe work done by the HTML parser?

2012-06-19 Thread Olli Pettay
On 06/19/2012 11:37 PM, Adam Klein wrote: On Sun, Jun 17, 2012 at 12:17 PM, Ryosuke Niwa rn...@webkit.org mailto:rn...@webkit.org wrote: On Sun, Jun 17, 2012 at 5:03 AM, Jonas Sicking jo...@sicking.cc mailto:jo...@sicking.cc wrote: On Sat, Jun 16, 2012 at 7:04 AM, Rafael

Re: CfC: publish FPWD of Fullscreen spec; deadline May 24

2012-06-19 Thread Daniel Glazman
Le 19/06/12 22:48, fantasai a écrit : You could just work in the explanation I sent in http://www.w3.org/mid/4fc64100.3060...@inkedblade.net e.g. | Each element in the top layer's stack has a ::backdrop pseudo-element, | which can be styled to create a backdrop that hides the underlying |

Re: [selectors-api] Consider backporting find() behavior to querySelector()

2012-06-19 Thread Marat Tanalin | tanalin . com
20.06.2012, 00:38, Tab Atkins Jr. jackalm...@gmail.com: On Mon, Jun 18, 2012 at 10:59 PM, Simon Pieters sim...@opera.com wrote:  On Mon, 18 Jun 2012 16:57:17 +0200, Kang-Hao (Kenny) Lu  kennyl...@csail.mit.edu wrote:  We have lots of shipped APIs with worse names. I think we should live with

RE: CfC: publish FPWD of Fullscreen spec; deadline May 24

2012-06-19 Thread Sylvain Galineau
[Daniel Glazman:] That's also the reason why I asked to explain requestFullscreen(). It can sound obvious, but it's not. And in fact, we should _never_ introduce a new syntax, API, whatever w/o saying _what it does_ from a functional point of view before explaining how it works. To the

Re: CfC: publish FPWD of Fullscreen spec; deadline May 24

2012-06-19 Thread Tobie Langel
On 6/20/12 12:05 AM, Sylvain Galineau sylva...@microsoft.com wrote: [Daniel Glazman:] That's also the reason why I asked to explain requestFullscreen(). It can sound obvious, but it's not. And in fact, we should _never_ introduce a new syntax, API, whatever w/o saying _what it does_ from

[IndexedDB] Origins and document.domain

2012-06-19 Thread Kyle Huey
By my reading, the spec does not clearly specify what the 'origin' should be. IDBFactory.open/deleteDatabase say Let origin be the origin of the IDBEnvironment used to access this IDBFactory. The IDL states Window implements IDBEnvironment; The HTML5 spec, as far as I can tell, does not define

Re: [IndexedDB] Origins and document.domain

2012-06-19 Thread Adam Barth
IndexedDB should ignore document.domain. Adam On Tue, Jun 19, 2012 at 9:06 PM, Kyle Huey m...@kylehuey.com wrote: By my reading, the spec does not clearly specify what the 'origin' should be.  IDBFactory.open/deleteDatabase say Let origin be the origin of the IDBEnvironment used to access

Re: [selectors-api] Consider backporting find() behavior to querySelector()

2012-06-19 Thread Elliott Sprehn
On Tue, Jun 19, 2012 at 1:38 PM, Tab Atkins Jr. jackalm...@gmail.comwrote: ... This is not a good argument. qSA is used often enough, and has a long enough name, that the name is actually a pretty significant misfeature. This is a pretty core API, and both it and its precursors

[IndexedDB] Extracting keys and null/undefined

2012-06-19 Thread Kyle Huey
Consider an autoincrementing IDBObjectStore with keyPath foo.bar. Which of the following (if any) should succeed? 1. objectStore.put({foo: null}); 2. objectStore.put({foo: undefined}); 3. objectStore.put({foo: {bar: null}}); 4. objectStore.put({foo: {bar: undefined}}); By my reading of the