On Friday, May 10, 2013 at 6:35 PM, Matt Basta wrote:
> > If the W3C format starts using an array instead of an object, backwards > > compatibility can be retained with existing FxOS content (if type is object > > === Mozilla format; if type is array === W3C format). Of course, if we > > start using the W3C format, we would need to deprecate using an object. > > This isn't backwards compatibility since existing devices that implement the > old standard will still break. You are correct, my bad. When an array is used, the array is ignored (in which case, the default icon is shown). <snip - moving platform detection to different thread> > There is a lot that can be done with icons, but removing information from the > manifest in a backwards-incompatible way probably isn't the right way to go. Right, but I'm still interested in addressing the high density display use cases and dealing with the issues I mentioned. Dealing with icons is quite fiddly at the moment. _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
