On Sat, Jun 27, 2015 at 5:51 AM, Marcos Caceres <mar...@marcosc.com> wrote:
>
> These look fantastic! so why not start with just those? Or are all those
> card types done and thoroughly tested on a good chunk of Web content? As I
> mentioned before, I'd be worried about the amount of error recovery
> code that will be needed just for those types of cards. (Sorry, I don't
> know any of the background and if you've already dealt with this).
>
We will definitely start with the simple open graph stuff that Ted
mentioned ("og:title", "og:type", "og:url", "og:image", "og:description")
since they are so widely used. And yes, even these simple ones are
problematic. For instance, when navigating between dailymotion videos they
keep the current meta tags, and just updates the html body content. In
fact, single-page-apps in general are hard here. Also, on the mobile
version of youtube they leave out og tags entirely, probably as a
performance optimization. Turns out, many sites do this. So in 2.5 we will
have to account for all of this and the solution might not be pretty.
I think Microformats addresses the aforementioned problems. But if youtube,
wikipedia, pinterest, twitter, facebook, tumblr, etc don't use them widely
what is the point of supporting them in a moz-internal API? Let's be
pragmatic and start with og. What's the next biggest win for us? Is the
data clear? Ben seems to think JSON-LD [1], does anyone have data to the
contrary?
1.)
https://groups.google.com/d/msg/mozilla.dev.platform/5sUoRTPDnSE/24ckuPSydjQJ
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
