Closed Bug 409936 Opened 17 years ago Closed 17 years ago

[Mac] First Run page tells my mom to "right-click"

Categories

(www.mozilla.org :: General, defect)

x86
macOS
defect
Not set
minor

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jruderman, Assigned: sgarrity)

References

()

Details

Firefox's "First Run" page says 

  Right-click on a link and select “Open Link in New Tab”

My mom asked me how to "right-click" and I was embarrassed to have to explain "there is no right-click on Mac; when things ask you to 'right-click' they mean hold Control and click".  Since the first thing my mom did when she got her new Macbook was download Firefox, this was her first encounter with the term "right-click".

The first run page should probably say

  Control-click on a link and select "Open Link in New Tab"

or even better, avoiding the context menu entirely:

  Hold the Command key and click a link
Assignee: nobody → reed
Good catch - I'll make sure this gets fixed.
This has been fixed.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Great, thanks.  But two more changes are needed:

1. A misplaced close-paren in the script makes it not work.

  if (document.getElementById('tab-info' != null))
should be
  if (document.getElementById('tab-info') != null)

2. In both the Windows/Linux text and the Mac text, the verb used with Ctrl+T (or Command+T) should be "pressing" or "typing", not "clicking".
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee: reed → steven
Status: REOPENED → NEW
JS syntax error was my mistake - thanks. That is fixed as is the misused term "clicking" (I went with "pressing").
We'll need to be careful when pushing this stuff to production as there are some plugin-check JS changes also on Stage that aren't ready for production (I don't think?).
Status: NEW → RESOLVED
Closed: 17 years ago17 years ago
Resolution: --- → FIXED
(In reply to comment #5)
> We'll need to be careful when pushing this stuff to production as there are
> some plugin-check JS changes also on Stage that aren't ready for production (I
> don't think?).

We're safe; https://www.mozilla.com/en-US/firefox/plugincheck/ is a 404.

I checked, and Jesse's comments are all fixed on production; Verified FIXED.
Status: RESOLVED → VERIFIED
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.