Can not open local .HTML file
I drag-n-drop local .HTML file to Iron window and it immediately opens there. I do the same with Slimjet. It works just fine. Not to mention the ol' IE, where it worked for ages... Why I can't do the same with Vivaldi??? Background: * I keep all my local records in .HTML files rather than in .TXT. Thus it's very important feature in any browser I use. * Using Vivaldi 1.2.470.11 (Developer Build) (64-bit)
Not yet. You can do it on the desktop, but not in the taskbar.
What I'm dong with other browsers is - I press left mouse button on a local HTML file, then drag it keeping left mouse button down to the browser's window and it usually opens that local file in that browser.
It's not possible with Vivaldi. It shows "+Copy" and nothing happens there.
BTW, why "+Copy"? I don't intend to copy anything there. I want to "Open" my file in the window.
You're right. It only works on the browser's desktop shortcut, not on the window itself. That function is not written yet.
I hope it will be implemented soon
Supporting DnD (drag-and-drop) is very generic and useful feature. While implementing it please keep in mind that destination (in this case - Vivaldi) should be able to accept not only local files, but any source objects. E.g. I can DnD link from Vivaldi's page to SlimJet browser and the latter will open that link there. Second use case is - if you DnD link on web page to the same web page, browser will open it in background in its new tab. It's very convenient in cases you use a search engine results page with many lings on it Simple DnD will open that link in new background tab. You do the same to the next link and so force… You;re still looking at the search results page while links of your interest are opening in background in new tabs... Again, it's very convenient in many use cases.
Hi, zulu. I'm a user like you. You can submit bugs and feature requests at https://vivaldi.com/bugreport
Full drag and drop support is sure to come, but the developers are swamped with requests, and some even more basic features are probably ahead of it in the pipeline.
Thanks for the suggestion. I've submitted this problem.
Where can I find the number of the submitted issue and / or see it there?
You should have left an email address, so they could mail you an issue number, which you could look for in future changelogs, and/or so that they could query you on what is exactly happening with a bug or whatever. There is no public bug tracking. You just get a number and look for it to be addressed in future builds.
The bug number is VB-17449 (it contains a link to this thread).
Thank you, guys. I've got email with the number.
It's too bad that I can't watch its current status and / or participate in it… From my experience, allowing public to participate in finding solutions usually greatly benefits development process and the project itself... On the other hand, closed, no-any-feedback systems suppress any incentives for people willing to contribute in it
Well, with "suppressed incentive," there are over seventeen thousand issues reported in 16 months. You will find a very involved community here, collaborating every step of the way with the developers, and helping each other as much as they can. This was the way the original Opera was developed - closed bug tracker, and a fervently-involved community. It worked then. I suspect it may work again now. Having public tracking may have its points, and I have no strong feeling about it one way or another. It's essential for open-source. For this project, it's probably not necessary.
… From my experience, allowing public to participate in finding solutions usually greatly benefits development process and the project itself... On the other hand, closed, no-any-feedback systems suppress any incentives for people willing to contribute in it
YMMV. Not seeing visible progress on a public bug-tracker can also lead to frustration and recrimination against developers as well. Thus far, I've only seen direct resolution on 2 of my 7 bug submissions, and it's not dampened my incentives to continue reporting and commenting in the least. Perhaps some of it's motivation: I'm not submitting bug reports to see my name in lights nor because I think my pet bug is the most important in the grand scheme of things - I'm simply giving free input to the developers of a free product, and I'm letting them make the call on what gets fixed when (if at all). In any case, I'm always free to go elsewhere if my frustration level with a browser were to get too high. (Note: I've worked through a lot of perspective "readjustment" about browsers during and since the Opera upheaval of the past several years…)
On the other hand, closed, no-any-feedback systems suppress any incentives for people willing to contribute in it
To make parts of bugtracking system open is too work intensive. Thats was discussed internally, and my not be changed in near future (i never say never… ).
And a open bug tracker will lead to anger against the developers if the beloved pet bug is not fixed as quickly as some people need. That needs more people looking into such open bug database and remove bad comments and unnessesary information.
If people want to know about their bugs, in Vivaldi forum are many internal Vivaldi testers who can check whats going and communicate.
I remember a big scandinavian browser company with less or even none communication between testers, users and developers. I dont tell you which, but you may gess.
Vivaldi Technologies tries to have as much communication to their users as they can, but the resources are limited.
And a open bug tracker will lead to anger against the developers if the beloved pet bug is not fixed as quickly as some people need.
Not in my experience. Those, who contribute know well, that on the developer's side there is no any obligation to implement proposed new features or fix specific bugs / problems. From the other side, allowing interested party to participate in issue discussion usually helps to find out better (more elaborate) solutions.
And BTW, if I could search / see opened bug tracking DB, I may not waste my time on duplicating already reported problems. In case, if I consider, that I have something valuable to contribute there, I may simply add it to that specific bug report thread…
I'm not submitting bug reports to see my name in lights nor because I think my pet bug is the most important in the grand scheme of things - I'm simply giving free input to the developers of a free product, and I'm letting them make the call on what gets fixed when (if at all). In any case, I'm always free to go elsewhere if my frustration level with a browser were to get too high.
I guess that just proves my point above…
I can understand you. Really. But… it is not my decision that the bug database is not public. I have no power to change this.
After a year, in vivaldi 1.8 this option is still not working...
I have to use file--open, or associate vivaldi to html files....very strange.
I thought it is a windows appliance, because this is the first program that cannot accept files by dropping it....