Can you reproduce in Chrome 69?

Thanks for the report!

I can't reproduce this, so it likely depends on your history.  Can you please submit chrome://omnibox output for "http://localhost:8000/#".  Check the following boxes:
- Prevent inline autocomplete
- show all details
- show results per provider

This will help us figure out what's going on.

Feel free to paste the results in here unformatted; we’ll be able to decipher them.

Also, when you press backspace to delete the trailing slash, does the trailing slash stay here *selected* or *unselected*?

thanks!

(note to self: sounds like bug 879796.)

Unable to reproduce the issue on latest chrome stable 69.0.3497.81 using Windows 10.Attaching screen-cast for reference.
Steps: 
---------
1. Launched reported chrome 
2. Entered given text on chrome://omnibox as per screen-cast 
3. Pressed back space on chrome://omnibox
As we are observed that backspace works fine 

@Reporter: Could you please upgrade to latest chrome stable 69.0.3497.81, you can download latest chrome builds here:" https://www.chromium.org/getting-involved/dev-channel ". Let us know whether issue still persists.

Thanks.!

Deleted: 880805.mp4 3.3 MB

	880805.mp4 3.3 MB View Download

I can reproduce on 70.0.3538.77 on macOS. When autocomplete occurs backspace no longer works!!

Deleted: backspace_bug.mov 6.4 MB

	backspace_bug.mov 6.4 MB View Download

It's clear from the screenshot that the omnibox is trying to get provide an inline autocompleted to the root page of the hostname plus a #hash fragment.  This is bug 879796.  It was only fixed for Chrome 71, so it's likely you'll be living with it for a while.  One way to fix it would be to delete the visits in your history that autocomplete with a #hash like that, e.g., 192.168.1.1/#.  It's the #hash that is causing the trouble.