Difference in zoom behavior between 4.0b4 & 4.0b5
Site-specific zoom is acting flaky in 4.05b... After typing in a URL with a preset page zoom level, the page loads and stays at 100% zoom *until* I switch to another tab, then back to the original, at which point the preset zoom suddenly kicks in. This wasn't the case in 4.0b4, and in fact, reverting back to 4.0b4 resolves the issue.
I've also noticed that the address bar (both URL and favicon) in 4.0b5 isn't always updated when moving from one page to another, within a tab; for instance, I do a search on www.google.com, then click on one of the search links, taking me to another page - the address bar still contains the www.google.com URL - until I click on the favicon, at which point the address bar refreshes, reflecting the correct URL. Again, no such behavior in 4.0b4.
I'm running Windows XP, incidentally.
Всички отговори (5)
Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of your add-ons is causing your problem (switch to the DEFAULT theme: Tools > Add-ons > Themes).
See Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems and Troubleshoot issues with plugins like Flash or Java to fix common Firefox problems
First thing I tried, actually. The problem persists.
Did you create a new profile for the Firefox 4.0 beta version?
Create a new profile as a test to check if your current profile is causing the problems
See Basic Troubleshooting: Make a new profile
There may be extensions and plugins installed by default in a new profile, so check that in "Tools > Add-ons > Extensions & Plugins"
If that new profile works then you can transfer some files from the old profile to that new profile (be careful not to copy corrupted files)
See http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox
I'm fairly certain it's not an interaction with an extension, but rather an issue with the 4.0b5 build itself, perhaps related to the recent changes in display rendering.
I'm mostly interested to know if someone else with XP encountered the same problem when upgrading from beta 4 to beta 5.
Anybody else have this problem?