[Excel PowerPoint] (content addins) add support for unified manifest #4668
Conversation
|
Learn Build status updates of commit 5790b37: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 69a8f36: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit b3e33fb: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Co-authored-by: Elizabeth Samuel <[email protected]>
|
Learn Build status updates of commit 36b2f18: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
docs/design/content-add-ins.md
Outdated
| 1. Set the "code.page" object to the full URL of the page that contains the content. | ||
| 1. Optionally, set the "requestedWidth" and "requestedHeight" properties to a size between 32 and 1000 pixels. If these properties aren't used, the Office application determines the size. | ||
| 1. Optionally, set the "disableSnapshot" property to `true` to prevent Office from saving a snapshot of the content component with the document. | ||
| 1. Optionally, add a "requirements.scopes" property to restrict the installability of the content component to only Excel or only PowerPoint. The allowed values are "workbook" and "presentation". (Listing both means the content component is available in both, which is the same as having no "requirements" property at all.) |
There was a problem hiding this comment.
Looks like requirements property is on this object. If so, will you be updating the requirements property article in this PR?
There was a problem hiding this comment.
Looks like requirements property is on this object. If so, will you be updating the requirements property article in this PR?
Good catch. I should do that in the same PR.
…/OfficeDev/office-js-docs-pr into content-add-ins-unified-manifest
|
Learn Build status updates of commit 964921f: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 89ec8fe: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit a295ef8: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 97f4aaf: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
DO NOT MERGE UNTIL PUBLIC PREVIEW OF UNIFIED MANIFEST IN WXP.