Program Management/Programs/Apps/Site Compatibility: Difference between revisions

Jump to navigation Jump to search
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]


==-webkit prefix==
==CSS==
As Chrome and Safari are both webkit based browsers there are a sites that use the -webkit css prefix. Firefox doesn't currently recognize the -webkit prefix resulting in different rendering of sites in the Firefox browser.<br/>
There are two CSS issues that relate to site compat:
<br/>
* performance of graphically intensive properties
The layout team is currently investigating.<br/>
* -webkit and -moz prefixed properties
<br/>
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.
TODO: Contact Jet for details.
<bugzilla>
    {
        "id": "702739,725095,539356,524925"
    }
</bugzilla>


==Firefox browser specific issues==
==Firefox browser specific issues==
Confirmed users
2,473

edits

Navigation menu