Compatibility/System Addon/Override Policies and Workflows: Difference between revisions

Jump to navigation Jump to search
→‎Preamble: Update language in preamble
m (→‎Generic Process of adding an override: Add note about needing more process.)
(→‎Preamble: Update language in preamble)
Line 1: Line 1:
== Preamble ==
== Preamble ==


There is no fixed guideline or a checklist on when to add an override or not. Instead, this project is rather dynamic and depends on the individual case. This document provides some help in making that decision.
If important sites are broken in Firefox, getting them fixed is our highest priority (even if by the user agent intervening on behalf of the user). However, there's a balance to be struck: we do not have the bandwidth to fix the entire web, and patching certain problem may disincentivize developers from fixing their bugs.


In general, decisions are made rather fast and we are able to roll out new overrides to the users quickly. ['''ToDo''': Who makes the decision? I feel like more than one person should be involved, but I am not sure who. Maybe a quick discussion on the webcompat bug to see if anyone has objections?]
As a guiding principle, if deploying a site patch or override would dramatically improve user experience or fix a top site it should be seriously considered. At the same time, we make efforts to remove the override as soon as possible, working with the site developers where possible.
 
The user is more important than the web and the web is more important than browser vendors. If sites are broken, getting them working again should have the highest priority. On the other hand, if we add overrides every time something breaks, we might not be able to convince the site developers to roll out a fix since the site will be working in their tests.


== Override or not? ==
== Override or not? ==
Confirmed users
796

edits

Navigation menu