I'm not an expert on <engine> requirements, but I'm happy to review your post.
-Michal On Tue, Sep 30, 2014 at 12:41 PM, Ray Camden <rayca...@adobe.com> wrote: > Ah, good point there. > > I¹m going to write up a blog post on this after I run some errands. I¹d > love a quick review from you, or anyone, before I publish. I¹m also going > to add something to the core docs. > > > On 9/30/14, 11:18 AM, "Michal Mocny" <mmo...@chromium.org> wrote: > > >That sounds reasonable. > > > >The <engine> tag is a bit weird though, in that the dependency is on cli > >and not platform version. Combined with CLI semver and platform release > >unbundling, its a bit hard to reason about. It kinda still works because > >we have default platform versions pinned to cli versions, but users can > >explicitly install non-default platform versions if they chose, and > >plugins > >may have support for only a subset of platforms.. > > > >-Michal > > > >On Tue, Sep 30, 2014 at 12:11 PM, Ray Camden <rayca...@adobe.com> wrote: > > > >> Ah - never mind. I picked a plugin that didn¹t have it specified. I > >>picked > >> another random one and it *was* shown. > >> > >> I¹d say that for plugins w/o engine support, the site should still say > >> something, even if > >> > >> Engine Number > >> Not Specified > >> > >
