User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; pt-BR; rv:188.8.131.52) Gecko/20100330 Fedora/3.5.9-1.fc12 Firefox/3.5.9 Build Identifier: http://www.mozilla.com/pt-BR/plugincheck/ does not work (however, http://www.mozilla.com/en-US/plugincheck/ does work). Reproducible: Always Steps to Reproduce: 1. Just open the page. Actual Results: The page loads, but does nothing; the plugins list stays empty. Expected Results: It should behave the same as the en-US variant, only in Portuguese. The error console says: Erro: jQuery is not defined Arquivo-fonte: http://www.mozilla.com/js/plugincheck.js Linha: 14 Erro: $ is not defined Arquivo-fonte: http://www.mozilla.com/pt-BR/plugincheck/ Linha: 191
I can confirm; thanks for the bug!
What is the status of pt-BR/plugincheck?
(In reply to comment #3) > What is the status of pt-BR/plugincheck? Still doesn't work? Not sure to what status you're referring.
Where is this page in the L10n process? I looked at the code and it doesn't match en-US. Was it ever blessed as final when pushed to production?
What about resolving this problem? 2 months ago the bug was reported and the situation is the same...... ¬¬ http://img40.imagefra.me/img/img40/8/6/16/danielpereira/f_5m_3541c31.jpg
I was going to look at pt-BR/plugincheck/index.html, but pt-BR isn't in trunk right now.
I can confirm this bug and the fact that is operational system independent. I do change "pt-BR" manually to "en-US" or "fr" in order to use the mozzila-plugin-check, but I believe the majority of Firefox users don't. That's why I think this is an important issue and should be fixed in order to improve user security. Thank you for your help, devels.
and 7 months later... the bug wasn't fixed yet ¬¬ >_> I ask, please any devloper fix this bug quickly! pl0x
There's only en-US plugincheck page now. Everybody agree marking this bug as WFM/Invalid?
Given that http://www.mozilla.com/pt-BR/plugincheck/ now works (by redirecting to the en-US page, which works), I agree to closing this bug. I am not sure WFM is the correct resolution (it was fixed by converting the whole page into a redirect), but I do not care much about it.