Compatibility/Desktop: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "=Desktop Web Compatibility= ==What Are Web Compatibility Issues?== '''A person should be able to use the Web with whichever browser they choose.''' Unfortunately, some deve...")
 
m (→‎Background: add mention of Edge)
 
(5 intermediate revisions by 2 users not shown)
Line 7: Line 7:


==Background==
==Background==
Desktop web compatibility has a '''long history''' at Mozilla. Many of the compatibility issues from the past have been resolved thanks to the efforts of Mozilla volunteers, staff and web developers adopting web standards. This doesn't mean there aren't problems in the current state. A small percentage of ghosts of issues past do still linger on the web. Also with the high adoption of Webkit, some developers are choosing to use non-standard code without a Gecko equivalent or not test their sites with other browsers. Some of the same issues are happening for Microsoft's Trident engine.
Desktop web compatibility has a '''long history''' at Mozilla. Many of the compatibility issues from the past have been resolved thanks to the efforts of Mozilla volunteers, staff and web developers adopting web standards. This doesn't mean there aren't problems in the current state. A small percentage of ghosts of issues past do still linger on the web. Also with the high adoption of Webkit, some developers are choosing to use non-standard code without a Gecko equivalent or not test their sites with other browsers. Some of the same issues are happening for Microsoft's Trident engine, and to a lesser extent the EdgeHTML engine.


==Goal==
==Goal==


Unlike [[Compatibility/Mobile|Mobile Web Compatibility]] desktop has no dedicated Mozilla resources allocated and is mostly driven by volunteers at the moment. The vague goal for this project is to continue to pursue equal opportunity for all desktop browsers and maintain the standards based environment we enjoy ''' for the most part''' today.
The vague goal for this project is to continue to pursue equal opportunity for all desktop browsers and maintain the standards based environment we enjoy ''' for the most part''' today.


===Scope===
===Scope===
Line 21: Line 21:
;Out of scope
;Out of scope
* Site enhancements  
* Site enhancements  
* Trivial site layout or functional bugs
* Issues caused by tracking protection or ad-blocking
* Issues caused by add-ons


== Get Involved ==
== Get Involved ==
Line 31: Line 32:
*Contacting Web sites for solving the issues
*Contacting Web sites for solving the issues


Get started here: [https://bugzilla.mozilla.org/buglist.cgi?f1=component&list_id=8384365&o1=notequals&resolution=---&query_format=advanced&v1=Mobile&product=Tech%20Evangelism List of Desktop Web Compatibility issues]
Get started here: [https://bugzilla.mozilla.org/buglist.cgi?product=Tech%20Evangelism&component=Desktop&resolution=---&list_id=13134991 List of Desktop Web Compatibility issues]
 
==Sorting Desktop Bugs==
 
In previous years there were large volumes of web compatibility bugs for Desktop and with it became [https://bugzilla.mozilla.org/describecomponents.cgi?product=Tech%20Evangelism more categories] in Bugzilla to organize them. There are currently many language components that these bugs are sorted to, the largest being "[https://bugzilla.mozilla.org/buglist.cgi?component=English%20US&product=Tech%20Evangelism&query_format=advanced&resolution=---&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&limit=0&list_id=10190566 English US]". In order to make it easier to monitor and maintain, all desktop bugs that are still valid are being moved to the [https://bugzilla.mozilla.org/buglist.cgi?product=Tech%20Evangelism&component=Desktop&resolution=---&list_id=10190589 Desktop component] in Bugzilla.
 
Two other areas in Tech Evangelism on Bugzilla to be aware of are "[https://bugzilla.mozilla.org/buglist.cgi?product=Tech%20Evangelism&component=Mobile&resolution=--- Mobile]" and "[https://bugzilla.mozilla.org/buglist.cgi?product=Tech%20Evangelism&component=Preinstalled%20B2G%20Apps&resolution=--- Preinstalled B2G Apps]". These bugs do not belong to Desktop Tech Evangelism and should not be moved.


==Old Tech Evangelism Bugs==
==Old Tech Evangelism Bugs==

Latest revision as of 21:24, 26 July 2016

Desktop Web Compatibility

What Are Web Compatibility Issues?

A person should be able to use the Web with whichever browser they choose.

Unfortunately, some developers by choice or negligence will make their Web sites unusable by specific devices or browsers. We need to open up the Web to any rendering engines (Blink, Gecko, Trident, etc.) and/or browsers.

Background

Desktop web compatibility has a long history at Mozilla. Many of the compatibility issues from the past have been resolved thanks to the efforts of Mozilla volunteers, staff and web developers adopting web standards. This doesn't mean there aren't problems in the current state. A small percentage of ghosts of issues past do still linger on the web. Also with the high adoption of Webkit, some developers are choosing to use non-standard code without a Gecko equivalent or not test their sites with other browsers. Some of the same issues are happening for Microsoft's Trident engine, and to a lesser extent the EdgeHTML engine.

Goal

The vague goal for this project is to continue to pursue equal opportunity for all desktop browsers and maintain the standards based environment we enjoy for the most part today.

Scope

In scope
  • Any site that serves a desktop optimized version
  • Any locale
Out of scope
  • Site enhancements
  • Issues caused by tracking protection or ad-blocking
  • Issues caused by add-ons

Get Involved

You can help keep the web open on desktop by:

  • Reporting Web sites issues
  • Analyzing Web sites issues
  • Contacting Web sites for solving the issues

Get started here: List of Desktop Web Compatibility issues

Old Tech Evangelism Bugs

There are some desktop bugs in Bugzilla that are very old, some dating back to the early 2000's. These bugs should be treated the same as any bug today. If the issue still exists, move the bug to the Desktop component and leave a comment.

There is also a video walk through that explains how to assess these bugs.