> 2) How do you actually see this integrating with the existing snippets > service? As I understand it, the snippets service that desktop uses serves > up web content, which is rendered directly in about:home (including running > JS). I suppose we could have the service serve us an add-on, or we could > support some simplified markup that we could convert into the appropriate > API calls, but I don't see us ever having the same kind of flexibility that > desktop has as long as we're creating this promo banner in native UI. Also, > the content from desktop snippets runs with content privileges, so if we do > start supporting running JS from this service, we should make sure to take > the same security precautions. > > I don't think we want this to integrate at all with the desktop snippet > service. This is totally separate. The add-on will decide where the > snippets are coming from and when to update them. The JS API only needs to > be able to show the information and respond to closes and clicks. And yes, > we will be more constrained by the type of "parts" in the banner: Icon, > Title and Message? The message could allow some basic span formatting - > whatever Java gives us for free. > > Thanks for clarifying. Reading the project page, I was confused about how the snippets service and the add-on both fit into the story, but this makes sense. We may want to update the project page to explain that part of building this add-on is going to depend on the snippets service serving up a totally different kind of content for mobile. If you read the snippets wiki page [1], it talks about how snippets are currently just a chunk of HTML, but for mobile we can probably ask whoever runs snippets.mozilla.comto create an endpoint that serves up JSON.
Margaret [1] https://wiki.mozilla.org/Websites/Snippets/about:home_101
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
