Confirmed users
564
edits
Blocklisting/Graphics: Difference between revisions
Jump to navigation
Jump to search
→Blocklisting Process: Added limitations and details section.
(Created page with "Blocklisting graphics drivers is the process of causing Firefox to not use some or all of its hardware acceleration features on a given device, potentially for a limited set of d...") |
Msreckovic (talk | contribs) (→Blocklisting Process: Added limitations and details section.) |
||
| Line 31: | Line 31: | ||
# The [[Blocklisting/Blocked_Graphics_Drivers|Blocked Graphics Drivers]] page will be updated with details on the block. | # The [[Blocklisting/Blocked_Graphics_Drivers|Blocked Graphics Drivers]] page will be updated with details on the block. | ||
# The blocklist item will be pushed to production. | # The blocklist item will be pushed to production. | ||
= Blocklisting Details and Limitations = | |||
There are some things that one should be aware of when modifying or interpreting the blocklist for graphics. | |||
* Until version 41 (bug 1162299) any features in the blocklist would be interpreted as "all features" by the versions that do not know about those features. For example, FEATURE_STAGEFRIGHT was added in Gecko version 17. If FEATURE_STAGEFRIGHT was added to the downloadable blocklist, all versions prior to version 17 would automatically block all features that otherwise match that blocklist entry. | |||
* Until version 41 (bug 1162530) all blocklist entries applied to all Gecko versions. We introduced the graphics blocklist entry versioning, which let us specify the minimum and maximum version that any particular blocklist entry applies to. Note that the versions include nightly/aurora/beta suffixes, so if you wanted a blocklist entry to apply to all versions after version 42, for example, you would specify minVersion as 43.0a1. | |||
* Downloadable blocklists are usually only downloaded once a day, and cached in the profile directory (as blocklist.xml.) Modifying that file is often the best way to do local testing of changes, before proceeding with the staging of the modified blocklist file. | |||
* Even with the local blocklist file, note that we don't necessarily check against it every run, so your testing should involve multiple runs. | |||
= More Information = | = More Information = | ||