Compatibility: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎What is Web Compatibility: adding a taxonomy)
(→‎Core Team: Alphabetical order)
 
(14 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<div style="display:flex" class="webc-wrapper">
<div style="flex: 2 1 auto">
= Web Compatibility =
= Web Compatibility =


'''A person should be able to use the Web with any devices and browsers.'''
<div style="width: 80%; padding: 1em 2em; background-color: #fc0;font-size: 1.5rem;margin:auto;">
A person should be able to use the Web with any devices and browsers.
</div>


Our attempt is to help both website developers and browser implementers to reach a point where users have no issues when browsing the Web because of their choices.
Our attempt is to help both website developers and browser implementers to reach a point where users have no issues when browsing the Web because of their choices.


== Contact Us ==
=== Cross Browsers. Any vendors ===
* [https://webcompat.com/ Web Compatibility bug reporting] (Cross Browsers. Any vendors)
* [https://twitter.com/WebCompat @WebCompat] on twitter
* [https://twitter.com/MozWebCompat @MozWebCompat] for Mozilla Web compatibility issues


== Our activity ==
== Our activity ==
Line 16: Line 14:


* Our [[Compatibility/Projects|current projects]].
* Our [[Compatibility/Projects|current projects]].
== What is Web Compatibility ==
Web Compatibility issues are related to Web sites implementing techniques that create issues for a certain class of browsers and/or devices. A person will not be able to use a Web site according to his/her own choices.


=== Mozilla Staff ===
These issues are cross-platforms, cross-products and related to the Web as a whole. There are circumstances when a company will choose to use a standardized techniques which is not available for an old browser, but that should be mitigated in making the [http://christianheilmann.com/2012/02/16/stumbling-on-the-escalator/ Web site usable in any circumstances]. So if a person is using the last version of [[Firefox]] or a vocal browser such as Jaws, or a proxy browser such as Opera Mini or UCWeb, the Web site should be able to work.
 
[[Mozilla]] has two areas for dealing with Web Compatibility issues. The goal is to make the Web usable by anyone and not only Firefox products, but we will focus the efforts on solving issues for Firefox users.


The web compatibility team is composed of:
Web Compatibility issues can change over time, we keep an updated list of the most [[Compatibility/CommonIssues|common issues]].


* Oana Arbuzov - oana (IRC) - compat triage and testing team
=== Evolving Web Platform ===
* Sergiu Logigan - sergiu (IRC) - compat triage and testing team
* [[User:Adam_s|Adam Stevenson]] - adam_s (IRC), developer experience team
* [[User:Olagasidlo|Ola Gasidlo]] - ola (IRC), developer experience team
* [[User:DenSchub|Dennis Schubert]] - denschub (IRC), compat tools team
* [[User:Karlcow|Karl Dubost]] - karlcow (IRC), compat tools team
* [[User:Miketaylr|Mike Taylor]] miketaylr (IRC), compat tools team manager
* Thomas Wisniewski - twisniewski (IRC), compat tools team


== Meetings ==
Sometimes Web Compatibility issues are created by the browsers themselves when the technology [[ExposureGuidelines|evolves by either adding a new feature or deprecating a feature]], if you are a browser implementer you may want to [[Compatibility/WebPlatform|seek assistance from the Web Compatibility team]] to evaluate the risk of deprecating and unshipping a Web exposed feature.
 
</div>
<div style="flex: 1 1 200px; margin-left: 1em; background-color:#eee;padding:.5em;border: 1px solid #ddd;">


=== Weekly Meeting ===
== Core Team ==


The team has a public meeting every Tuesday at 6am PST*.
{| class="wikitable"
{| class="wikitable"
|-
|-
! Day of week !! Pacific Time !! Eastern Time !! UTC !! Central European Time !! Japan Time
! Name !! Matrix !! GitHub !! Role
|-
| [[User:DenSchub|Dennis Schubert]] || denschub || denschub || Diagnosis / Site Interventions
|-
| James Graham || jgraham || jgraham  || Web Platform Test
|-
| [[User:Ksenia|Ksenia Berezina]] || ksy36 || ksy36 || Diagnosis/ Webcompat.com / Machine Learning
|-
| Martin Balfanz || mbalfanz || martinbalfanz || Product Management
|-
| Oana Arbuzov || oana || softvision-oana-arbuzov  || Triage/Testing
|-
|-
| Tuesdays || 6:00AM - 7:00AM || 9:00AM - 10:00AM || 2:00PM - 3:00PM || 3:00PM - 4:00PM || 10:00PM - 11:00PM (summer)<br/>11:00PM - 12:00PM (winter)
| Raul Bucata || raulbucata|| softvision-raul-bucata || Triage/Testing
|-
|-
| Thomas Wisniewski || twisniewski || wisniewskit || Diagnosis / ETP Shims
|}
|}


* If there are no agenda items on the [https://public.etherpad-mozilla.org/p/webcompat public etherpad], there is no meeting.
== Meetings ==
* See our [[Compatibility/Meetings]] for more details and [[Compatibility/Meetings|minutes]].


=== Tech Evangelism Triage ===
We hold Weekly [[Compatibility/Meetings|meetings]] every Tuesday at 6am PST (if we have something to discuss).
== Contact Us ==
* [https://webcompat.com/issues/new Report a Bug] (Cross Browsers. Any vendors)
* [https://twitter.com/WebCompat @WebCompat]
* [https://twitter.com/MozWebCompat @MozWebCompat] for Mozilla Web compatibility issues


All are welcome to participate.
</div>
</div>


The current goal is to triage the backlog and make sure we haven't missed important bugs to be diagnosed, or to catch what has been fixed. Anything deemed not important will be made P5, and won't appear in query results.


* Thursdays, 8am Pacific, Vidyo Channel Compatibility
== Web Compatibility Taxonomy ==
* [https://mzl.la/2H9Qzc6 Untriaged Tech Evangelism::Desktop and ::Mobile with no priority (minus P5s)]


== What is Web Compatibility ==
[[Compatibility/Taxonomy|Why sites are failing in Firefox?]] What can we do when this is happening?
Web Compatibility issues are related to Web sites implementing techniques that create issues for a certain class of browsers and/or devices. A person will not be able to use a Web site according to his/her own choices.
 
These issues are cross-platforms, cross-products and related to the Web as a whole. There are circumstances when a company will choose to use a standardized techniques which is not available for an old browser, but that should be mitigated in making the [http://christianheilmann.com/2012/02/16/stumbling-on-the-escalator/ Web site usable in any circumstances]. So if a person is using the last version of [[Firefox]] or a vocal browser such as Jaws, or a proxy browser such as Opera Mini or UCWeb, the Web site should be able to work.
 
[[Mozilla]] has two areas for dealing with Web Compatibility issues. The goal is to make the Web usable by anyone and not only Firefox products, but we will focus the efforts on solving issues for Firefox users.
 
Web Compatibility issues can change over time, we keep an updated list of the most [[Compatibility/CommonIssues|common issues]].
 
=== Web Compatibility Taxonomy ===
 
Why sites are failing in Firefox? What can we do when this is happening?
 
 
* '''The Web site is using a specific vendor technology'''. Examples: Think about prefixed CSS and JavaScript. Specific codec for video supported only in one browser, platform, …
** We can outreach the site. Long process and not always successful
** We may be able to shim it inside Firefox while attempting to do outreach.
** We can fix it in Firefox if really widespread on too may sites. It becomes (unfortunately) part of the Web reality.
* '''The Web site is sending a specific working version of the site'''. Often based on user agent sniffing both on the client side or/and the server side. Examples: Different tier version for different browsers (Google search, Baidu, etc.). These can be very difficult to solve. It's more business related than a technical issue.
** We can outreach to the site, if we can demonstrate that the other version is working well in Firefox.
** We can create a UA override in some circumstances. Drawback: we disappear from the statistics.
* '''The Web site is sending to a specific interactions of the site through features detections.'''
** We can outreach to the site.
** We can try to shim it.
* '''The Web site is using a standard technology not yet supported by Firefox.''' Example: SpeechRecognition. This creates a load of secondary issues such as adding future code detection legacies. The Webcompat issues of today are sometimes created by the lack of support of technologies of yesterdays.
** We need to fix it in Firefox.
* '''The Web site is using a non-standard technology not yet supported by Firefox.''' Example from the past: innerText, window.event, … These are hard to fix. When we fix it in Firefox, we create secondary compatibility issues, because sites were relying on it. Example: using window.event, to target the detection of keyCode.
** We can fix it in Firefox, but we need to deal with the consequences too.
** We can outreach if the problem is not widespread.


== Web Compatibility Issues  ==
== Web Compatibility Issues  ==
Line 93: Line 76:
! Status !! Bugzilla !! Webcompat.com  
! Status !! Bugzilla !! Webcompat.com  
|-
|-
| To triage ||[https://mzl.la/2PLx4ep 🐝] || [https://webcompat.com/issues?page=1&per_page=50&state=open&stage=needstriage&sort=created&direction=desc 🐝]
| To triage ||[https://mzl.la/3lpjj3Z 🐝] || [https://webcompat.com/issues?page=1&per_page=50&state=open&stage=needstriage&sort=created&direction=desc 🐝]
|-
|-
| To diagnose ||[https://mzl.la/2BZAyH1 🐝] || [https://webcompat.com/issues?page=1&per_page=50&state=open&stage=needsdiagnosis&sort=created&direction=desc 🐝]
| To diagnose ||[https://mzl.la/3nzE7aX 🐝] || [https://webcompat.com/issues?page=1&per_page=50&state=open&stage=needsdiagnosis&sort=created&direction=desc 🐝]
|-
|-
| Find a contact ||[https://mzl.la/2MZkRnQ 🐝] || [https://webcompat.com/issues?page=1&per_page=50&state=open&stage=needscontact&sort=created&direction=desc 🐝]
| Find a contact ||[https://mzl.la/3jPGHHC 🐝] || [https://webcompat.com/issues?page=1&per_page=50&state=open&stage=needscontact&sort=created&direction=desc 🐝]
|-
|-
| To contact || [https://mzl.la/2PeWb8e 🐝]|| [https://webcompat.com/issues?page=1&per_page=50&state=open&stage=contactready&sort=created&direction=desc 🐝]
| To contact || [https://mzl.la/2Idp0Uj 🐝]|| [https://webcompat.com/issues?page=1&per_page=50&state=open&stage=contactready&sort=created&direction=desc 🐝]
|-
|-
|}
|}
Line 109: Line 92:
** [https://wiki.mozilla.org/Compatibility/Test_Plan Test Plan]
** [https://wiki.mozilla.org/Compatibility/Test_Plan Test Plan]
** [https://wiki.mozilla.org/Compatibility/Lessons_Learned Lessons Learned]
** [https://wiki.mozilla.org/Compatibility/Lessons_Learned Lessons Learned]
== WebCompat Tracking and Triage ==
https://wiki.mozilla.org/Compatibility/WebCompat_Tracking_And_Triage


== Web Compatibility How-To ==  
== Web Compatibility How-To ==  
Line 115: Line 101:
== Web Compatibility Summit ==
== Web Compatibility Summit ==
[[ WebCompat Summit (2015)]]
[[ WebCompat Summit (2015)]]
[[Category:Web Compatibility]]
[[Category:Web Compatibility]]

Latest revision as of 16:41, 27 January 2026

Web Compatibility

A person should be able to use the Web with any devices and browsers.

Our attempt is to help both website developers and browser implementers to reach a point where users have no issues when browsing the Web because of their choices.


Our activity

The Web Compatibility activity is composed of permanent Mozilla staff and volunteer contributors. We are part of the Developer Experiences Team.

What is Web Compatibility

Web Compatibility issues are related to Web sites implementing techniques that create issues for a certain class of browsers and/or devices. A person will not be able to use a Web site according to his/her own choices.

These issues are cross-platforms, cross-products and related to the Web as a whole. There are circumstances when a company will choose to use a standardized techniques which is not available for an old browser, but that should be mitigated in making the Web site usable in any circumstances. So if a person is using the last version of Firefox or a vocal browser such as Jaws, or a proxy browser such as Opera Mini or UCWeb, the Web site should be able to work.

Mozilla has two areas for dealing with Web Compatibility issues. The goal is to make the Web usable by anyone and not only Firefox products, but we will focus the efforts on solving issues for Firefox users.

Web Compatibility issues can change over time, we keep an updated list of the most common issues.

Evolving Web Platform

Sometimes Web Compatibility issues are created by the browsers themselves when the technology evolves by either adding a new feature or deprecating a feature, if you are a browser implementer you may want to seek assistance from the Web Compatibility team to evaluate the risk of deprecating and unshipping a Web exposed feature.

Core Team

Name Matrix GitHub Role
Dennis Schubert denschub denschub Diagnosis / Site Interventions
James Graham jgraham jgraham Web Platform Test
Ksenia Berezina ksy36 ksy36 Diagnosis/ Webcompat.com / Machine Learning
Martin Balfanz mbalfanz martinbalfanz Product Management
Oana Arbuzov oana softvision-oana-arbuzov Triage/Testing
Raul Bucata raulbucata softvision-raul-bucata Triage/Testing
Thomas Wisniewski twisniewski wisniewskit Diagnosis / ETP Shims

Meetings

We hold Weekly meetings every Tuesday at 6am PST (if we have something to discuss).

Contact Us


Web Compatibility Taxonomy

Why sites are failing in Firefox? What can we do when this is happening?

Web Compatibility Issues

You can participate into making the Web a better place by handling these issues.

Status Bugzilla Webcompat.com
To triage 🐝 🐝
To diagnose 🐝 🐝
Find a contact 🐝 🐝
To contact 🐝 🐝



WebCompat Tracking and Triage

https://wiki.mozilla.org/Compatibility/WebCompat_Tracking_And_Triage

Web Compatibility How-To

In case, you want to contribute time or help fix issues, you can learn how to get involved. The Web Compatibility team also participates in the Outreachy program.

Web Compatibility Summit

WebCompat Summit (2015)

Retrieved from "https://wiki.mozilla.org/index.php?title=Compatibility&oldid=1256318"