1,623
edits
Evangelism/WebsiteCompatibilityInternational: Difference between revisions
Evangelism/WebsiteCompatibilityInternational (view source)
Revision as of 19:37, 10 March 2009
, 10 March 2009→Feedback
| Line 139: | Line 139: | ||
* As for type of the problem, in Japan (and I believe in China, Korea etc too) [http://en.wikipedia.org/wiki/Mojibake mojibake] (garbage text) is the most famous broken case (caused by lack or miss of charset in the content type header). I thinks it's nice to add mojibake in the type list in the reporter (at least for multibyte locales). (dynamis) | * As for type of the problem, in Japan (and I believe in China, Korea etc too) [http://en.wikipedia.org/wiki/Mojibake mojibake] (garbage text) is the most famous broken case (caused by lack or miss of charset in the content type header). I thinks it's nice to add mojibake in the type list in the reporter (at least for multibyte locales). (dynamis) | ||
* Some problems are caused by addons and reporter should also include installed addons list (not only build config). (dynamis) | * Some problems are caused by addons and reporter should also include installed addons list (not only build config). (dynamis) | ||
** I was going to add this to the list too; on SUMO we get a lot of suppor issues of sites not working as a direct result of an add-on (e.g. AdBlock). I'm concerned that a lot of the people that use the Site Reporter tool in Firefox confuse it with a way to get support. (djst) | |||
** Do we really want end-users to report broken websites? Ideally, everyone that reports a broken website should always try with another browser ''and'' trying with Firefox running in Safe Mode (sans add-ons) to ensure that the problem is indeed caused by incompatibilities and not other support issues. (djst) | |||
* I think volunteer may use Greasemonkey to test, verify and develop code to fix a listed broken page. This code needs to be uploaded to our server database. A mechanism shall be established at back-end to review and verify his code. Meanwhile, we develop an add-on, shipping with Firefox, whenever user open an incompatible page, this add-on will grab the code from server, and fix it. A question is that what a kind of mechanism could ensure this program sustainable? for example, one fixed some pages in CNN.com, a few days later, CNN changed their pages ... (jguo) | * I think volunteer may use Greasemonkey to test, verify and develop code to fix a listed broken page. This code needs to be uploaded to our server database. A mechanism shall be established at back-end to review and verify his code. Meanwhile, we develop an add-on, shipping with Firefox, whenever user open an incompatible page, this add-on will grab the code from server, and fix it. A question is that what a kind of mechanism could ensure this program sustainable? for example, one fixed some pages in CNN.com, a few days later, CNN changed their pages ... (jguo) | ||
** Jack, please see the TouchUpWeb project that was co-produced by Mozilla Japan (link below) as this is what was done in Japan. (gen) | ** Jack, please see the TouchUpWeb project that was co-produced by Mozilla Japan (link below) as this is what was done in Japan. (gen) | ||
| Line 149: | Line 151: | ||
*** [http://www.ipa.go.jp/software/open/ossc/download/Web_Recommendations_En.pdf Recommendations] | *** [http://www.ipa.go.jp/software/open/ossc/download/Web_Recommendations_En.pdf Recommendations] | ||
** Gen's post on compatibility: http://blog.mozilla.com/gen/2007/11/08/browser-and-web-content-compatibility-in-asia/ | ** Gen's post on compatibility: http://blog.mozilla.com/gen/2007/11/08/browser-and-web-content-compatibility-in-asia/ | ||
* The goal says to "improve Firefox website compatibility and the use of open standards outside of the US and Europe" -- does that exclude Europe? There are still website compatibility problems in Sweden. (djst) | |||
* In the dashboard in Stage 2, per-country is mentioned. Does that mean "issue reported from a user in country X" or "issue reported on a website hosted in country X"? The latter seems more relevant if we want to form local teams of evangelism experts that can reach out to website owners. (djst) | |||