Compatibility/Guide: Difference between revisions

Jump to navigation Jump to search
→‎Reporting a Web compatibility issue: Change reporting instructions to be for webcompat.com
(→‎Mobile Web Compatibility Issues By Countries: Put this section down at the bottom.)
(→‎Reporting a Web compatibility issue: Change reporting instructions to be for webcompat.com)
Line 18: Line 18:
=== What? ===
=== What? ===


# Enter the Web site URI
# You visit a webpage.
# You have not been able to use it with your Web browsers of choice
# Something about the experience is broken: layout is messed up, video doesn't play, buttons don't work, etc.
# '''Check on other browsers'''. Are there any differences making the site unusable.
# '''Check in another browser'''. Is it working there but not in Firefox?


'''You can help'''!
'''You can help'''!


This guide is focused on Mozilla browsers but you can also help other browser vendors. If you have an issue with Opera ([https://bugs.opera.com/wizarddesktop/ Bug Wizard]), Chrome ([http://code.google.com/p/chromium/issues/entry Bug]), Safari ([https://bugs.webkit.org/ Bug]) or Internet Explorer ([https://connect.microsoft.com/IE Bug]).
Note: We try to avoid working on fixing Web sites which are working badly everywhere. We focus first our energy on Web sites which are broken in one browser and not others.
 
PS: We try to avoid to fix Web sites which are working badly everywhere. We focus first our energy on Web sites which are broken in one browser and not the others.


=== Requirements ===
=== Requirements ===


You will need a Mozilla bugzilla account. If not [https://bugzilla.mozilla.org/createaccount.cgi create a new account].
You will need a GitHub account. If you don't have one, [https://github.com/ you can create a new account] (it's free). You can also file bugs anonymously, but that makes it hard to follow up— filing with an account is preferred!
 
Alternately, you can open a bug on [https://webcompat.com/?open=1 webcompat.com ]


=== Steps to follow ===
=== Steps to follow ===


The person (volunteer or Mozilla engineer) will need to know which steps you have followed to reach the issue. The more details you give, the better chance the issue will be properly addressed. If, for example, one must log in to see the issue, it is important to say so.
A good bug report includes steps to reproduce an issue, and what the expected outcome was. The more details you give, the better chance the issue will be properly addressed. If, for example, one must log in to see the issue, it is important to say so. Screenshots can also be very helpful!


# Create a [https://bugzilla.mozilla.org/form.mobile.compat new bug in Bugzilla]
# Create a [https://webcompat.com/?open=1 new bug on webcompat.com]
## Describe the steps you have been doing for reaching the point where you have an issue: '''[https://bugzilla.mozilla.org/show_bug.cgi?id=901569#c0 Example of steps]'''
## Include the URL'''
## Describe what is happening
## Include the steps to perform to see the problem after opening that URL
## Describe what you were expecting
## Describe the expected behavior
## Give information about your device and your browser
## Describe the actual behavior
# (Bonus) Test in one or more browsers to understand the differences: [https://bugzilla.mozilla.org/show_bug.cgi?id=843165#c1 Example of tests in different browsers]
## Give relevant information about your device and your browser
# (Bonus) Test in one or more browsers to understand the differences


Someone might ask further questions in the bug report to better understand the issue.  
Someone might ask further questions in the bug report to better understand the issue. This is why it's important to report issues with a GitHub account — you'll be able to get notifications about questions and progress.


Do not forget: '''Be nice'''. It is our collective effort.
Do not forget: '''Be nice'''. It is our collective effort.
Confirmed users
796

edits

Navigation menu