Re: CfC: publish FPWD of UI Events; deadline May 4

On Sat, Apr 27, 2013 at 3:30 PM, Arthur Barstow wrote: > As discussed during WebApps' April 25 meeting, this is a Call for Consensus > to publish a First Public Working Draft of the UI Events spec using the > following ED as the basis: > >

Re: CfC: publish FPWD of UI Events; deadline May 4

+1 On 04/27/2013 05:30 PM, Arthur Barstow wrote: As discussed during WebApps' April 25 meeting, this is a Call for Consensus to publish a First Public Working Draft of the UI Events spec using the following ED as the basis: This

[quota-api] Seeking status and plans for Quota Mangement API

Hi Kinuko - during WebApps' f2f meeting last week, someone asked [Mins] about the status and plans of the Quota Management API [ED] (last published in July 2012). We would appreciate it, if you would please provide a short status and plan for that spec, especially any data you have regarding im

[selectors-api2] Seeking implementation data re Selectors API Level 2

Hi Lachlan, During WebApps' f2f meeting last week, someone asked [Mins] about the implementation status of Selectors API Level 2. Do you have any implementation data re selectors-api2 you can share with us? -Thanks, AB [Mins] --

Re: Proposal for a DOM L3 Events Telecon

On Mon, Apr 29, 2013 at 12:59 PM, Travis Leithead < travis.leith...@microsoft.com> wrote: > I’d like to propose we start a call to begin to work toward resolving > the final bugs in the spec and for other business related to getting DOM L3 > Events to CR. On the call we can workout what subsequen

ZIP archive API?

Hi all, at the last TPAC there was discussion of a ZIP archive proposal. This has come and gone in various guises. Are there people currently interested in being able to work with ZIP in a web app? Are there implementors and is there an editor? cheers Chaals -- Charles McCathie Nevile - C

Re: ZIP archive API?

On Tue, Apr 30, 2013 at 1:07 PM, Charles McCathie Nevile wrote: > Hi all, at the last TPAC there was discussion of a ZIP archive proposal. > This has come and gone in various guises. > > Are there people currently interested in being able to work with ZIP in a > web app? Are there implementors and

Re: ZIP archive API?

I am very interested in working with archives. I'm currently using it as a delivery from server (like quake packs), import and export format for WebGL apps. On Tue, Apr 30, 2013 at 3:18 PM, Anne van Kesteren wrote: > On Tue, Apr 30, 2013 at 1:07 PM, Charles McCathie Nevile > wrote: > > Hi all,

Re: [Shadow DOM] Simplifying level 1 of Shadow DOM

On Apr 25, 2013, at 2:42 PM, Edward O'Connor wrote: > First off, thanks to Dimitri and others for all the great work on Shadow > DOM and the other pieces of Web Components. While I'm very enthusiastic > about Shadow DOM in the abstract, I think things have gotten really > complex, and I'd like to

Re: [Shadow DOM] Simplifying level 1 of Shadow DOM

The thing about reprojection is that it makes implementers life harder but it makes developers life easy. I'd rather have us do the hard work here. For the record, we have two independent implementations of the Shadow DOM spec so that should debunk some of the myths that this is too hard to implem

Re: [Shadow DOM] Simplifying level 1 of Shadow DOM

I'm concerned that we're over engineering here. I do understand adding reprojection significantly reduces the need to write author scripts, but I would like to see us implement the truly minimal set of features, have all browsers ship it, and see how authors, particularly that of high profile we

Re: [Shadow DOM] Simplifying level 1 of Shadow DOM

On 4/30/13 1:52 PM, Erik Arvidsson wrote: For the record, we have two independent implementations of the Shadow DOM spec Do we? Correct ones that are actually shipping in a UA? -Boris

Re: [Shadow DOM] Simplifying level 1 of Shadow DOM

I'm concerned that if the spec shipped as you described, that it would not be useful enough to developers to bother using it at all. Without useful redistributions, authors can't use composition of web components very well without scripting. At that point, it's not much better than just leaving it

[webcomponents]: Comprehensive update of Custom Elements spec

Greetings, fellow public-webappsters! Over the past few weeks, I've been digging through implementation feedback and bugs, and polishing the Custom Elements spec. I think it is now in a pretty nice state, so come lookit: https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/custom/index.html Not

Re: Collecting real world use cases (Was: Fixing appcache: a proposal to get us started)

On Apr 18, 2013 6:19 PM, "Paul Bakaus" wrote: > > Hi Jonas, > > Thanks for this ­ I feel this is heading somewhere, finally! I still need > to work on submitting my full feedback, but I'd like to mention this: Why > did nobody so far in this thread include real world use cases? > > For a highly co

Re: Fixing appcache: a proposal to get us started

On Mon, Apr 1, 2013 at 4:03 AM, Glenn Jones wrote: > I think this outline for improving AppCache is a really good start, but I > can see one major problem with it. As you point out AppCache was initially > designed for building simple single page web apps. > > >> The appcache appears to be aimed a

Re: Fixing appcache: a proposal to get us started

On Wed, Apr 3, 2013 at 5:50 AM, Robin Berjon wrote: > On 29/03/2013 21:08 , Jonas Sicking wrote: >> >> * Cache both files (poor bandwidth) >> * We could enable some way of flagging which context different URLs >> are expected to be used in. That way the UA can send the normal >> content negotiatio

Re: Fixing appcache: a proposal to get us started

On Mon, Apr 8, 2013 at 12:17 AM, Mark Nottingham wrote: > Hi Jonas, > > I don't get a good sense from this proposal (and NavigationController) about > what the scope of an application is. E.g., if both > http://example.com/fooApp > and > http://example.com/barApp > say that they both grab the

Re: Fixing appcache: a proposal to get us started

On 01/05/2013, at 2:20 PM, Jonas Sicking wrote: > The current AppCache spec suffers from this too, but only once users > go offline. I.e. I can use FALLBACK to take over > http://users.example.edu/~alice/ using a resource from from > http://users.example.edu/~bob/newalice.html > > But that only