Using an array for "orientation" in manifest

[Anant Narayanan]

cvan points out in https://bugzilla.mozilla.org/show_bug.cgi?id=784574
that using a comma-seperated list for the orientation property in the
manifest is inconsistent with all the other fields.

I agree, as parsing a comma-seperated list is extra work, so we should
simply use an array of strings. The behavior will remain exactly the same.

If there are no major objection, I propose we make this switch as soon
as possible. If someone could point me to the best way to make the
update to all the Gaia manifests in one swoop, that would be great!

Cheers,
-Anant

[Jonas Sicking]

I don't care that strongly either way, but note.that using a string matches
what the screen.lockOrientation takes. Of course, that is as of yet just a
proposal and could be changed too.

/ Jonas
On Aug 24, 2012 3:40 AM, "Anant Narayanan" <an...@mozilla.com> wrote:

> cvan points out in https://bugzilla.mozilla.org/**show_bug.cgi?id=784574<https://bugzilla.mozilla.org/show_bug.cgi?id=784574>that using a comma-seperated list for the orientation property in the

> ______________________________**_________________
> dev-webapps mailing list
> dev-w...@lists.mozilla.org
> https://lists.mozilla.org/**listinfo/dev-webapps<https://lists.mozilla.org/listinfo/dev-webapps>
>

[Mounir Lamouri]

On 08/24/2012 11:05 AM, Jonas Sicking wrote:
> I don't care that strongly either way, but note.that using a string matches
> what the screen.lockOrientation takes. Of course, that is as of yet just a
> proposal and could be changed too.

I'm going to change the specification and Mozilla's implementation to
accept a string or an array of string in screen.lockOrientation().
So, it's fine to accept that in the manifest I believe.

--
Mounir