Bug 1514809 Comment 5 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I went through the blocking bugs, and I don't think they need to be blocking the pref flip for release:

Bug 1445909 - Original design there was done before the final API (with the added `onBeforeScript` event) landed, so the actual way we handle it will likely be slightly different.  Implementing for example a `script.cancel()` method to that API seems strictly additive, and so doesn't need to be done before the main API is enabled.

Bug 1468579 - This one is a bit trickier, since it represents a security footgun for providers of userScripts addons.  But workarounds exist, and we'll make sure to document and point out the issue in our Intent To Ship announcement.


Additionally, it looks like MDN documentation might not be done before 68 hits release, so we can treat this as a "soft lunch" in 68, with the two bugs listed above landing in 69 (I don't recommend rushing and uplifting those to 68).
I went through the blocking bugs, and I don't think they need to be blocking the pref flip for release:

Bug 1445909 - Original design there was done before the final API (with the added `onBeforeScript` event) landed, so the actual way we handle it will likely be slightly different.  Implementing for example a `script.cancel()` method to that API seems strictly additive, and so doesn't need to be done before the main API is enabled.

Bug 1468579 - This one is a bit trickier, since it represents a potential security footgun for providers of userScripts addons.  But workarounds exist, and we'll make sure to document and point out the issue in our Intent To Ship announcement.


Additionally, it looks like MDN documentation might not be done before 68 hits release, so we can treat this as a "soft lunch" in 68, with the two bugs listed above landing in 69 (I don't recommend rushing and uplifting those to 68).
I went through the blocking bugs, and I don't think they need to be blocking the pref flip for release:

Bug 1445909 - Original design there was done before the final API (with the added `onBeforeScript` event) landed, so the actual way we handle it will likely be slightly different.  Implementing for example a `script.cancel()` method to that API seems strictly additive, and so doesn't need to be done before the main API is enabled.

Bug 1468579 - This one is a bit trickier, since it represents a potential security footgun for providers of userScripts addons.  But workarounds exist, and we'll make sure to document and point out the issue in our Intent To Ship announcement.


Additionally, it looks like MDN documentation might not be done before 68 hits release, so we can treat this as a "soft launch" in 68, with the two bugs listed above landing in 69 (I don't recommend rushing and uplifting those to 68).

Back to Bug 1514809 Comment 5