Extensions Manifest V2 support #3246
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mikehoffms
commented
Aug 12, 2024
|
|
||
|
|
||
| <!-- ====================================================================== --> | ||
| ## Providing feedback | ||
|
|
||
| Microsoft continues to iteratively improve the platform and address the feedback shared by extension developers. Share your questions, comments, and concerns with the team on Twitter [@MSEdgeDev](https://twitter.com/msedgedev/) or via the [Microsoft Edge Insider forums on TechCommunity](https://techcommunity.microsoft.com/t5/articles/manifest-v3-changes-are-now-available-in-microsoft-edge/m-p/1780254). |
There was a problem hiding this comment.
these two links are not mentioned in
https://learn.microsoft.com/microsoft-edge/extensions-chromium/publish/contact-extensions-team
@sivMSFT
mikehoffms
commented
Aug 12, 2024
| <!-- ------------------------------ --> | ||
| #### Timeline for MV2-based extensions | ||
|
|
||
| The move to Manifest V3 improves the security, privacy, and performance of extensions. Our current strategy for Microsoft Edge is to support new MV3-based extensions and support updates to existing MV2-based extensions from our partner ecosystem. Microsoft Edge Extensions will continue to support updates for MV2-based extensions for an extended period of time, and we will communicate with our partner ecosystem when we plan the deprecation of existing MV2-based extensions. For enterprises, Manifest V2 extensions will continue to be supported through Enterprise policies at least until the date in the Chromium Manifest V2 support timeline. |
There was a problem hiding this comment.
the initial draft text:
MV2 timeline for Enterprise:
We see the move to MV3 as a change in the positive direction to improve security, privacy and performance of extensions. Our current strategy is to honour any new mv3 extensions from our partner ecosystem and any updates to existing mv2 extensions. At the same time, we will continue updates for MV2 extensions for an extended period of time and will communicate once we plan deprecation of existing mv2 extensions. For enterprises, Manifest V2 extensions will continue to be supported through Enterprise policies at least until the date in the Chromium Manifest V2 support timeline.
mikehoffms
commented
Aug 12, 2024
| Manifest V2 extensions will continue to be supported through Enterprise policies at least until the date in the Chromium Manifest V2 support timeline. | ||
|
|
||
| <!-- ------------------------------ --> | ||
| #### Timeline for MV2-based extensions |
There was a problem hiding this comment.
Suggested change
| #### Timeline for MV2-based extensions | |
| #### Timeline for MV2-based extensions for Enterprise partners |
not sure how specific/focused the section is, @sivMSFT
mikehoffms
changed the title
|
Learn Build status updates of commit 0a98e00: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 8b22310: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 721f12a: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
mikehoffms
commented
Aug 14, 2024
| ## Manifest timeline for the Chromium browser engine | ||
|
|
||
| Chromium has revised the timelines for ending support for Manifest V2. See: | ||
| Chromium has revised the timelines for ending support for Manifest V2.<!-- todo: add "in/for Chrome"? --> See: |
There was a problem hiding this comment.
Suggested change
| Chromium has revised the timelines for ending support for Manifest V2.<!-- todo: add "in/for Chrome"? --> See: | |
| Chromium has revised the timelines for ending support for Manifest V2 in Google Chrome. See: |
@sivMSFT tech review this suggested change
mikehoffms
commented
Aug 14, 2024
mikehoffms
commented
Aug 14, 2024
|
|
||
| To help you plan the migration of your extension from Manifest V2 to Manifest V3, consider the following schedule for support for Manifest V2 and V3 in Microsoft Edge and Microsoft Partner Center. | ||
|
|
||
| The Microsoft Edge team will independently decide on MV3 migration timelines for Microsoft Edge Add-ons and share an update here. We continue to analyze the concerns raised by extension developers and explore the optimal path for the Microsoft Edge Add-ons ecosystem. Meanwhile, to plan the migration of your extension from Manifest V2 to Manifest V3, see [Manifest timeline for the Chromium browser engine](#manifest-timeline-for-the-chromium-browser-engine), above. | ||
| The Microsoft Edge team will independently decide on MV3 migration timelines for Microsoft Edge Add-ons and share an update here.<!-- todo: revise wording in this h2 section? --> We continue to analyze the concerns raised by extension developers and explore the optimal path for the Microsoft Edge Add-ons ecosystem.<!-- todo: change to "for Microsoft Edge Add-ons." 'ecosystem' is undefined in these articles; if it's a needed term, define it --> Meanwhile, to plan the migration of your extension from Manifest V2 to Manifest V3, see [Manifest timeline for the Chromium browser engine](#manifest-timeline-for-the-chromium-browser-engine), above. |
There was a problem hiding this comment.
Suggested change
| The Microsoft Edge team will independently decide on MV3 migration timelines for Microsoft Edge Add-ons and share an update here.<!-- todo: revise wording in this h2 section? --> We continue to analyze the concerns raised by extension developers and explore the optimal path for the Microsoft Edge Add-ons ecosystem.<!-- todo: change to "for Microsoft Edge Add-ons." 'ecosystem' is undefined in these articles; if it's a needed term, define it --> Meanwhile, to plan the migration of your extension from Manifest V2 to Manifest V3, see [Manifest timeline for the Chromium browser engine](#manifest-timeline-for-the-chromium-browser-engine), above. | |
| Independently from the Chromium engine and Google Chrome, the Microsoft Edge team will decide on MV3 migration timelines for Microsoft Edge Add-ons and share an update here.<!-- todo: revise wording in this h2 section? --> We continue to analyze the concerns raised by extension developers and explore the optimal path for the Microsoft Edge Add-ons ecosystem.<!-- todo: change to "for Microsoft Edge Add-ons." 'ecosystem' is undefined in these articles; if it's a needed term, define it --> Meanwhile, to plan the migration of your extension from Manifest V2 to Manifest V3, see [Manifest timeline for the Chromium browser engine](#manifest-timeline-for-the-chromium-browser-engine), above. |
to clarify: "independently" from what?
@sivMSFT - techreview this particular change of a few words
mikehoffms
commented
Aug 14, 2024
|
|
||
| To help you plan the migration of your extension from Manifest V2 to Manifest V3, consider the following schedule for support for Manifest V2 and V3 in Microsoft Edge and Microsoft Partner Center. | ||
|
|
||
| The Microsoft Edge team will independently decide on MV3 migration timelines for Microsoft Edge Add-ons and share an update here. We continue to analyze the concerns raised by extension developers and explore the optimal path for the Microsoft Edge Add-ons ecosystem. Meanwhile, to plan the migration of your extension from Manifest V2 to Manifest V3, see [Manifest timeline for the Chromium browser engine](#manifest-timeline-for-the-chromium-browser-engine), above. | ||
| The Microsoft Edge team will independently decide on MV3 migration timelines for Microsoft Edge Add-ons and share an update here.<!-- todo: revise wording in this h2 section? --> We continue to analyze the concerns raised by extension developers and explore the optimal path for the Microsoft Edge Add-ons ecosystem.<!-- todo: change to "for Microsoft Edge Add-ons." 'ecosystem' is undefined in these articles; if it's a needed term, define it --> Meanwhile, to plan the migration of your extension from Manifest V2 to Manifest V3, see [Manifest timeline for the Chromium browser engine](#manifest-timeline-for-the-chromium-browser-engine), above. |
There was a problem hiding this comment.
Suggested change
| The Microsoft Edge team will independently decide on MV3 migration timelines for Microsoft Edge Add-ons and share an update here.<!-- todo: revise wording in this h2 section? --> We continue to analyze the concerns raised by extension developers and explore the optimal path for the Microsoft Edge Add-ons ecosystem.<!-- todo: change to "for Microsoft Edge Add-ons." 'ecosystem' is undefined in these articles; if it's a needed term, define it --> Meanwhile, to plan the migration of your extension from Manifest V2 to Manifest V3, see [Manifest timeline for the Chromium browser engine](#manifest-timeline-for-the-chromium-browser-engine), above. | |
| The Microsoft Edge team will independently decide on MV3 migration timelines for Microsoft Edge Add-ons and share an update here.<!-- todo: revise wording in this h2 section? --> We continue to analyze the concerns raised by extension developers and explore the optimal path for Microsoft Edge Add-ons. Meanwhile, to plan the migration of your extension from Manifest V2 to Manifest V3, see [Manifest timeline for the Chromium browser engine](#manifest-timeline-for-the-chromium-browser-engine), above. |
'ecosystem' is undefined in these articles; if it's a needed term, define it
@sivMSFT - techreview this particular change of a couple words
mikehoffms
commented
Aug 14, 2024
| @@ -60,10 +61,49 @@ The Microsoft Edge team will independently decide on MV3 migration timelines for | |||
| | TBD | Microsoft Partner Center will no longer accept updates to existing Manifest V2 extensions. Developers can submit updates for migrating a V2 extension to V3. | Microsoft Edge stops running Manifest V2 extensions. Enterprises can allow Manifest V2 extensions to run on Microsoft Edge, by using enterprise policies. | | |||
| | TBD | No change. | Manifest V2 extensions will no longer function in Microsoft Edge, even with the use of enterprise policies. | | |||
|
|
|||
| Manifest V2 extensions will continue to be supported through Enterprise policies at least until the date in the Chromium Manifest V2 support timeline. | |||
| <!-- todo: existing MV2 extensions already published on the Microsoft Edge Add-ons website can be updated until the end of FY-24. [what Month/Day?] This timeline is subject to change. --> | |||
There was a problem hiding this comment.
Suggested change
| <!-- todo: existing MV2 extensions already published on the Microsoft Edge Add-ons website can be updated until the end of FY-24. [what Month/Day?] This timeline is subject to change. --> | |
| Existing MV2 extensions already published on the Microsoft Edge Add-ons website can be updated until December 31, 2024. This timeline is subject to change. |
@sivMSFT - add this statement? if so, this statement should be moved into the summary table. is date correct?
mikehoffms
commented
Aug 14, 2024
| Manifest V2 extensions will continue to be supported through Enterprise policies at least until the date in the Chromium Manifest V2 support timeline. | ||
| <!-- todo: existing MV2 extensions already published on the Microsoft Edge Add-ons website can be updated until the end of FY-24. [what Month/Day?] This timeline is subject to change. --> | ||
|
|
||
| <!-- todo: at TBDs, add "see below"? or, replace right-hand cell content by the main point that's below? --> |
There was a problem hiding this comment.
in the summary table, replace "tbd" by some other wording -- possibly "see below", but really, all the substantial points in this section should be moved into the summary table.
@sivMSFT
mikehoffms
commented
Aug 14, 2024
| <!-- ------------------------------ --> | ||
| #### Timeline for ending support for Manifest V2-based Microsoft Edge extensions for enterprises | ||
|
|
||
| <!-- todo: orig draft wording, for reference: |
There was a problem hiding this comment.
i'll delete this provided draft wording. instead of adding such a paragraph to the h2 section, better to condense the h2 section, fully leveraging the summary table.
@sivMSFT
mikehoffms
commented
Aug 14, 2024
| For enterprises, Manifest V2 extensions will continue to be supported through Enterprise policies at least until the date in the Chromium Manifest V2 support timeline. | ||
| --> | ||
|
|
||
| The move to Manifest V3 improves the security, privacy, and performance of extensions.<!-- todo: delete sentence about MV3, b/c off-topic for this "MV2" section --> |
There was a problem hiding this comment.
Suggested change
| The move to Manifest V3 improves the security, privacy, and performance of extensions.<!-- todo: delete sentence about MV3, b/c off-topic for this "MV2" section --> |
delete sentence about MV3, b/c off-topic for this "MV2" section
mikehoffms
commented
Aug 14, 2024
| --> | ||
|
|
||
| The move to Manifest V3 improves the security, privacy, and performance of extensions.<!-- todo: delete sentence about MV3, b/c off-topic for this "MV2" section --> | ||
| Our current strategy for Microsoft Edge is to support new MV3-based extensions and support updates to existing MV2-based extensions from our partner ecosystem.<!-- todo: delete sentence b/c the mv3 point is off-topic for this "MV2" section, & the mv2 point is redundant w/ next, clearer sentence --><!-- todo: delete "from our partner ecosystem" b/c it's undefined & redundant or superfluous; not needed: can there exist any existing MV2-based extensions that are not from our partner ecosystem? --> |
There was a problem hiding this comment.
Suggested change
| Our current strategy for Microsoft Edge is to support new MV3-based extensions and support updates to existing MV2-based extensions from our partner ecosystem.<!-- todo: delete sentence b/c the mv3 point is off-topic for this "MV2" section, & the mv2 point is redundant w/ next, clearer sentence --><!-- todo: delete "from our partner ecosystem" b/c it's undefined & redundant or superfluous; not needed: can there exist any existing MV2-based extensions that are not from our partner ecosystem? --> |
delete sentence, b/c the mv3 point is off-topic for this "MV2" section, & the mv2 point is redundant w/ the next, clearer sentence
mikehoffms
commented
Aug 14, 2024
| --> | ||
|
|
||
| The move to Manifest V3 improves the security, privacy, and performance of extensions.<!-- todo: delete sentence about MV3, b/c off-topic for this "MV2" section --> | ||
| Our current strategy for Microsoft Edge is to support new MV3-based extensions and support updates to existing MV2-based extensions from our partner ecosystem.<!-- todo: delete sentence b/c the mv3 point is off-topic for this "MV2" section, & the mv2 point is redundant w/ next, clearer sentence --><!-- todo: delete "from our partner ecosystem" b/c it's undefined & redundant or superfluous; not needed: can there exist any existing MV2-based extensions that are not from our partner ecosystem? --> |
There was a problem hiding this comment.
Suggested change
| Our current strategy for Microsoft Edge is to support new MV3-based extensions and support updates to existing MV2-based extensions from our partner ecosystem.<!-- todo: delete sentence b/c the mv3 point is off-topic for this "MV2" section, & the mv2 point is redundant w/ next, clearer sentence --><!-- todo: delete "from our partner ecosystem" b/c it's undefined & redundant or superfluous; not needed: can there exist any existing MV2-based extensions that are not from our partner ecosystem? --> | |
| Our current strategy for Microsoft Edge is to support new MV3-based extensions and support updates to existing MV2-based extensions. |
if we keep this sentence, delete "from our partner ecosystem", b/c it's undefined & redundant or superfluous; not needed: can there exist any existing MV2-based extensions that are not from our partner ecosystem?
mikehoffms
commented
Aug 14, 2024
|
|
||
| The move to Manifest V3 improves the security, privacy, and performance of extensions.<!-- todo: delete sentence about MV3, b/c off-topic for this "MV2" section --> | ||
| Our current strategy for Microsoft Edge is to support new MV3-based extensions and support updates to existing MV2-based extensions from our partner ecosystem.<!-- todo: delete sentence b/c the mv3 point is off-topic for this "MV2" section, & the mv2 point is redundant w/ next, clearer sentence --><!-- todo: delete "from our partner ecosystem" b/c it's undefined & redundant or superfluous; not needed: can there exist any existing MV2-based extensions that are not from our partner ecosystem? --> | ||
| Microsoft Edge Extensions will continue to support updates for MV2-based extensions for an extended period of time, and we will communicate with extension developers when we plan the deprecation of existing MV2-based extensions.<!-- todo: move this sentence to be first --> |
There was a problem hiding this comment.
move this key sentence to be first - or better, move it into the summary table and get rid of this new h4 subsection
@sivMSFT
mikehoffms
commented
Aug 14, 2024
| The move to Manifest V3 improves the security, privacy, and performance of extensions.<!-- todo: delete sentence about MV3, b/c off-topic for this "MV2" section --> | ||
| Our current strategy for Microsoft Edge is to support new MV3-based extensions and support updates to existing MV2-based extensions from our partner ecosystem.<!-- todo: delete sentence b/c the mv3 point is off-topic for this "MV2" section, & the mv2 point is redundant w/ next, clearer sentence --><!-- todo: delete "from our partner ecosystem" b/c it's undefined & redundant or superfluous; not needed: can there exist any existing MV2-based extensions that are not from our partner ecosystem? --> | ||
| Microsoft Edge Extensions will continue to support updates for MV2-based extensions for an extended period of time, and we will communicate with extension developers when we plan the deprecation of existing MV2-based extensions.<!-- todo: move this sentence to be first --> | ||
| For enterprises, Manifest V2 extensions will continue to be supported through Enterprise policies at least until the date in the Chromium Manifest V2 support timeline.<!-- todo: revise phrase "at least ... timeline" --> |
There was a problem hiding this comment.
revise the phrase "at least until the date in the Chromium Manifest V2 support timeline", b/c that's the problem that this PR is intended to fix & clarify.
@sivMSFT
that's the sentence that appears in live docs
https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/developer-guide/manifest-v3#manifest-timeline-for-microsoft-edge-and-partner-center
mikehoffms
commented
Aug 14, 2024
| Microsoft Edge Extensions will continue to support updates for MV2-based extensions for an extended period of time, and we will communicate with extension developers when we plan the deprecation of existing MV2-based extensions.<!-- todo: move this sentence to be first --> | ||
| For enterprises, Manifest V2 extensions will continue to be supported through Enterprise policies at least until the date in the Chromium Manifest V2 support timeline.<!-- todo: revise phrase "at least ... timeline" --> | ||
|
|
||
| <!-- todo: delete almost all instances of "we", "our", "us", per https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/w/we --> |
There was a problem hiding this comment.
delete almost all instances of "we", "our", "us", per https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/w/we
mikehoffms
commented
Aug 14, 2024
| <!-- ====================================================================== --> | ||
| ## Providing feedback | ||
|
|
||
| <!-- todo: when to use twitter, techcommunity, or github forum? --> |
There was a problem hiding this comment.
when to use twitter, techcommunity, or github forum?
@sivMSFT
mikehoffms
commented
Aug 14, 2024
|
|
||
| To help you plan the migration of your extension from Manifest V2 to Manifest V3, consider the following schedule for support for Manifest V2 and V3 in Microsoft Edge and Microsoft Partner Center. | ||
|
|
||
| The Microsoft Edge team will independently decide on MV3 migration timelines for Microsoft Edge Add-ons and share an update here. We continue to analyze the concerns raised by extension developers and explore the optimal path for the Microsoft Edge Add-ons ecosystem. Meanwhile, to plan the migration of your extension from Manifest V2 to Manifest V3, see [Manifest timeline for the Chromium browser engine](#manifest-timeline-for-the-chromium-browser-engine), above. | ||
| The Microsoft Edge team will independently decide on MV3 migration timelines for Microsoft Edge Add-ons and share an update here.<!-- todo: revise wording in this h2 section? --> We continue to analyze the concerns raised by extension developers and explore the optimal path for the Microsoft Edge Add-ons ecosystem.<!-- todo: change to "for Microsoft Edge Add-ons." 'ecosystem' is undefined in these articles; if it's a needed term, define it --> Meanwhile, to plan the migration of your extension from Manifest V2 to Manifest V3, see [Manifest timeline for the Chromium browser engine](#manifest-timeline-for-the-chromium-browser-engine), above. |
There was a problem hiding this comment.
"team will ... share an update here"
below, it says instead:
"we will communicate with extension developers when we plan the deprecation of existing MV2-based extensions."
need to bring together & reconcile these two different, similar statements: we will update this page AND communicate [how?] with [all??] extension developers.
@sivMSFT
|
Learn Build status updates of commit 98ddbc7: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit cc7927b: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 3868d17: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 946d90c: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit bc364dd: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 3d21436: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 76ec097: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 00ffc8b: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit f5dea8c: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 29f5517: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit d19ba90: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Closing Without Merging this PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rendered article section for review:
AB#53185346