- From: Andrei Popescu <andreip@google.com>
- Date: Mon, 26 Jul 2010 15:08:58 +0100
- To: Anne van Kesteren <annevk@opera.com>
- Cc: Jonas Sicking <jonas@sicking.cc>, Henri Sivonen <hsivonen@iki.fi>, "public-html@w3.org WG" <public-html@w3.org>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Hi Anne, Thanks for the comments! On Mon, Jul 26, 2010 at 2:50 PM, Anne van Kesteren <annevk@opera.com> wrote: > On Thu, 22 Jul 2010 20:21:29 +0200, Jonas Sicking <jonas@sicking.cc> wrote: >> >> On Thu, Jul 22, 2010 at 10:52 AM, Andrei Popescu <andreip@google.com> >> wrote: >>> >>> But I am not sure I understand what prevents you from doing both. You >>> can render your two buttons for the existing millions of pages. If >>> some new pages do specify the capture parameter, you can just hide the >>> irrelevant button. What is the drawback to that? >> >> That could be an ok solution I agree. > > It seems better to me to start out simple first. Ok, but is 'capture' that complex / complicated? It seems to me very easy to implement and use. > Like Jonas I'm not too > convinced the capture parameter is really justified. > I see. What would it take to convince you? We have a real world application presenting a pretty reasonable use case for it. Thanks, Andrei
Received on Monday, 26 July 2010 14:09:36 UTC