Open URL / Search in New Tab from Address Bar with "Enter"

BoneTone

Here's a very simple workaround. If your intention is to always open a typed address/search in a new tab:

Create the new tab then type the address. This takes no extra time, not any extra key presses. Instead of hitting the keyboard shortcut for address field, hit the one for new tab, then enter your address. This is the exact same number of keystrokes, you could make it fewer if you want to change the keyboard shortcuts and use single key shortcuts to create the new tab -- I recommend T.
Configure searches to always open in a new tab (I use this option as I too prefer having my searches create a new tab).

7twenty

@BoneTone said in Option to Open a URL / Search Results in a New Tab from the Address Bar with "Enter":

The only way it doesn't become essentially automatic is if one doesn't make use of it frequently,

I do use it, when required.

The problem is the standard response has always been to use quick commands as it has an option to open in a new tab. Which is what i started to do. So now you've got a mixup between QC which you press enter, and the address bar which requires the modifier.

But then you have the issue that QC doesn't do everything the address bar can (eg. typed addresses), which is where the hassles are. If QC could work like a popout address bar i'd use that all the time, but that's not an option either.

So here's a question, why does QC have the open in a new tab option with no modifier? What makes that feature special? Shouldn't both QC and address bar use the same confirmation key option?

cannibalox

@BoneTone said in Option to Open a URL / Search Results in a New Tab from the Address Bar with "Enter":

Please do so. How is that related?

I'll take it as a genuine question and just link you to this

Once again, if don't understand the issue or do not have a need for the feature, please do not respond by saying it's not a big deal or you will adapt.

I'm happy that everything is working fine for you, please do not extrapolate your own experience to everyone else and refrain for replying in features you have no interest in.

Thanks and have a good day. (you don't need to reply, just go on with your life).

BoneTone

@cannibalox that link says nothing about the issue. I'm well aware of disabilities, I understand the issue far deeper than that link goes into. I've spent years working specifically on technologies for people with disabilities. If you can't explain how using Ctrl-Enter is is a problem, that's okay, it's a tough ask if using the keyboard is something the person is able to do.

BoneTone

@7twenty I said nothing about QC, that's what is known as a strawman.

cannibalox

@BoneTone interesting, so you don't see how pressing just 'enter' can be easier than pressing 'shift enter' or 'alt enter' for people with dexterity issues ? change your line of job, there must be a lot of other things that go over your head.

I get that you are not interested in this feature request, now please explain why you absolutely want to stop others from getting this ? what issue will you have if it ever gets implemented ?
you will still be able to use your 2-key shortcut if you please, so what is your problem ?

7twenty

@BoneTone said in Option to Open a URL / Search Results in a New Tab from the Address Bar with "Enter":

I said nothing about QC, that's what is known as a strawman.

You can call it whatever you want. The very first response given in this thread is to use QC, and two times after that. And for that reason I, and probably many others, started doing the same.

Getting used to using a modifier key for all of these interactions is an option, but it's not what the request is about.

I'll ask the question again, why does QC have an open in new tab option, and for that matter, also the search box?

BoneTone

@cannibalox said in Option to Open a URL / Search Results in a New Tab from the Address Bar with "Enter":

@BoneTone interesting, so you don't see how pressing just 'enter' can be easier than pressing 'shift enter' or 'alt enter' for people with dexterity issues ?

Having observed dozens of usability studies with hundreds of subjects, I can safely say I've never seen any disability with which the person was capable using the keyboard, but had a problem pressing shift-enter. It's likely the easiest key combo that could exist, two of the largest keys directly adjacent to one another. One can press shift-enter using a single digit.

I've seen people with rheumatoid arthritis, Parkinson's, and unilateral amputees make proficient use of far more difficult key combos. The industry standards for increasing keyboard accessibility are using Alt for access keys and Ctrl for action keys -- people making use of the keyboard for accessibility reasons are using for more difficult key combos than shift-enter all the time. I haven't seen everything though, and am always happy to watch recordings and read reports of usability studies.

change your line of job, there must be a lot of other things that go over your head.

Keeping it classy. Personal attacks are always the best way to support your argument.

I get that you are not interested in this feature request, now please explain why you absolutely want to stop others from getting this ? what issue will you have if it ever gets implemented ?
you will still be able to use your 2-key shortcut if you please, so what is your problem ?

You "got" something I never wrote. I have never advocated for not implementing this feature request. I have provided people with ways to workaround not having their "favorite thing" available "right now", and pointed out that people are hyperbolically making it a bigger issue than it is. I have no problem, but for whatever reason you thought to make this personal. There's no need for that -- it doesn't bolster what you're trying to say and doesn't foster a positive community.

BoneTone

@7twenty said in Option to Open a URL / Search Results in a New Tab from the Address Bar with "Enter":

You can call it whatever you want. The very first response given in this thread is to use QC, and two times after that. And for that reason I, and probably many others, started doing the same.
Getting used to using a modifier key for all of these interactions is an option, but it's not what the request is about.
I'll ask the question again, why does QC have an open in new tab option, and for that matter, also the search box?

Well, you can reply to those posts instead of mine if you have questions about QC. I don't use Quick Commands and made no mention of them in my posts. It's one of those features of Vivaldi that many find useful, but I've never incorporated in my workflows.

I provided a different workflow to workaround this. If you don't want to use it, that's fine and your prerogative. As it requires no additional time or keystrokes, hopefully some find it useful as long as Vivaldi operates the way it currently does in this respect.

This is what makes Vivaldi such a great browser -- it supports many different ways of doing things. So when there's a bit that doesn't work exactly the way we would prefer, there are usually multiple ways to achieve the same thing without significantly greater effort until the dev team has the resources to address the request.

cannibalox

@BoneTone You own attitude triggered the following replies. You may have had good intentions by coming here to provide alternative workarounds to our issue, however you also omitted the following points (did you read the whole thread ?):

it was clearly stated that we (the requesters) already knew about the current workarounds and that these workarounds are not ideal for us.
you started by dismissing the requests as "it's a rare issue and again not a major problem." then on with the snarky questions "Please do so. How is that related?" to which I'll gladly reply, although your expertise in the field seem to surpass mine.... Please enlighten me, and explain to me why they introduced [sticky keys](https://www.disabled-world.com/assistivedevices/computer/sticky-keys.php) in major operating systems if no-one actually has a use for them ?
being an expert in disabilities doesn't grant you any expertise in other's people workflows and needs.
the feature seems simple to implement and would ensure a more consistent behavior between the address bar and the Quick Command bar; more consistency usually means less friction for everyone. (for instance, I would also like all commands from QC to be available straight from the address bar/omnibar).

From where I stand, you just came here to tell me that you know better than I do, what's good for me. Basically saying `you don't really need that, you'll get used to it'.

In this matter, regardless of our initial intentions, I don't think your posts were helpful, nor did they help to "foster a positive community" (as far as this thread is concerned at least).

have a nice one.

Pesala

@cannibalox:

Please enlighten me, and explain to me why they introduced sticky keys

You shot down your own argument there. Anyone who has difficulty pressing two keys at once can enable Sticky Keys. If every application offered complete flexibility on customising the keyboard, sticky keys would be superfluous, but they do not. Vivaldi is a lot better than most apps in this.

If anyone does not need to use sticky keys, then the suggested methods of using one finger to press Shift+Enter, or two fingers to press Alt+Enter are not difficult to do.

The only argument remaining is that users might lose work if they forget to hold down shift or alter. I never use any other browser, but I still sometimes press the wrong shortcut and lose work. If one uses Vivaldi as one’s default browser then muscle memory soon adapts to the selected method.

Bottom Line: Some users are over-egging the importance of this issue (which is well down the list of popular requests). There are currently 3,000 feature requests and tens of thousands of bugs to fix, and not many more developers than there were in February 2018 when this thread was started. We all have to wait patiently for our pet issues to be fixed.

It is tiresome to be accused of being unfriendly or dismissive because we suggest a work-around while users are waiting for an issue to be fixed. It is condescending to suggest that we do not understand the issue.

cannibalox

let's focus for a bit before I get into details :

I believe that using enter is faster and requires less keypresses than using shift-enter or alt-enter
I would like to open new tabs when entering an url in the address bar; I think it should work similarly to the QC popup.
This could be a 3rd choice in the existing menu : settings > Address bar > Open address in new tab > add an option for enter

details :

it seems somehow you don't agree with this simple fact : pressing enter requires less keypresses (and by extension less time) than pressing shift enter or alt enter
¯\__(ツ)_/¯ let's agree to disagree here...
about sticky keys [1] (which is an edge case, but very important if your are suffering from dextery issues; number is not always equal to importance) :

if you've ever used sticky keys, you know how cumbersome and slower they are compared to a single-keypress : basically you have to press at least 3 keys in succession to output one command... so I don't think I'm shooting down my own argument: see point 1)
even if we put disability/dexterity issues aside, I still believe that the experience should be consistent between the QC bar and urlbar : I can type an url and press enter in QuickCommand to open a new tab, the same action in the url bar will have a different output as it will open the url in the active tab.

the implicit behavior is different from the actual output. this creates friction in the UX hence the feature requests in this thread. (there is no way to tell that the outcome will differ, whereas the UI is quite similar and seems to offer the same functionality : opening an url)

it's not a workflow-breaking issue; but it's inconvenient.
We are talking about quality of life improvement and more streamlined workflows.
Depending on your situation, these QoL improvements can have major or minor benefits (or none at all).
For some of us, it will be a major improvement.
it seems that for you, it will not have any impact, so I can understand you are not interested, but I don't get why you are so vehement.
implementing this feature is really an extension/improvement on existing options, not a major change nor a re-design.

You say : " Some users are over-egging the importance of this issue" ... "It is tiresome to be accused of being unfriendly or dismissive". Well, I regret to inform you that you are indeed dismissive; yet I don't think you are unfriendly.

"We all have to wait patiently for our pet issues to be fixed." : as you stated, the thread has been started in 2018... no-one is asking for an urgent fix; we are merely posting to inform that this is still an ongoing isuue (meaning that for some people, the workarounds are still less satisfactory than the proposed feature request) that would be nice to fix.

priorities should be defined by the devs by factoring difficulty/usefulness/schedule.
I don't think shutting down or discouraging feature requests is helpful in any way.

[1]: side note regarding the sticky keys : I am NOT advocating for sticky keys, actually I think sticky keys are a very bad implementation of accessibility features. this should really be contextual adaptation of the UI/UX: instead of trying to adapt shortcuts literally, the input areas/textareas/forms should provide accessibility shortcuts in the form of popups with directionnal options/scrolling lists/audio. there are multiple alternatives that should be implemented in OS

Pesala

@cannibalox said in Option to Open a URL / Search Results in a New Tab from the Address Bar with "Enter":

I don't think shutting down or discouraging feature requests is helpful in any way.

No one is shutting down or discouraging the feature request. I was the first to vote for it. If you voted for it, that is all that anyone can do. All you are doing now is repeating what has already been said several times.

Yes it seems easy to do.
Yes it would be an improvement.
No it is not urgent. We will have to wait until it is done.
The workarounds offered are not ideal.

cannibalox

@Pesala well my original intent was to upvote to mark the topic as still relevant in 2020, for the rest I'm just replying whenever someone pings me out of common courtesy.

projektilski

I keep coming back to check if this simple and easy to implement feature, which many other browsers have, is implemented and to my huge disappointment it is still not available.

This straight slap in the face of the community. I would understand if this request is something that requires significant time to develop however this is not the case. It is exact opposite.

Waiting so long for such simple (and not innovative feature in any way) is simply unacceptable as it shows that you cannot rely on this browser and its development.

BoneTone

@projektilski there's no such thing as a simple and straightforward feature involving the address bar. Everyone just thinks about what the feature does, and maybe if they get that far, how many lines of code it would take to implement. The address field is packed with functionality. Any changes to it require a large QA effort; many different suites of tests, both manual and automated, must be completed before any such feature could be released. So the development resources necessary are not insignificant nor small.

This feature request isn't even in the top 50 of requests that the community has expressed their desire for. There has been no insult to the community, let alone a slap in the face. Everyone has their pet features they want to set implemented, but the community has prioritized many other feature requests ahead of this one.

Ayespy

@projektilski I suppose one could ask why you are slapping yourself in the face over this. Certainly, no one else is.

Pesala

@projektilski I understand how you feel. It sure beats me why they cannot find time to add a checkbox to settings.

I post this in my list of Easy to Implement Feature Requests back in May 2019.

projektilski

@BoneTone
I don't think you are a developer because if you were you would understand how easy is to implement such an option. You already have in your code option A and option B, adding option C does not involve any hard work. You have to put new checkbox and when selected fill already existing parameter which stores choices A or B (and now newly option C)

The rest of the code does not change.

Are those top 50 requests as simple as this one?

@Ayespy
Explain how am I slapping my face? Every few months I check if Vivaldi got this feature which it doesn't. I don't use Vivaldi because of that. It is not my loss nor am I crying about it. I mearly express my opinion that this is terrible from Vivaldi as this feature is extremely important to some users and it is simple to implement (unless there is some terrible coding in play).
What I see is that some of you are so narrow minded that they cannot phantom that this feature, for those that use it, actually a deal breaker and that it saves a lot of time and that there is no better replacement for it. People always need some other features which could come handy but they are usually are not deal breaker. You can work with out it. However opening new tabs directly from address bar with only enter is for those that use it something they use for 1000 or 10000 times per day. It is one of the most used actions used during web surfing. You should try to understand why this feature is extremely important for those that use it. It is not a gimmick or some visual tweak that we are requesting.

BoneTone

@projektilski My entire point was that it's not the implementation that makes this feature require a significant effort. Some people just think about the feature, you got to the second step, thinking about the implementation. As I wrote, it's the QA effort that so few think about or understand if it does cross their mind, which didn't even factor in any of your comments. Releasing software of the quality that Vivaldi does requires a strong QA department. You don't just implement a feature, try it a few times, see that it works, and call it good.

The rest of the code does not change.

It's precisely this thought that leads to bugs getting released.