Hi Chris, Mike,

I've added the information that I know based on your feedback.

1. Are they going to be distributed in some special area of the Fx
> marketplace eventually?
>

We currently have no plans to do this, though I would very much like to
when the API is more stabilized.

3. "Add-ons count as a cross-origin resource, originating at their origin."
> - as in, the origin of the app? So therefore CORS is needed? A little more
> info would be nice here.
>

I don't know much more about this. I just vaguely remember seeing CORS
errors. I thought that it would be better to include a note on this than
nothing at all, so that someone who figures it out more could add to the
documentation.

Doug

On Mon, Jun 8, 2015 at 7:34 PM, Douglas Sherk <[email protected]> wrote:

> Hi Chris, Mike,
>
> I've added the information that I know based on your feedback.
>
> 1. Are they going to be distributed in some special area of the Fx
>> marketplace eventually?
>>
>
> We currently have no plans to do this, though I would very much like to
> when the API is more stabilized.
>
> 3. "Add-ons count as a cross-origin resource, originating at their
>> origin." - as in, the origin of the app? So therefore CORS is needed? A
>> little more info would be nice here.
>>
>
> I don't know much more about this. I just vaguely remember seeing CORS
> errors. I thought that it would be better to include a note on this than
> nothing at all, so that someone who figures it out more could add to the
> documentation.
>
> Doug
>
> On Mon, Jun 8, 2015 at 2:17 PM, Michael Henretty <[email protected]>
> wrote:
>
>> How does one disable Developer Mode? Can we we add this to the doc?
>>
>> On Mon, Jun 8, 2015 at 4:53 AM, Chris Mills <[email protected]> wrote:
>>
>>>
>>> > On 8 Jun 2015, at 08:56, Douglas Sherk <[email protected]> wrote:
>>> >
>>> > Hi all,
>>> >
>>> > I've added articles to the MDN on Firefox OS Add-ons and Developer
>>> Mode, which are both relatively new and previously undocumented features.
>>>
>>> Thanks for the great coverage, Doug.
>>>
>>> >
>>> > https://developer.mozilla.org/en-US/Firefox_OS/Add-ons
>>>
>>> Cool! I have given this an edit, and I had a few comments you might want
>>> to address:
>>>
>>> 1. Are they going to be distributed in some special area of the Fx
>>> marketplace eventually?
>>>
>>> 2. In the sample manifest section, it might be nice to include a few
>>> regular expressions examples, to give people an idea of how to use them in
>>> this context.
>>>
>>> 3. "Add-ons count as a cross-origin resource, originating at their
>>> origin." - as in, the origin of the app? So therefore CORS is needed? A
>>> little more info would be nice here.
>>>
>>> 4. "Simple example" - have you got this addon available anywhere to link
>>> to, say in a github repo?
>>>
>>> “I also added information about the new manifest features here:
>>>
>>> https://developer.mozilla.org/en-US/Apps/Build/Manifest#role
>>> https://developer.mozilla.org/en-US/Apps/Build/Manifest#customizations
>>>
>>> > https://developer.mozilla.org/en-US/Firefox_OS/Developer_Mode
>>>
>>> Looking pretty good; just made some minor edits. One comment:
>>>
>>> 1. Where it says "there's a problem" (multiple instances), some
>>> troubleshooting information would be nice, if possible.
>>>
>>> One last thing — I am not 100% sure that where you have put these
>>> articles is the best place for them, although it certainly makes them
>>> findable. They probably fit best into The apps center and the tools zone,
>>> respectively. I’ve cc’d my MDN colleague Will, who owns the Tools and
>>> Add-ons docs, so we can discuss where would be best to put these.
>>>
>>> All the best,
>>>
>>> Chris Mills
>>>   Senior tech writer || Mozilla
>>> developer.mozilla.org || MDN
>>>   [email protected] || @chrisdavidmills
>>>
>>>
>>>
>>> _______________________________________________
>>> dev-gaia mailing list
>>> [email protected]
>>> https://lists.mozilla.org/listinfo/dev-gaia
>>>
>>
>>
>
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to