Re: [selectors-api] RfC: LCWD of Selectors API Level 1; deadline July 19

On 2012-08-06 13:25, Lachlan Hunt wrote: On 2012-08-06 13:08, Kang-Hao (Kenny) Lu wrote: (12/07/31 20:06), Arthur Barstow wrote: On 7/19/12 11:15 PM, ext Kang-Hao (Kenny) Lu wrote: http://lists.w3.org/Archives/Public/public-webapps/2012JanMar/thread#msg518 I think this is a very minor issue,

Re: [selectors-api] RfC: LCWD of Selectors API Level 1; deadline July 19

On Mon, Aug 6, 2012 at 7:13 PM, Kang-Hao (Kenny) Lu wrote: > (12/08/06 19:25), Lachlan Hunt wrote: >> On 2012-08-06 13:08, Kang-Hao (Kenny) Lu wrote: >> I'd rather find a way to address the issue. I've just been a bit busy >> with other tasks for the last 2 weeks to look into this. >> >> I'd like

Re: [selectors-api] RfC: LCWD of Selectors API Level 1; deadline July 19

(12/08/06 19:25), Lachlan Hunt wrote: > On 2012-08-06 13:08, Kang-Hao (Kenny) Lu wrote: > I'd rather find a way to address the issue. I've just been a bit busy > with other tasks for the last 2 weeks to look into this. > > I'd like feedback from implementers about how best to address the issue. >

RE: [selectors-api] RfC: LCWD of Selectors API Level 1; deadline July 19

> From: Lachlan Hunt [mailto:lachlan.h...@lachy.id.au] > > I'd like feedback from implementers about how best to address the issue. > The options I can think of: > > 1. Disallow all comments within the selector for this API. Throw SyntaxError > when they are used. > 2. Allow comments, but defin

Re: [selectors-api] RfC: LCWD of Selectors API Level 1; deadline July 19

On Mon, Aug 6, 2012 at 4:25 AM, Lachlan Hunt wrote: > On 2012-08-06 13:08, Kang-Hao (Kenny) Lu wrote: >> I think this is a very minor issue, and it has a simple workaround - >> mark it as undefined. However, if Lachlan doesn't feel like paying extra >> fee for versionning (what Anne calls "make wo

Re: [selectors-api] RfC: LCWD of Selectors API Level 1; deadline July 19

On 2012-08-06 13:08, Kang-Hao (Kenny) Lu wrote: (12/07/31 20:06), Arthur Barstow wrote: On 7/19/12 11:15 PM, ext Kang-Hao (Kenny) Lu wrote: http://lists.w3.org/Archives/Public/public-webapps/2012JanMar/thread#msg518 I completely missed that comment of yours when you originally sent it, which

Re: [selectors-api] RfC: LCWD of Selectors API Level 1; deadline July 19

(12/07/31 20:06), Arthur Barstow wrote: > On 7/19/12 11:15 PM, ext Kang-Hao (Kenny) Lu wrote: >> Sorry for my late comment. >> >> While I think it's fine to publish LCWD Selectors API as it is, it would >> be nice if it can address my comment in [1]. By "address", I mean either >> define the desire

Re: [selectors-api] RfC: LCWD of Selectors API Level 1; deadline July 19

On 7/19/12 11:15 PM, ext Kang-Hao (Kenny) Lu wrote: Sorry for my late comment. While I think it's fine to publish LCWD Selectors API as it is, it would be nice if it can address my comment in [1]. By "address", I mean either define the desired behavior or explicitly mark it as undefined (which I

[selectors-api] RfC: LCWD of Selectors API Level 1; deadline July 19

Sorry for my late comment. While I think it's fine to publish LCWD Selectors API as it is, it would be nice if it can address my comment in [1]. By "address", I mean either define the desired behavior or explicitly mark it as undefined (which I think is better than not saying anything because an e

Re: [selectors-api] RfC: LCWD of Selectors API Level 1; deadline July 19

On 2012-06-28 18:03, Stewart Brodie wrote: Arthur Barstow wrote: This is a Request for Comments for the June 28 Last Call Working Draft of Selectors API Level 1: The comment deadline is July 19 and all comments should be sent to the publ

Re: [selectors-api] RfC: LCWD of Selectors API Level 1; deadline July 19

Arthur Barstow wrote: > This is a Request for Comments for the June 28 Last Call Working Draft > of Selectors API Level 1: > > > > The comment deadline is July 19 and all comments should be sent to the > public-webapps@w3.org list with a