Impossible to backspace over URL fragment from omnibox
Reported by
jleedev@gmail.com,
Nov 1
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: 1. Find a URL completion that includes a # hash component 2. Place the cursor at the end 3. Try to backspace over the fragment What is the expected behavior? Editing works normally What went wrong? As soon as the # is reached, the text is reinserted automatically. Same thing if Option+Delete is used to erase the whole word. Screencast attached. Did this work before? N/A Chrome version: 70.0.3538.77 Channel: stable OS Version: OS X 10.14.1 Flash Version:
,
Nov 2
,
Nov 2
Unable to reproduce the issue on reported chrome version #70.0.3538.77 and latest chrome #72.0.3598.0 using Mac OS 10.14 by following below steps. Steps: ===== 1.Launched chrome. 2.Navigated to "https://portal.aws.amazon.com/billing/signup#/start". 3.Placed the cursor at the end. 4.Tried backspacing until it reached "#', observed that editing works normally and the text gets deleted. Attached screencast for reference. @reporter: Could you please retry the issue by creating a new person without any apps and extensions in it, reset all flags to default and let us know if still exists. Thanks.!
,
Nov 2
This definitely depends on the exact state of the omnibox completions and will not work on a fresh profile. I got it to repro on mail.google.com, I think. I can try omnibox-intervals if that would help.
,
Nov 2
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 2
In fact, it is even more path-dependent than I realized. - If I *paste* `https://console.aws.amazon.com/dynamodb/home?region=us-east-1#tables:`, I can then backspace (or option+backspace) over it just fine. - If I *type* `con` then press the right arrow key, then it gets stuck.
,
Nov 2
[Mac triage] Thanks for the report. This looks like a known issue which is going to be fixed in an upcoming update. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by meh...@chromium.org
, Nov 1