Closed
Bug 1067981
Opened 10 years ago
Closed 10 years ago
"Did you mean to go to 127.0.0.1" question cannot be disabled.
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 1067168
People
(Reporter: stomlinson, Unassigned)
Details
Attachments
(1 file)
The new feature that asks "Did you mean to go to 127.0.0.1" is *really* annoying for web devs since most local web development occurs on this IP. I cannot disable the question, and every attempt to set browser.fixup.domainwhitelist.127.0.0.1 to false is automatically reverted the next time I visit 127.0.0.1.
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Comment 2•10 years ago
|
||
(In reply to Shane Tomlinson [:stomlinson] from comment #0) > The new feature that asks "Did you mean to go to 127.0.0.1" is *really* > annoying for web devs since most local web development occurs on this IP. I > cannot disable the question, and every attempt to set > browser.fixup.domainwhitelist.127.0.0.1 to false is automatically reverted > the next time I visit 127.0.0.1. I don't understand. You're meant to set it to *true*. What do you mean by "automatically reverted" ? There's currently a bug where "1.2.3.4/" triggers a search when it shouldn't, which is what this got duped to. The current workaround would be using "localhost" instead of "1.2.3.4" for the time being (or whitelisting things correctly - which in fact, clicking the relevant button (Yes, take me to "127.0.0.1") on the info bar should be doing for you - does it not?)
Flags: needinfo?(stomlinson)
Reporter | ||
Comment 3•10 years ago
|
||
> The current workaround would be using "localhost" instead of "1.2.3.4" for the time being (or
> whitelisting things correctly - which in fact, clicking the relevant button (Yes, take me to
> "127.0.0.1") on the info bar should be doing for you - does it not?)
:Gijs - If I click "Yes", it takes me to the dev site. The next time I try to visit the exact same site (127.0.0.1:8080), it asks again. No matter what I answer, I am always asked again.
I misunderstood the purpose of the preference. I see the preference is always set to the answer that I click in the info bar, so even though I manually set the preference to "false" in "about:config", I reset it to "true" whenever I click on "yes" in the info bar.
Where does the whitelist live? If there is a whitelist, I'll add the site to it.
Can this feature be disabled with a preference? It makes web dev more difficult than it needs to be.
Flags: needinfo?(stomlinson)
Reporter | ||
Comment 4•10 years ago
|
||
Comment 5•10 years ago
|
||
(In reply to Shane Tomlinson [:stomlinson] from comment #3) > > The current workaround would be using "localhost" instead of "1.2.3.4" for the time being (or > > whitelisting things correctly - which in fact, clicking the relevant button (Yes, take me to > > "127.0.0.1") on the info bar should be doing for you - does it not?) > > :Gijs - If I click "Yes", it takes me to the dev site. The next time I try > to visit the exact same site (127.0.0.1:8080), it asks again. No matter what > I answer, I am always asked again. I'm sorry, but this is really not a clear bugreport so far. The problem here is likely a mismatch between the host we're reading and what you're putting in the URL bar. So, please answer these questions: What *exactly* do you type in the urlbar, do you use the autocomplete popup, do you include the protocol or not, and do you always use a port or not? What does the button say, exactly? (Yes, take me to... what?) Can you reproduce if using "localhost:8080" ? > I misunderstood the purpose of the preference. I see the preference is > always set to the answer that I click in the info bar, so even though I > manually set the preference to "false" in "about:config", I reset it to > "true" whenever I click on "yes" in the info bar. > > Where does the whitelist live? If there is a whitelist, I'll add the site to > it. The preferences *are* the whitelist. For every host that's set to 'true', we shouldn't be using a search provider. "localhost" is in the whitelist by default. IP addresses shouldn't be triggering this code in the first place, which will hopefully be fixed as part of bug 1067168, which should be in today's nightly. Please check if you can reproduce there. > Can this feature be disabled with a preference? It makes web dev more > difficult than it needs to be. Then we should fix the feature - random prefs aren't the right solution here.
Flags: needinfo?(stomlinson)
Comment 6•10 years ago
|
||
Egh, I missed the gif. I'd still want to know if this reproduces for you with "localhost:8080" or not.
Reporter | ||
Comment 7•10 years ago
|
||
:Gijs
> I'm sorry, but this is really not a clear bugreport so far.
Sorry about that, I thought the gif would be clearer than anything I would write.
This looks like it is fixed now. When I was wrote the bug report, I was not adding the `http://` prefix. When I *did* add the `http://` prefix, no problems.
In today's Nightly, I am unable to reproduce with any combination. Thanks for the quick turnaround!
Flags: needinfo?(stomlinson)
Comment 8•10 years ago
|
||
(In reply to Shane Tomlinson [:stomlinson] from comment #7) > :Gijs > > > I'm sorry, but this is really not a clear bugreport so far. > > Sorry about that, I thought the gif would be clearer than anything I would > write. Yeah - sorry on my part for missing that. I'm in Italy with intermittent wifi, and I'd read all the bugmail but missed the gif. > This looks like it is fixed now. When I was wrote the bug report, I was not > adding the `http://` prefix. When I *did* add the `http://` prefix, no > problems. > > In today's Nightly, I am unable to reproduce with any combination. Thanks > for the quick turnaround! Great!
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•