# Migrating to Manifest v3

**URL:** <https://discourse.mozilla.org/t/migrating-to-manifest-v3/35784>\
**Category:** Development\
**Created:** [February 7, 2019, 9:26pm UTC](https://discourse.mozilla.org/t/migrating-to-manifest-v3/35784 "2019-02-07T21:26:20Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![caitlin](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/caitlin/32/6091_2.png) [@caitlin](https://discourse.mozilla.org/u/caitlin)\
**Post date:** [February 27, 2019, 9:36pm UTC](https://discourse.mozilla.org/t/migrating-to-manifest-v3/35784/4 "2019-02-27T21:36:33Z")

</div>

Like I mentioned earlier, we’re still monitoring Chrome’s manifest v3 proposals. Their [recent post](https://groups.google.com/a/chromium.org/forum/#!topic/chromium-extensions/WcZ42Iqon_M) indicates that they are still iterating on some of the ideas they would like to implement, including changes that would impact content-blockers.

Regardless of what happens with Chrome’s manifest v3 proposals, we want to ensure that ad-blockers and other similarly powerful extensions that contribute to user safety and privacy remain part of Mozilla’s add-ons ecosystem while also making sure that users are not being exposed to extreme risks via malicious use of powerful APIs.

---

_[View the full topic](https://discourse.mozilla.org/t/migrating-to-manifest-v3/35784)._
