303175 - "autofill as you type" should not rematch when you backspace/delete

Status: RESOLVED DUPLICATE of bug 246237

(Firefox :: Address Bar, defect)

Description

[Chris Petersen]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc4 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc4 Firefox/1.0.6

see "steps to reproduce"

Reproducible: Always

Steps to Reproduce:
with browser.urlbar.autoFill on, I paste a URL like:

http://example.com/foo/bar

Now, I wanted "foo", not "foo/bar", so I control-backspace (I have
layout.word_select.stop_at_punctuation enabled), or select "/bar" on the end
manually and press backspace.

Now, I wanted "foo", not "foo/bar", so I control-backspace (I have
layout.word_select.stop_at_punctuation enabled), or select "/bar" on the end
manually and press backspace.  This does delete "/bar" but ....

Actual Results:  
Since I previously visited http://example.com/foo/bar, the autofill decides to
add /bar back onto the end of the URL (selected, of course, so more typing would
overwrite it).  I then have to hit backspace again to delete the text.
(control-backspace doesn't work in this case, it just repositions the cursor to
the beginning of the selection, unhighlighting /bar and requiring me to hit
shift-end to reselect, and hit backspace to delete it)

Expected Results:  
/bar should be deleted and nothing else.

basically, if autofill is on, the autofill should NOT be generated if the
keystroke was a delete or backspace keystroke, or at the very least,
control-backspace should delete both the selection and the previous word.

Comment 1

[Adam Guthrie]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050802 Firefox/1.0+
ID:2005080214

This works for me and has most likely been fixed in the latest builds. You need
to test this in the most recent builds for it to be a valid bug.
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/

Comment 2

[Chris Petersen]

Just tested the latest build and it behaves exactly as I said it does.  Not sure
if it matters that I have browser.urlbar.matchOnlyTyped enabled....

Comment 3

[Adam Guthrie]

*** This bug has been marked as a duplicate of 246237 ***