- From: Paul Kinlan <paulkinlan@google.com>
- Date: Mon, 19 Dec 2011 21:43:59 +0000
- To: Bjartur Thorlacius <svartman95@gmail.com>
- Cc: WebIntents <public-web-intents@w3.org>, gbillock@google.com
- Message-ID: <CADGdg3DNqS6PuQNj_5NMAgiVtYySk72tBRTkVnLyBOmwoXWTtA@mail.gmail.com>
The publisher needs to be in control of where the actions are placed inside their experience. The actual picker will be managed by the user agent. For sites that don't support the actions the UA could have them embedded in their chrome as generic actions to take place on the users command in consistent places in the browser (such as the URL bar or menus). But that is up to the UA. On Dec 19, 2011 9:38 PM, "Bjartur Thorlacius" <svartman95@gmail.com> wrote: > My understanding was that sites are responsible for showing the picker > interface for users to select actions. That is what I oppose. > > If a user wants to have "bookmark this" and "post to reddit" buttons in a > certain place, should he modify his UA to expose a bookmarking API to all > websites, email authors of all websites he may read and ask them to add > both "bookmark this" and "post to reddit" to the place of choice in > disregard for the preferences of other readers of the websites. > > I don't want any buttons visible while I'm reading text or watching > pictures. I've got a menu button for when I need them. Another user might > want buttons to appear when he has scrolled through all the page. A third > user on a wide screen might want a load of always-visible buttons in a > sidebar. > > The code that places and shows buttons has to be reused, so device makers > can optimize it for their input and output devices and users configure it > to their liking. > -- > -,Bjartur > >
Received on Monday, 19 December 2011 21:44:35 UTC