Loss of editing controls in Firefox

[rdenney]

Quite suddenly today, I have lost access to editing controls in the LFP vBulletin interface. This happened only in Firefox (I'm using v3.5 on this older XP laptop)--everything still works fine in Internet Explorer.

None of the mouse-over commands are present. For example, the little down arrow next to Search is gone, as is the functionality it provides. The MS Office-style formatting controls in the editing window are all there, but clicking on them does nothing. The control-key combinations that invoke those formatting commands (e.g. cntrl-I for italic) has reverted back to the Firefox effect.

Finally, the LFPF logo in the upper left has been replaced by a plain-text link "Large Format Photography Forum", and not the graphical logo.

This happened this afternoon quite suddenly, during a period of very spotty Internet access using a 3G modem in a fringe area.

I have reinstalled Firefox, thinking it got corrupted somehow, but that had no effect. Of course, I rebooted thinking I'd corrupted run code in memory somehow. Again, no effect.

I went to the vBulletin forum to see if there was any discussion of these symptoms, but all the controls in that forum (which presumably shares its code with this one) still work as expected.

Anybody got any ideas?

Rick "another mystery fault" Denney

[BradS]

that is certainly odd.

The only thing I can think of is that some web sites detect a "limited bandwidth" client and decide to dumb down their response. I'm not sure that this is what you are experiencing but, it sounds familiar. I still connect to the internet with a dial-up connection over a 56k modem from time to time and I see this a lot.
You might try to clear you cookies and all of the cache (tools->clear recent history, and check all of the check boxes). Then close firefox and try again...


Why have you not upgraded to the latest version of firefox?

[Leigh]

Sounds like your security settings got changed.

Are you running NoScript? It will do that if you tell it to block a site (or don't tell it the site's OK).

I'm running 3.6.19 on an iBook Pro with nary a problem. I don't have any windoze machines connected to the internet anymore.


- Leigh

[RickV]

I'm running 3.6.18 on all my PCs and laptop without drama. I was only offered the upgrade yesterday so perhaps seek it out. Do not run V.4...many add-ons are incompatible with this version but fine with the V.3s

The upgrade install may resolve obvious glitches.

Rick

[IanG]

With a poor connection the pages don't always fully load, effectively they timeout with most of the content and no graphics.

Firefox is now on V6 which is very much more stable and faster (still Beta thoiugh), I had no issues weith V4 and all my plugins.

Ian

[Leigh]

... I had no issues weith V4 and all my plugins.

FireFTP doesn't work with v4. I use it a lot, maintaining three websites.

- Leigh

[IanG]

Leigh. I use FireFTP all the time it works in V6 and I used to use it with V4 as well but there was a short spell before it was compatible.

One great thing about FireFTP is you can run it in multiple tab or windows, quite usefull for faster uploading.

Ian

[RickV]

Ian, the issues are with the add-ons not plug-ins. Probably just a case of third party offerings being tardy which I do not tolerate. Given time, they will catch up with the changes no doubt.

[IanG]

Ian, the issues are with the add-ons not plug-ins. Probably just a case of third party offerings being tardy which I do not tolerate. Given time, they will catch up with the changes no doubt.

Actually the issues are Firefox develops memory problems and this leads to problems like this, it slows down and then when you get a bad connection it stumbles, it tends to pull some files from cache. I found the later versions of V3 the worst for this.

It's worth trying to restart with the add ons disabled, which should be on the help menu, but I think I had to edit the Config file for V3.6 to overcome a couple of problems.

Ian

[Leigh]

Actually the issues are Firefox develops memory problems and this leads to problems like this, it slows down ...

This is a classic windoze memory leak problem that has nothing to do with Firefox.

When you allocate memory under windoze, it generates a 16-byte mezzanine header that has the owning process and the size of the block and ???.

When you release the memory, that mezzanine header is not released, but remains in memory. This creates two problems:
1) These accumulate over time, in large numbers for programs that rely heavily on dynamic memory allocation;
2) The headers present in RAM prevent efficient memory consolidation and allocation.

This is a well-known problem that μ$oft chooses to ignore.

- Leigh