Compatibility/WebPlatform: Difference between revisions
Jump to navigation
Jump to search
(creating page about Web compat and creating/removing new web features.) |
m (→Mitigation through site interventions: fix typo) |
||
| Line 34: | Line 34: | ||
@@ explain how we site interventions can help fix websites during a transition phase. | @@ explain how we site interventions can help fix websites during a transition phase. | ||
[[Category:Compatibility]] | [[Category:Web Compatibility]] | ||
Latest revision as of 04:24, 14 March 2022
Status: EARLY DRAFT - @@ means there's text to be written. Provide also ways on how the webcompat team can help.
Evolving Web Platform and Web Compat
There is a process for exposing new Web feature. When doing so, some of the issues are related to Web Compatibility risks. Here some guidelines on what you could do or experiment to assess the Web Compatibility risks.
Creating a new Web exposed feature
Name Conflict
@@ Example: MooTools, and array…
Deprecating a Web exposed feature
Telemetry
@@ Assessing if the feature deprecated is widely used.
@@ Example: window.installTrigger
Impossible or very hard to fix
@@ CSS Zoom.
Cascading breakage because of adding/removing a feature
@@ example: window.event -> charCode/keyCode
Mitigation through site interventions
@@ explain how we site interventions can help fix websites during a transition phase.