Document the new external extensions path on Mac OS.

chrome/common/extensions/docs/static/external_extensions.html

Index: chrome/common/extensions/docs/static/external_extensions.html
diff --git a/chrome/common/extensions/docs/static/external_extensions.html b/chrome/common/extensions/docs/static/external_extensions.html
index 1996132c78866c9bed8e9899df6c3d88e55638c9..4950cc9a377a939edd52e0f0b41fc9c91bf1fccb 100644
--- a/chrome/common/extensions/docs/static/external_extensions.html
+++ b/chrome/common/extensions/docs/static/external_extensions.html
@@ -92,8 +92,7 @@ file available to the machine you want to install the extension on.
 <code>\\server\share\extension.crx</code>
 or <code>/home/share/extension.crx</code>.)
 </li>
-<li>Locate the <code>external_extensions.json</code> file
-  under the Google Chrome installation directory.
+<li>Locate the <code>external_extensions.json</code> file.
   If the file doesn't exist, create it.
   The location depends on the operating system.
   <dl>
@@ -103,7 +102,11 @@ or <code>/home/share/extension.crx</code>.)
     Example: <code>c:\Users\Me\AppData\Local\Google\Chrome\Application\6.0.422.0\Extensions\</code>
     </dd>
   <dt> Mac OS X: </dt>
-    <dd> <code>/Applications/Google Chrome.app/Contents/Extensions/</code> </dd>
+    <dd> <code>/Library/Application Support/Google/Chrome/External Extensions/</code> </dd>
+    <p class="note"><b>Note:</b> The external extensions file will only be read if every directory in the path is owned by the user <code>root</code>, the group <code>admin</code>, and is not world readable.  The path must also be free of symbolic links.  These restrictions prevent an unprivileged user from causing extensions to be installed for all users.  See <a href="#troubleshooting">troubleshooting</a> for details.</p>

[kathyw, 2011/09/29 20:31:20]

file will only be read if
->
file is valid only if

(move "only" closer to what it modifies, avoid future tense and passive voice)
(if you can think of a better word than "valid", go ahead and use it)

[kathyw, 2011/09/29 20:31:20]

the group -> has the group

[Sam Kerner (Chrome), 2011/09/30 15:22:04]

I went with "read" instead of "valid".

[Sam Kerner (Chrome), 2011/09/30 15:22:04]

Done.

+    <p class="note">
+    <b>Note:</b> The above path was added in Chrome 16.  Prior versions used a different path, which is now deprecated:
+    <code>/Applications/Google Chrome.app/Contents/Extensions/</code> .</p>
   <dt> Linux: </dt>
     <dd> <code>/opt/google/chrome/extensions/</code> <br>
     <b>Note:</b> Use <code>chmod</code> if necessary
@@ -150,6 +153,18 @@ Example:
 you should see the extension listed. </li>
 </ol>
 
+<h3 id="troubleshooting">Troubleshooting Mac OS permissions problems</h3>
+
+On Mac OS, if you do not see the external extension installed when Chrome is launched, there may be a permissions problem with the external extensions prefs file.  To see if this is the problem, follow these steps:

[kathyw, 2011/09/29 20:31:20]

prefs -> preferences

[Sam Kerner (Chrome), 2011/09/30 15:22:04]

Done.

+
+<ol>
+  <li> Launch the console program, under /Applications/Utilities/Console. </li>

[kathyw, 2011/09/29 20:31:20]

console program, under
->
Console program. You can find it under

(make it a little clearer that the "under" phrase just says where to find it,
not  how to launch it)

[Sam Kerner (Chrome), 2011/09/30 15:22:04]

Done.

+  <li> Click <code>Console Messages</code> in the left pane. </li>

[kathyw, 2011/09/29 20:31:20]

Insert a step above here that says something like:

<li> If the leftmost icon in the Console says "Show Log List", click that icon.
A second column appears at the left. </li>

[Sam Kerner (Chrome), 2011/09/30 15:22:04]

Done.  Good catch.

+  <li> Search for the string <code>Can not read external extensions</code>.  If there is a problem reading the external extensions file, you will find an error message.  Look for another error message directly above it, which should explain the issue.  For example, if you see the following error:

[kathyw, 2011/09/29 20:31:20]

change <code> to <b>?

<code> is pretty ugly.

[Sam Kerner (Chrome), 2011/09/30 15:22:04]

Done.

+     <code>Path /Library/Application Support/Google/Chrome is owned by the wrong group.</code>, you need to use <code>chgrp</code> or the Finder's Get Info dialog to make the file owned by the Administrator group.</li>

[kathyw, 2011/09/29 20:31:20]

Use quotation marks (double quotes) instead of <code> for "Path ... group", and
don't include the period, for readability.

[kathyw, 2011/09/29 20:31:20]

make the file owned by the
->
change the file's owner to the

(this makes it harder to misread "by" as describing the file instead of the
action of changing ownership)

[Sam Kerner (Chrome), 2011/09/30 15:22:04]

Done.

[Sam Kerner (Chrome), 2011/09/30 15:22:04]

Done.

+  <li> After fixing the issue, relaunch Chrome to try reading the external preferences file again. </li>

[kathyw, 2011/09/29 20:31:20]

Chrome to try
->
Chrome.</li>
<li> Test whether the external extension is now installed.

(It's easy to misread "to try reading", plus the important thing is testing the
installation, right?)

[Sam Kerner (Chrome), 2011/09/30 15:22:04]

Done.

+</ol>
+
 <h2 id="registry">Using the Windows registry</h2>
 
 <ol>