857908 - Issues with Magento since update to 20.0

Status: RESOLVED INVALID

(Firefox :: Untriaged, defect)

Description

[Campbell]

Attachment: manage-categories.jpg

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.43 Safari/537.31

Steps to reproduce:

I upgraded firefox to 20.0 & logged into the backend of Magento & went to manage categories. I also went to the front-end of the site none of the jquery tabs are loading correctly.


Actual results:

See the screenshot attached.


Expected results:

It should have loaded the category information like it does in other browsers.

Comment 1

[Loic]

We need a way to test Magento (access, testcase). Is there an online demo?

Comment 2

[Xavier Hourcade]

I can see this, exactly as displayed in the screen capture attached to this bug, using Firefox 23/Fedora, Firefox 22 & 23/Win. Not sure about intermediary releases.

Konqueror/KHTML gets that page only partly functional, but does not show the issue.
Konqueror/Webkit is fine. Besides, I was told Chrome is fine too (didn't test this one myself).

The affected Magento here, is the Community Edition (CE) version 1.5.1.0.
Which is obsolete/EOL, for long.

(In reply to Loic from comment #1)
> We need a way to test Magento (access, testcase). Is there an online demo?

Yes, there is a public instance which is *not* presenting the issue at the moment.
It is running Magento CE version 1.7.0.2

  http://demo-admin.magentocommerce.com/index.php/admin/

If anyone is interested in digging this, I can provide more information until that Magento instance gets updated, as it should have for long! Until then, workaround here will be using any other browser for managing categories under Magento.

Comment 3

[Loic]

Honestly, if the issue is with an EOLed version of Magento, don't expect to see a bugfix. The best workaround is to update Magento to the latest supported version which doesn't have this issue.

It's frequent to see broken features in JS lib or frameworks after Mozilla landed new features in Firefox.

Anyway, if you have some time to spend, you can use the tool http://harthur.github.io/mozregression/ to find a possible regression range.
FF20 nightlies started in Nov 2012 (mozregression --good=2012-11-01).

Comment 4

[Xavier Hourcade]

Thank you for your response Loic.

More info FWIW

A default Magento CE instance was *not* tested here (but only the on-line demo provided by Magento Inc.). Also, I suspect the affected instance was quite "fiddled", but not this part of the back-end.

The Category page seems to be briefly rendered properly, then within half a second it leaves place to the error shown in the capture.

Still it could be a true regression, I'll try to retrieve the instance's source and look at mozregression too, thanks for the pointer.

Honestly -- yes I agree, plus that's "unrivaled security" :p Short story, it's a small business owned by a relative and I have no say (tried, so long). The "web designer" always fought any upgrade as "one-week effort" and is now advising to "just use Chrome".

Unfortunately it's a common scenario, Magento instances were massively embraced without any skills (or not enough, even just to maintain it). I hope this won't affect many Firefox users at small businesses, how would just drop it "pragmatically", as they'd say.

Campbell,

Could you please confirm the affected Magento version(s) ?
With or without customization?
If you upgraded it yet, did it fix your issue?