Confirmed users
44
edits
Compatibility/Contribute: Difference between revisions
Jump to navigation
Jump to search
m
→Testing and Technical analysis
| Line 40: | Line 40: | ||
**'''Skills required:''' A keen eye for spotting visual differences | **'''Skills required:''' A keen eye for spotting visual differences | ||
**'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists. | **'''Description:''' Compatibility issues occur when a website is broken for one browser, or is providing a lesser experience than what another browser receives. You can help identify these issues through a few ways. The easiest way is using the screenshot tool to compare screenshots from different browsers, if the sites don’t match reasonably well, that’s a bug! You can also use other automated testing tools if you want to get fancy, or do it the old fashion way and manually test sites from the regional site lists. | ||
**'''Get started:''' //maybe hallvors can help to write this | **'''Get started:''' //maybe hallvors can help to write this *screenshot vid* | ||
*'''Analyzing Web Compat Issues''' | *'''Analyzing Web Compat Issues''' | ||
| Line 46: | Line 46: | ||
**'''Skills required:''' Knowledge of web coding, CURL, user agent detection | **'''Skills required:''' Knowledge of web coding, CURL, user agent detection | ||
**'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit). | **'''Description:''' Compatibility bugs that have been reported need to be analyzed to identify the cause of the issue. The way to analyze varies by the type of issue. The most common issues found on mobile sites are related to User Agent detection, Javascript libraries and vendor specific CSS/JS (webkit). | ||
**'''Get started:''' [[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section | **'''Get started:''' | ||
***[[Compatibility/Guide#Analyzing_for_Web_Compatibility_Issues|Read this]] wiki section | |||
*** Create a Bugzilla account | |||
*** Use [http://webcompat.com/bugsahoy/?analysis=1 Bugs Ahoy!] to find some mobile bugs to work on. There are lots of [http://planet.webcompat.com/ blogs] with information of common issues and tools to use. [http://www.otsukare.info/2013/08/08/http-cli-and-ua-sniffing This post] is a good start for detecting User Agent issues on the command line. | |||
*** There are also older desktop compatibility which need to be analyzed. These bugs are an easy introduction to analyzing compatibility bugs. There's also a [https://air.mozilla.org/webcompat-walkthrough-old-tech-evangelism-bugs/ walk-through video] to get you started. | |||
== Writing code and UX == | == Writing code and UX == | ||