Compatibility/Mobile/Non Standard Compatibility

From MozillaWiki
< Compatibility‎ | Mobile
Revision as of 14:15, 17 October 2015 by Miketaylr (talk | contribs) (→‎CSS Features: Add link to gradient bug)
Jump to navigation Jump to search

Meta tracking bug for all issues here: 1170774

Non-standard APIs and Properties required for Web Compatibility

This page contains a list of CSS and DOM properties & APIs required for compatibility with the de-facto (mobile) web.

Each is grouped into a group of relative priority, as perceived by the Web Compat team (based on known issues in Bugzilla and webcompat.com and other investigations).

Parts of this list will eventually make its way into the Compatibility Standard.

This document of WebKit stuff implemented in Microsoft Edge also serves as a guide, though not everything will be as important for Gecko.

CSS Features

Tracker bug for CSS changes: 1170789

Highest Priority

  • Enable CSS Unprefixing Service globally. 1177263

The rest of the properties below could be added to the CSS Unprefixing Service, or aliased natively, depending on what makes the most sense.

Any properties that are aliased or rewritten in CSS should also be available via the CSSOM.

High Priority

Medium Priority

  • -webkit-appearance (or at least -moz-appearance to behave in the same way 605985)
  • -background-position-x/y 550426

Lower Priority

Super Hard but would fix many cosmetic issues (maybe create more?)

  • max-width 100% inside of table (975632 + blockers/dependencies, related, etc). In the process of trying to understand this bug, I went on a journey to graph the dependencies.

max-width graph

DOM APIs

Tracker bug for DOM changes: 1170774

High Priority

  • window.orientation/orientationchange event 920734
  • WebKitCSSMatrix 717722

Medium Priority

Low Priority

  • Make any CSSUnprefixingService-backed properties available via the DOM 1181624 (we need to gather bugs that would be fixed by having this).

Video