docs conflict about default app

RESOLVED FIXED

Status

RESOLVED FIXED
9 years ago
8 years ago

People

(Reporter: myk, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
The SDK documentation you get with |cfx docs| says that Firefox is the default application for commands like |cfx testall|, but the docs that print to the console when you run cfx without options say that xulrunner is the default app.  The docs should agree (and reflect the actual default app, which looks like it's xulrunner).

Comment 1

9 years ago
Hmm, this is actually a weirdly subtle issue; the docs say that cfx tries to find Firefox, which it actually does--*but* by default it actually uses it with the '-app' argument, thereby putting Firefox into 'xulrunner mode'.

What if the text at the bottom of #guide/getting-started said this instead:

> By default, running cfx with no special options will attempt to find the
> Firefox binary in its most common location on your system and use it in
> XULRunner mode to perform the action you requested.

Or were you referring to someplace different in the docs?
(Reporter)

Comment 2

9 years ago
(In reply to comment #1)
> What if the text at the bottom of #guide/getting-started said this instead:
> 
> > By default, running cfx with no special options will attempt to find the
> > Firefox binary in its most common location on your system and use it in
> > XULRunner mode to perform the action you requested.
> 
> Or were you referring to someplace different in the docs?

That's what I was referring to, and it sounds fine, but the cfx console output should also make this clear, as currently it seems like XULRunner is the default, not "Firefox in XULRunner mode".

Comment 3

9 years ago
Hmm, how should this be expressed in the cfx console output? Internally we try to actually treat "Firefox in XULRunner mode" and "XULRunner" as the same thing.
(Reporter)

Comment 4

9 years ago
(In reply to comment #3)
> Hmm, how should this be expressed in the cfx console output? Internally we try
> to actually treat "Firefox in XULRunner mode" and "XULRunner" as the same
> thing.

I think the console output should say:

Note: --app xulrunner actually runs Firefox in XULRunner mode.  If you really want to run XULRunner, you must specify the XULRunner binary using the --binary option.
(Reporter)

Comment 5

8 years ago
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product.

To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
(Reporter)

Comment 6

8 years ago
This seems to have been fixed in the meantime.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.