WebExtensions/DeprecationPolicy: Difference between revisions

WebExtensions/DeprecationPolicy (view source)

127 bytes added , 31 March 2017

Confirmed users

1,158

edits

Revision as of 23:21, 31 March 2017 (view source) Amckay (talk \| contribs) No edit summary ← Older edit		Revision as of 23:32, 31 March 2017 (view source) Amckay (talk \| contribs) (→‎Security) Newer edit →
Line 31:		Line 31:
	If there is a pressing security or privacy issue that a WebExtension API causes, then we would review and expedite that. Deprecation based on security would be on an as needed basis, but if it was deemed critical then most of the above would happen quickly and the block pushed to release as quickly as possible within the release management schedule.		If there is a pressing security or privacy issue that a WebExtension API causes, then we would review and expedite that. Deprecation based on security would be on an as needed basis, but if it was deemed critical then most of the above would happen quickly and the block pushed to release as quickly as possible within the release management schedule.

	To report one of these please file a bug in bugzilla and set the security flag on the bug.		To report one of these please [https://bugzilla.mozilla.org/enter_bug.cgi?product=Toolkit&component=WebExtensions:%20Untriaged&groups=toolkit-core-security file a bug in bugzilla and set the security flag on the bug].