Closed Bug 200381 Opened 23 years ago Closed 21 years ago

Location bar click has delay before selecting text

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

x86
Windows 2000
defect
Not set
minor

Tracking

()

RESOLVED EXPIRED

People

(Reporter: davidh, Assigned: saari)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016 When the computer is running slowly, clicking in the location bar and typing turns odd. If I click in the location bar and immediately begin typing, the first several characters appear in the location bar at the place I clicked, then the entire location bar is highlighted and the next character I type replaces what I've typed so far. Reproducible: Sometimes Steps to Reproduce: 1. Get the machine running slowly. Examples may be running a lot of programs so the computer runs low on memory and has to swap, or performing a disk-intensive operation in another program. 2. Click location bar and immediately begin typing, not waiting for the location to highlight. Actual Results: If I'm viewing "http://www.mozilla.org/" and I click in the location bar around the "z" and start typing "http://www.cnn.com/", I might get up to "http://www.mozhttilla.org/" for a moment, then the entire URL is highlighted and I end up with "p://www.cnn.com/" when I'm finished typing. (The number of characters I can type before it highlights varies.) If machine is very, very slow, I can type the entire URL and press enter before the location bar has a chance to highlight the URL. In this case, I may end up requesting "http://www.mozhttp://www.cnn.com/illa.org/". Expected Results: The click in the location bar should have caused the URL to be selected first, before processing any keystroke events which would replace the selection. Using the "Modern" theme. Don't know if the same happens in other themes.
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.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → EXPIRED
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.