Yes, fair point.
I'm not saying that my muscle memory should take precedence.
I think the points about internally consistent behavior and matching
behavior of other browsers are more compelling.
Maybe upon hitting cmd-enter, FF could detect whether the entry was in
need of .com completion, and
Yes, it's true that any change has the potential to interrupt current users.
But, if FF could detect when to append ".com" vs. when to open a new tab based
on the entered URL, then this is a very minimal change for current users.
The current behavior of ".com-completion in same tab, when
> "Also, the current "open in new tab" doesn't really make sense to me."
For me, there are several use cases in my muscle memory for Chrome:
e.g.
* slight change to existing URL
"https://bugzilla.mozilla.org/show_bug.cgi?id=237027; to
"https://bugzilla.mozilla.org/show_bug.cgi?id=12345;
*
semi-annual post to confirm that this bug persists into latest release,
and this behavior still doesn't make sense.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/66566
Title:
Inconsistent shortcuts
Gavin,
Please reconsider this issue.
Allowing both ctrl- and alt-enter opening a new tab would accommodate
all concerns and reservations expressed in this thread.
Currently ctrl-enter in the address bar has no different effect than
enter by itself, so this change would satisfy all parties.
--
What about *both* ctrl- and alt-enter opening a new tab?
(This is how Google Chrome behaves, presumably in order to accommodate FF
users.)
Currently ctrl-enter in the address bar has no different effect than
enter by itself, so this change would satisfy both parties.
--
You received this bug
Gavin is basically saying this is how it's always been done, so this is
how it will continue to be done. In the face of mounting evidence that
this is not what everyone wants, seems like providing a flag is not too
much to ask.
Do the patches not provide an amenable compromise between fixing and
Sorry if this is the wrong place to post such a message, but I'm
experiencing this issue on a production host and it's a significant
issue. I have to reboot my machine regularly, and this bug is causing
boot to take well over 30 minutes.
Is there a workaround I can use until the next stable
Sorry if this is the wrong place to post such a message, but I'm
experiencing this issue on a production host and it's a significant
issue. I have to reboot my machine regularly, and this bug is causing
boot to take well over 30 minutes.
Is there a workaround I can use until the next stable
