FF 4.0.1 no longer shows buttons in email at webmail.infoquest.com
Messages at webmail.infoquest.com accounts used to have buttons displayed for delete, next, previous, reply, reply all etc. displayed across the top and bottom of the message. Now only an image placeholder appears. Functionality remains intact, but without the image it is hard to determine which button does what. NOTE: this used to work fine in previous FF versions and all other browsers (IE, Chrome etc.)
所有回覆 (3)
If images are missing then check that you aren't blocking images from some domains.
See:
- Check the permissions for the domain in the current tab in Tools > Page Info > Permissions
- Check that images are enabled: Tools > Options > Content: [X] Load images automatically
- Check the exceptions in Tools > Options > Content: Load Images > Exceptions
- Check the "Tools > Page Info > Media" tab for blocked images (scroll through all the images)
There are also extensions (Tools > Add-ons > Extensions) that can block images.
None of the suggested troubleshooting steps provide relief. I've also found that a text link "Printer Friendly Version" does not function (produces a 404 error).
In looking at the frame source where these problems manifest, the missing images, and the "printer friendly version" all point to very long link name that has the string, "cache" in it. E.g.: "https://webmail.infoquest.com/cache/2AB5090665FD17CD1358614FA077D3DF/427670749/">
Note that these links still function correctly in Chrome, IE and versions of Firefox earlier than 4.0. Other images and links that DO NOT have locations formed that that shown above (or have the word "cache" in the link) display / function properly in 4.o.1. I should also add that these long links with "cache" in them are referenced from a javascript function.
Also not that since this problem appears on two different machines running two different versions of Windows (XP and 7) it quite clearly indicates a coding error in Firefox, and one that changed between 3.6.17 and 4.0.1.
Problem also exists in versions 5.x and 6.x, so it appears this is a problem that will remain in all future builds. It adds to other incompatibilities with .asp and javascript that force me to use IE for an increasing number of sites, most notably those running on Windows servers that appear to have been developed using .NET tools, and which rely heavily on scripting. I guess it is time to start searching for an IE alternative again, because Firefox's decreasing reliability and site compatibility are making it less and less useful.