Option to let us set a custom .HTML file as our new tab blank page…
-
Please add option to let us set a custom .HTML file as our new tab blank page. This can open up a lot of powerful possibilities for what we can have in our new tab blank page.
-
still want
-
Remember those times, when you could set your bookmarks.html as browser homepage, which then subsequently appeared inside each new browser view?
Have browsers gotten to "smart"?
-
Have browsers gotten too "smart"?
No. Users have gotten too demanding.
Set your custom HTML page as your home page. Go to your home page instead of opening a new tab, or open a new tab, then go to your home page.
-
but i want my custom .HTML to auto open with every new tab
-
but i want my custom .HTML to auto open with every new tab
Add it to your bookmarks bar and use that instead of the New page button.
I understand that you want everything that you are used to in other browsers, but accept that it's not going to happen at once, and look for other solutions while you're waiting.
As I mentioned in your other thread, just submit one feature request via the Bug Report wizard, then you won't have to keep bumping your threads.
However, I am sure that the developers already know about this request, as there are several previous threads in a similar vein. Their aim is to produce a highly customisable browser like Opera 12.17, but we're still on version 1.1, so it may be a few years before Vivaldi gets even 95% of the features in old Opera.
-
please understand the purpose of this feature request is to be able to set a custom blank page for new tabs. so your alternative suggestions don't work.
-
It works if you have the browser set to "Open Bookmarks in New Tab."
-
It works if you have the browser set to "Open Bookmarks in New Tab."
but i don't like using that behavior, so it doesn't work for me
-
Please add option to let us set a custom .HTML file as our new tab blank page. This can open up a lot of powerful possibilities for what we can have in our new tab blank page.
You can already do that whit this extension
https://chrome.google.com/webstore/detail/new-tab-start-page-pro/mjfahldkpjhcnfbbmdhpjolcjpcfhcpj
-
nice to know about the extension. but for something this basic, i would prefer a powerful browser like vivaldi to have native support for it.
-
Sure. But as usual, a native function requires a lot of work on the development side, while the extension requires two seconds to download it.
The native speed dial requires a lot of love, we all know that. But there are other task that have higher priority, at least that's dev's position.
-
nice to know about the extension. but for something this basic, i would prefer a powerful browser like vivaldi to have native support for it.
"…for something this basic..."
"Basic" to you, utterly foreign to me.
To me, "basic" things are email in the browser, ability to put my bookmark bar vertically at the side, stacking pinned tabs or pinning stacked tabs, choice to open bookmarks in the panel or manager with a single click, broad choice in the appearance of the UI, low resource usage, ability to prevent autoplay of media, persistent setting to show images or not, visibility and retrievability of passwords, etc., etc. With a small team, every ounce of time and effort spent getting you what you want, delays my getting what I want. The developers are not guided by what other browsers are doing or have done. Their priorities are set by their initial vision, as modified by volume of user requests, and by the impacts of unanticipated obstacles like tenacious coding challenges and unpredictable changes in the underlying engine. So we cling to our preferences, but we adjust our expectations to more accurately reflect what is on offer in the real world.
-
vivaldi is meant to be a power user's browser–and every power user has their needs. there is no need for anti-progress comments. if you don't care for a particular feature request, then don't bother replying.
-
vivaldi is meant to be a power user's browser–and every power user has their needs. there is no need for anti-progress comments. if you don't care for a particular feature request, then don't bother replying.
I am all for progress. I am totally against spreading FUD about the browser just because it doesn't meet your single favorite criterion - or even because it's problematic on your machine, but not others.
If people want help, I give it. If they want to make suggestions, I'm all for it. If they want to criticize and judge some of the most creative and hardest-working developers anywhere, or disparage their work because it "should" do whatever makes them happy even though it's in its infancy, I will express my opinion on that.
I have probably done more to promote good will toward this browser on these forums than literally anyone else.
If you don't like my comments, don't bother to respond. It's not your job to police the forum or regulate my behavior. Good day.
-
I feel it's important that users know what they are dealing with when they use Vivaldi. This is immature software, and the developers are working their guts out trying to get it finished. The basic goals for the browser are nowhere near being met. All we have is a very good beginning.
It's not as though the Team is sitting around basking in the glow of a job well done and idly awaiting suggestions from users to tweak or add features to polish up a finished product and make it wonderful for everyone. Literally thousands of users each want their own personal itch scratched, and they want it ahead of everyone else's, because it's always the "most basic" or "most important" feature, but the thing isn't even DONE yet.
Patience is a virtue. An exceedingly rare one, it would seem.
-
still want…
-
still want…
Please, quit being a pest. This feature request has already been implemented. No doubt others will also be implemented in due course. There is no need to keep nagging for your wanted features. Just submit them via the Bug Report wizard, or add them to the Feature Requests thread (once only).
[attachment=4241]NewTabPage.png[/attachment]
Attachments: