Jaakko Keränen

This is intentional. To save space, a narrow URL field will not show the default "gemini:" scheme. This applies to all URL fields in the UI.

I agree the implementation isn't ideal. At least it should compare the length of the actual URL to the available space and not just check the width of the field.

64-bit is not a requirement, nor is Windows 7. As a practical matter, I only have a 64-bit Windows development environment set up for making prebuilt binaries, and no real...

This is already implemented on macOS and iOS. Which operating system and/or desktop environment are you requesting this for? Implementing it everywhere at once is quite a bit of work...

I'll take a look.

I think this is acceptable with this little addition: * The user triggers the Bookmark dialog * Lagrange fetches /favicon.txt _**if the "Fetch Favicon when Bookmarking" setting is enabled (default:...

Yeah this is one of the drawbacks of doing custom text rendering and UI controls... > other search results I saw suggest that there are cross-platform libraries Such a cross-platform...

I am committed to keeping Lagrange small and nimble, so there are practical limits to what can be achieved here. I'll incorporate accessibility features when they are reasonable given the...

> would something like self-voicing - i.e. Lagrange itself generating a voice to read out the text - be an option? Interesting idea. If we can assume that the user...

Comment I wrote in #322: My current thinking is that the path of least resistance here is to make it possible to have alternative UI chrome implementations in the app,...