Comment by ~lufte on ~lufte/vimini
I was delaying adding CLI arguments because I wasn't sure what to support, but I guess I should start simple and URL is the most obvious one. I'll work on it.
Ticket created by ~lufte on ~lufte/vimini
We could notify users of a missing close_notify with a notification but still show the content we've downloaded. This would make it compliant without losing functionality.
Ticket created by ~lufte on ~lufte/vimini
The new text wrapping feature is now working properly after https://github.com/iced-rs/iced/pull/2723
Ticket created by ~lufte on ~lufte/vimini
Including an underscore in a search yields no results when there should be.
Ticket created by ~lufte on ~lufte/vimini
We need a way to ask the user for input before proceeding with some actions, for example:
- The destination of a download
- Whether to continue to a capsule if it's a cross-domain certificate usage situation, required for #85
- Whether to navigate back or forward to a URL which resulted from submitting an input, required for #20
- Whether to continue to a capsule with an expired/unknown certificate, required for #16
qutebrowser's prompt mode, the obvious approach, has the following drawbacks:
- It's a new mode, but it would be weird to be switching tabs in normal mode and suddenly be stuck in a new mode because this one tab is requiring input.
- The keys required to answer need to be shown in the screen. Does it mean they are hardcoded?
Another option is to use the document itself. Have special links and inputs that, instead of navigating to a URL, perform an internal action within the browser. This doesn't require a new mode, and users can navigate these documents normally. Multi-step processes, like downloading a file, require more interaction and this solution may fall short. How do alert the user that the path doesn't exist? How do we autocomplete the path?
Comment by ~lufte on ~lufte/vimini
This is handled by rust-url.
REPORTED
RESOLVED CLOSEDComment by ~lufte on ~lufte/vimini
lufte referenced this ticket in commit cc7f171.
REPORTED
RESOLVED FIXEDComment by ~lufte on ~lufte/vimini
lufte referenced this ticket in commit 751d9ed.
REPORTED
RESOLVED FIXEDTicket created by ~lufte on ~lufte/vimini
Clicking a link to a URL which is set up to use a certificate from a URL that is not set up to use that same certificate should not work transparently. Warning the user, though, requires some sort of prompt mode that we currently don't have.
I had though about loading the URL using the default certificate, warning users about it with a notification, and ask them to reload the tab to force the usage of the right certificate. This is problematic because stuff could be submitted with the default certificate unintentionally, or the URL could redirect somewhere else and it's now too late to reload.