Program Management/Programs/Apps/Site Compatibility: Difference between revisions
| Line 13: | Line 13: | ||
[https://bugzilla.mozilla.org/buglist.cgi?list_id=2517736;resolution=---;op_sys=Android;query_format=advanced;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;product=Tech%20Evangelism Tech Evangelism Android bugs] | [https://bugzilla.mozilla.org/buglist.cgi?list_id=2517736;resolution=---;op_sys=Android;query_format=advanced;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;product=Tech%20Evangelism Tech Evangelism Android bugs] | ||
== | ==CSS== | ||
There are two CSS issues that relate to site compat: | |||
* performance of graphically intensive properties | |||
* -webkit and -moz prefixed properties | |||
< | The layout team is currently focusing on mobile performance to meet or exceed webkit capabilities on identical hardware. The focus is on -webkit and -moz CSS properties that are graphically intensive (transforms, transitions, and animations.) The plan is to improve our performance first and, in parallel, to work on unprefixing those properties in the W3C CSS standards. | ||
<bugzilla> | |||
{ | |||
"id": "702739,725095,539356,524925" | |||
} | |||
</bugzilla> | |||
==Firefox browser specific issues== | ==Firefox browser specific issues== | ||
Revision as of 18:33, 7 March 2012
Site Compatibility
There are a number of issues that can affect the appearance and functionality of a site on a given platform. This page contains a number of issues that are being tracked that affect site compatibility as it relates to apps. At this point much of the focus is on mobile.
Comparison testing
Aaron Train (QA) has a script that automatically captures screenshots of sites using various UA strings. This testing shows differences based on the UA string and webkit compatiblity. The latest results are available at: [1]
Serving the right site
Many sites have mobile specific versions but these versions are not served to Firefox mobile. The primary reason is that the sites are sniffing the UA string and do not correctly identify the Firefox mobile UA string. In these cases either the full desktop site or an older WAP site may be returned to Firefox.
Evangelism is solving this problem by speaking directly with site owners to update the UA sniffing logic to include the Firefox UA.
Fennec Native Evangelism bugs
Tech Evangelism Android bugs
CSS
There are two CSS issues that relate to site compat:
- performance of graphically intensive properties
- -webkit and -moz prefixed properties
The layout team is currently focusing on mobile performance to meet or exceed webkit capabilities on identical hardware. The focus is on -webkit and -moz CSS properties that are graphically intensive (transforms, transitions, and animations.) The plan is to improve our performance first and, in parallel, to work on unprefixing those properties in the W3C CSS standards.
| ID | Summary | Priority | Status |
|---|---|---|---|
| 524925 | Avoid reflows for transform changes | -- | RESOLVED |
| 539356 | Replace Invalidate() calls in reflow with display list analysis | -- | RESOLVED |
| 702739 | Pre-render overflow area of frames translated by CSS transforms, that are active and partially visible | -- | RESOLVED |
| 725095 | [Meta] OMTC: Land Android compositor | P1 | RESOLVED |
4 Total; 0 Open (0%); 4 Resolved (100%); 0 Verified (0%);
Firefox browser specific issues
There are issues that may be Firefox specific as well, such as not recognizing touch inputs. These issues may be due to differences between gecko and webkit.
TODO: Determine if there are additional issues that fall in this category.