Solved Rename "Clone Tab" to "Duplicate Tab"
-
@pafflick
There is absolutely no reason to exclude features from sync, just because they are only vailable on desktop and not on mobile. We had to wait years for the search engine sync, because the destop and mobile build didn't have te same backend. Following this logic, menu customization is barely a solution for any related issue, because we have to make the same adjustments on every installation, which is very annoying.I understand, that your solution is better than nothing, but it's far from ideal, and even far from acceptable.
-
@nekomajin But who said anything about excluding something from Sync? I'm just lost here...
Menu customization is not a solution for each similar request (nobody argued that it is), but it's still the best solution for many of them, as there is often no consensus on how should some things be presented or where should they be placed.
As I said: there's no universal setting that fits everyone, hence the focus on customization and flexibility, rather than forcing "the only right solution" upon everyone. -
@pafflick
I am too lazy to look it up, but one of the developers said a few weeks ago, that for search engine sync, they had to make modifications in the backend, because the desktop and mobile implementations were incompatible. Sync came before mobile, and search engine sync was among the most upvoted requests, but we had to wait years to make it happen.I understand, that menu customization is a very powerful feature, because it can cover a huge variety of unique issues, but it's not a real solution until it's being synced. Menu sync should have been there from day one of the introduction of the feature.
I don't see how it differs from other synced features. The only reason I can think of is the lack of menu customization on mobile. As long as it's not synced, any related solution is just an annoying factor.
-
@nekomajin That's true - almost the entire backend on the desktop had to be rebuilt for the search engines to allow syncing them with the mobile version. We wanted to implement it for the 5.2 release, but it turned out to be such a tremendous task, that we had to revert the changes temporarily, as we couldn't tackle all the major issues in time. Yes, development can sometimes take years in such cases.
@nekomajin said in Rename "Clone Tab" to "Duplicate Tab":
Menu sync should have been there from day one of the introduction of the feature.
That would cause the release of said feature to be delayed even more, so I believe a lot of people who don't use Sync (or profiles) would disagree with that statement.
@nekomajin said in Rename "Clone Tab" to "Duplicate Tab":
The only reason I can think of is the lack of menu customization on mobile.
But it's not the case. Whether a feature is available in sync has nothing to do with its presence on Mobile. However, if it is present, then it has to be compatible (as is the case with the search engines sync).
-
@pafflick
I follow the dev releases, and I am not complaining because of this delay. Shit happens, it's not a problem.That would cause the release of said feature to be delayed even more, so I believe a lot of people who don't use Sync (or profiles) would disagree with that statement.
Why exactly? You release a feature, let us test it, and if it works properly, you can implement sync in the next major release. That's only a few months delay at most, which is acceptable, and no harm done to those, who don't use sync.
But it's not the case. Whether a feature is available in sync has nothing to do with its presence on Mobile.
What is the cause of the delay then? Menu customization is one of the most powerful features of Vivaldi. It can solve A LOT of issues on it's own. And please, don't tell me you don't have enough resources, because you had time to implement a reading list...
However, if it is present, then it has to be compatible (as is the case with the search engines sync).
I agree.
-
@nekomajin said in Rename "Clone Tab" to "Duplicate Tab":
You release a feature, let us test it, and if it works properly, you can implement sync in the next major release. That's only a few months delay at most, which is acceptable, and no harm done to those, who don't use sync.
What is the cause of the delay then? Menu customization is one of the most powerful features of Vivaldi. It can solve A LOT of issues on it's own. And please, don't tell me you don't have enough resources, because you had time to implement a reading list...I'm afraid that introducing a full sync of all settings is a little bit more difficult than just pushing a few buttons or adding
sync: true
here or there. Developing a browser is much more difficult than most people would think.
As for the question of "why we didx
instead ofy
" - it's part of the company's know-how, which I'm not authorized to disclose. I will instead reply with this: it's much, much more complex than it looks from the outside. -
@pafflick
OK, I accept that, but in this case, please, don't advertise menu related options as solutions. These are just band-aids, because they create other problems. -
@nekomajin They are solutions to many users (as people use different setups), so they're marked as such, to make them easier to find. I always mention that in the highlighted post.
@nekomajin said in Rename "Clone Tab" to "Duplicate Tab":
they create other problems
Please use the Support & Troubleshooting category to report your problems. Please remember about troubleshooting and searching the forum for relevant threads before starting new ones. If an issue is easily reproducible, you can create a bug report.
-
-
The change has been implemented in Vivaldi 5.6. Read more about the new version on our blog: https://vivaldi.com/blog/vivaldi-5-6-on-desktop/.
-
-
-
-
-
Thanks for this. I've wanted "Duplicate" or "Dupe" for years, instead of "Clone". Because the latter is way too much like "Close".