Closed
Bug 649038
Opened 14 years ago
Closed 13 years ago
enable the content api
Categories
(Mozilla Labs :: F1, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mixedpuppy, Unassigned)
References
Details
(Whiteboard: [low-prio])
We removed the content api when we were trying to land for fx5, now that we are looking towards fx6 we would like to renable it (conversation with clarkbw).
We should follow the Navigator API section in https://github.com/mozilla/f1/wiki/Proposal:-Extensible-Share-API rather than the older version at https://github.com/mozilla/f1/wiki/navigator-share-api
|
||
Comment 1•14 years ago
|
||
(In reply to comment #0)
> We removed the content api when we were trying to land for fx5, now that we are
> looking towards fx6 we would like to renable it (conversation with clarkbw).
This will in all likelihood require bug 641552. I would like us to not block on this. If it makes the Firefox 6 train, good. If not, we can always land it later.
Depends on: 641552
|
Reporter | |
Updated•14 years ago
|
Whiteboard: [low-prio]
|
|
Reporter | |
Updated•13 years ago
|
Component: Share: Firefox Client → F1
Product: Mozilla Services → Mozilla Labs
QA Contact: share-fx-client → f1
|
|
Reporter | |
Comment 2•13 years ago
|
||
content api is inherited from owa, invokeService provides the capability.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•