Closed
Bug 641284
Opened 13 years ago
Closed 13 years ago
page-mod documentation should have an example using contentScriptFile
Categories
(Add-on SDK Graveyard :: Documentation, defect, P1)
Add-on SDK Graveyard
Documentation
Tracking
(Not tracked)
RESOLVED
FIXED
1.1
People
(Reporter: dietrich, Assigned: wbamberg)
Details
(Whiteboard: [cherry-pick-1.1])
Attachments
(1 file)
1.30 KB,
patch
|
dietrich
:
review+
|
Details | Diff | Splinter Review |
Because the construction of local file URLs is non-obvious and non-intuitive.
Updated•13 years ago
|
OS: Mac OS X → All
Priority: -- → P2
Hardware: x86 → All
Target Milestone: --- → 1.0
Comment 1•13 years ago
|
||
(automatic reprioritization of 1.0 bugs)
Priority: P2 → P1
Target Milestone: 1.0 → 1.1
Assignee | ||
Comment 2•13 years ago
|
||
Assignee: nobody → wbamberg
Attachment #551917 -
Flags: review?(dietrich)
Reporter | ||
Comment 3•13 years ago
|
||
Comment on attachment 551917 [details] [diff] [review] Added example using contentScriptFile Review of attachment 551917 [details] [diff] [review]: ----------------------------------------------------------------- r=me w/ these minor changes. ::: packages/addon-kit/docs/page-mod.md @@ +63,5 @@ > +### Using `contentScriptFile` ### > + > +For conciseness the examples above, and the other examples in this page, > +create content scripts as strings and use the `contentScript` property to > +assign them. This sentence is awkward. Maybe break it into two somehow? @@ +77,5 @@ > +code like: > + > + const data = require("self").data; > + > + var pageMod = require("page-mod"); This example uses const for 'data' but var for 'pageMod'. I think we should be consistent about how we bring external APIs into the current scope. But that doesn't need to be fixed just here, so it's up to you if you want to change this or not.
Attachment #551917 -
Flags: review?(dietrich) → review+
Assignee | ||
Comment 4•13 years ago
|
||
Thanks Dietrich! Landed as: https://github.com/mozilla/addon-sdk/commit/0d9f3b8778b29a8d6de572230cdaf58803c7d1d2 > > + const data = require("self").data; > > + > > + var pageMod = require("page-mod"); > > This example uses const for 'data' but var for 'pageMod'. I think we should > be consistent about how we bring external APIs into the current scope. But > that doesn't need to be fixed just here, so it's up to you if you want to > change this or not. It's a good catch: we decided we should var in all the examples, so I fixed the other ones in this file too.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Whiteboard: [cherry-pick-1.1]
You need to log in
before you can comment on or make changes to this bug.
Description
•