WebAPI/WidgetAPI: Difference between revisions
< WebAPI
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
===embed-widgets === | ===embed-widgets === | ||
In order to expose to privileged APPs and consider security issue.<br /> | In order to expose to privileged APPs and consider security issue.<br /> | ||
"embed-widgets" is a new permission for "mozapp" attribute, it comes from 'embed-apps' but more | "embed-widgets" is a new permission for "mozapp" attribute, it comes from 'embed-apps' but has more restriction. {{bug|1005818}} | ||
<iframe mozapp="manifesturl" mozwidget="mywidget1"> | <iframe mozapp="manifesturl" mozwidget="mywidget1"> | ||
Revision as of 07:32, 12 May 2014
Widget API
The widget API allows privileged APPs have ability to embed APPs in their own APP.
Use case
Proposal
embed-widgets
In order to expose to privileged APPs and consider security issue.
"embed-widgets" is a new permission for "mozapp" attribute, it comes from 'embed-apps' but has more restriction. bug 1005818
<iframe mozapp="manifesturl" mozwidget="mywidget1">
extend manifest.webapp
Declare details of widget in mainfest.
{
name: "MyApp2000",
...
widgets: {
"mywidget1": {
href: "widget.html"
positions: ["homescreen", "lockscreen"]
description: "This is my cool widget"
},
"myotherwidget": { ... }
}
}