User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 Updating of the status text seems to be broken or illogical. 1. Activating a link (clicking on a link, or selecting it by tabbing and then pressing return) does not change the status text from the URL of the link to the "Connecting..." message. (Note that clicking on a link and then _moving_ the cursor does change the status text, and that successfully loading a new page also changes the status text.) 2. When the "The operation timed out when attempting to contact xxx" message dialog pops up, the status text still says "Connecting to xxx". (Note how that is _not_ the current status: Mozilla is no longer connecting; it has already determined that trying to connect failed.) Reproducible: Always Steps to Reproduce: 1. Use a link to a server that is not currently on line (or is slow to respond). 2. Move the mouse cursor over the link. 3. Notice that the status text shows the link URL. 4. Click on the link, being careful not to move the mouse cursor off of the link. 5. Notice that the status text is still the link URL. 6. Repeat step 4, but also move the mouse cursor away from the link. 7. Notice that the status text changes to the "Connecting to ..." message. 8. Wait until the connection times out and the "The operation timed out when attempting to contact xxx" message dialog pops up. 9. Notice that the status text still says "Connecting to xxx". Actual Results: See steps 5 and 9. Expected Results: It seems that for step 5, Mozilla should display the "Connecting..." message (at least until the user moves the mouse cursor or tabs the focus to another link, at which point displaying any focused URL makes sense). It seems that for step 9, the status text should be updated as soon as the status changes (when the dialog appears) from attempting to connect to the having failed or at least being done with the attempt.
See also bug 85551.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
This bug (both parts) still exists in Mozilla 1.7.12 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915).
Confirmed. Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.8) Gecko/20051030 SeaMonkey/1.0b Component -> XP Apps: GUI Features Happens on all OSes. OS -> All
Forgot to mention that only part 1 still happens. Part 2 has been fixed. Thanks for the reminder, ajschult. :)