User-Agent: Mozilla/5.0 (Windows; Windows NT 6.1) AppleWebKit/534.23 (KHTML, like Gecko) Chrome/11.0.686.3 Safari/534.23 Build Identifier: Firefox 4.0 RC1 I have this website: www.faravirusi.com on WordPress platform. I use Hybrid News theme: http://themehybrid.com/ When I go to my Widgets, I can't open all of them in Firefox 4.0 RC1. They didn't work in none of the Firefox 4.0 build before this one. Internet Explorer 8 displays them properly. I can create a temporary admin account for a developer to investigate this. Reproducible: Always Steps to Reproduce: 1. Access wordpress Dashboard 2. I go to Widgets 3. I click some widgets and they don't open to be able to edit their elements Actual Results: Widgets don't open Expected Results: Widgets to be able to be opened and edited.

Could you see if the issue occurs if using Firefox in safe mode: http://support.mozilla.com/kb/Safe+Mode How about with a new, empty profile? http://support.mozilla.com/kb/Basic+Troubleshooting#w_make-a-new-profile Also, please could you paste any errors that show in the error console (Ctrl + shift + J). I'd recommend just pasting errors (in red) rather than warnings (in yellow) as well, otherwise there will inevitably be a lot more to shift through.

Thank you for your comment Ed. I've started Firefox in Safe mode, but this bug is still occuring. Creating a new profile doesn't help either. This are the errore I have in error console: Error: no element found Source File: https://testpilot.mozillalabs.com/testcases/index.json Line: 1 Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIURI.host]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://testpilot/modules/feedback.js :: FeedbackManager_isInputUrl :: line 109" data: no] I don't think they are related to my issue...

Thanks for the update. The error listed there is not related, was worth a try! Can you check if the widgets work in Firefox 3.6.x and also Chrome 11 dev.latest; to help work out if this is a problem with Firefox in particular, or with a particular Wordpress plugin/widget.

Ed, it works flawless in Firefox 3.6.15, but not working in Chrome 11. So, the bug appeared after Firefox 3.6.15 and it's related only to Firefox 4.0.

It's possibly related to the ES5 javascript changes or else the introduction of the new html5 parser in Firefox 4. eg: the widget is broken and only worked by chance before; Firefox 4 could be performing correctly/according to the new the spec. Chrome 11 uses a new parser/supports ES5 strict mode as well (iirc), so would explain why that isn't working either. If you can spare say 20 mins, would you be able to find the regression range please (if probably the easiest way of tracking down the cause at this point): http://harthur.github.com/mozregression/ Thanks :-)

Thank you Ed! I've found the working build. It's from May 2010... Here's the result in the screenshot below: http://i53.tinypic.com/accw94.png

Typing that out from the screenshot... Last good: 2010-05-03 First bad: 2010-05-04 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=83c887dff0da&tochange=d6bb0f9e9519 Which contains this changeset: Bug 373864 - Enable the HTML5 parser by default. r+sr=jst. http://hg.mozilla.org/mozilla-central/rev/358113b3642e So yeah, this is due to the new html5 parser, so likely invalid, given that it doesn't work in Chrome either, so is more likely to be a bug in the widget/Wordpress than Firefox's new parser. I've just tested using Chrome 11.dev and client's Wordpress install (running Wordpress v3.0.5) and the widgets work fine. What version of Wordpress are you using? Are all widgets broken, or just some? If you disable all Wordpress plugins, does the problem go away?

I'm using Wordpress 3.1. The issue occured in 3.0.5 also. Not all the widgets are broken, only half of them.

(In reply to comment #7) > If you disable all Wordpress plugins, does the problem go away?

Do the widgets work in IE8?

@Henri Sivonen: Yes, they work perfectly in IE8. @Ed: I'll try this in about one hour.

@Ed: That's a little bit odd. The issue appears only when I add the Feedburner widget on my secondary widget bar. If I remove it, everything works fine and I can open and edit all my widgets.

I've looked on WP plugins but there are several Feedburner plugins available: http://wordpress.org/extend/plugins/search.php?q=feedburner Please can you paste the full name, version and plugin URL, from the plugins page in wp-admin, thanks!

Is this not just http://richard.milewski.org/archives/995 ?

@Ed: This is my plugin: http://wordpress.org/extend/plugins/feedburner-widget/ FeedBurner Widget 1.2 Now I see it hasn't been updated for a while.

@Mike: That's bug 638487, which is due to the Wordpress theme being used at the time; whereas this is only affecting the admin control panel for widgets, which isn't styled by the site theme. Also, since removing the widget/plugin fixes the widget admin page; it's specific to this Feedburner plugin. @faravirusicom: Thanks for the info. The plugin you are using is not listed as being compatible with Wordpress 3.1; in fact the highest supported is 2.7.1. It also hasn't been updated since 2009, as you spotted above. There are several other feedburner plugins available, suggest you use a newer, more compatible one: http://wordpress.org/extend/plugins/search.php?q=feedburner Moving to TE/clarifying title. However will likely get marked as invalid; since the plugin doesn't say it's compatible with WP 3 and hasn't been updated for 2 years, so isn't likely to receive an update now.

@Ed: Thanks. Now I saw that feedburner.com itself has a code to display the stats on your sidebar widgets. I am now using that and everything works fine :) Thanks for all your help!

Posted a warning/explanation on WP forums/support: http://wordpress.org/support/topic/feedburner-widget-12-breaks-wp-admin-widget-page?replies=1 @faravirusicom: Thanks for your fast responses/help finding the regression range. Glad you've found an alternative Feedburner method :-)

In fact, WONTFIX is probably more appropriate, given that a message has been posted by no update is expected on their part, seeing as it's an old plugin. Not too familiar with TE section convention...

WONTFIX is entirely appropriate here.