Closed
Bug 710216
Opened 13 years ago
Closed 12 years ago
In the tabs module documentation, mark tab.attach()'s onMessage property as optional.
Categories
(Add-on SDK Graveyard :: Documentation, defect, P2)
Add-on SDK Graveyard
Documentation
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: KWierso, Assigned: wbamberg)
Details
Attachments
(1 file)
608 bytes,
patch
|
ochameau
:
review+
|
Details | Diff | Splinter Review |
Every other property in the attach() method's constructor object is labeled optional, and the example used doesn't actually include the onMessage property, so it is also optional.
Reporter | ||
Updated•13 years ago
|
Priority: -- → P2
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → wbamberg
Assignee | ||
Comment 1•12 years ago
|
||
Attachment #599438 -
Flags: review?(poirot.alex)
Updated•12 years ago
|
Attachment #599438 -
Flags: review?(poirot.alex) → review+
Comment 2•12 years ago
|
||
Commit pushed to master at https://github.com/mozilla/addon-sdk https://github.com/mozilla/addon-sdk/commit/2a5aad4317234f3fb5afab6da8109eaf2d5e1961 Bug 710216 - In the tabs module documentation, mark tab.attach()'s onMessage property as optional.;r=@ochameau
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•