| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Added a utility for setting up dialog titles consistently. They are now in all-caps and aligned appropriately.
|
|
|
|
|
|
Post merge.
|
|
# Conflicts:
# CMakeLists.txt
# Depends-Android.cmake
# res/about/version.gmi
# res/lang/cs.bin
# res/lang/eo.bin
# res/lang/es.bin
# res/lang/fi.bin
# res/lang/gl.bin
# res/lang/ia.bin
# res/lang/ie.bin
# res/lang/ru.bin
# res/lang/sr.bin
# res/lang/tok.bin
# res/lang/tr.bin
# res/lang/uk.bin
# res/lang/zh_Hant.bin
# src/app.c
# src/main.c
# src/ui/documentwidget.c
# src/ui/labelwidget.c
# src/ui/sidebarwidget.c
# src/ui/util.c
|
|
When navigating via home row, ensure that other widgets will not trigger when keys are pressed. The document is given keyboard focus even though it is not flagged as focusable, to make sure it gets to handle all the keys first.
On macOS, disable all native menu items that have a home row keyboard shortcut.
Also on macOS, disable all native menus when changing bindings.
IssueID #419
|
|
|
|
|
|
Use a regular font weight and dimmer color for the entry date.
|
|
SGR codes 2 and 10.
|
|
|
|
|
|
|
|
Portrait phone URL input field has some special padding rules. This should be done elsewhere (updateMetrics_Root?), but InputWidget does not check the Widget paddings currently.
|
|
|
|
|
|
The navbar is an important tap target, so it should be the same height as most menu items and the toolbar.
|
|
|
|
The keyboard height was miscalculated if there were system keys under the window.
|
|
Actions for the first two mobile portrait phone toolbar buttons can be chosen in Settings.
|
|
On iPad, activity views are popovers and require information about the source. The UI doesn't provide this, though, so just use the long-press tap position for now.
|
|
|
|
|
|
|
|
Use of uninitialized memory was possible related to the folder selection dropdown.
|
|
|
|
|
|
A convenient way to copy the current page's source and open the Titan upload dialog with it prefilled.
IssueID #415
|
|
Image responses get inlined on gemtext pages.
It would make sense to use this mechanism for all media since the MIME type is ultimately what matters in determining the appropriate presentation. The file extensions shouldn't matter.
IssueID #373
|
|
The banner would sometimes appear only after the page had finished loading, because the site icon got lost when the GmDocument was switched.
|
|
|
|
The inline downloads UI finally has some interactivity: left-clicking on a finished download opens it in the default viewer app, and right-clicking shows a context menu with relevant actions.
|
|
After receiving content of unsupported type, show a footer action button to open it in another app.
IssueID #135
|
|
|
|
These should be user-configurable, though.
|
|
|
|
Send a notification from the Java side when the software keyboard
is shown.
|
|
|
|
|
|
|
|
Making URL encoding a little less convoluted. Now when sending out a request, the URL is fully encoded except for reserved characters. In the internal representation, non-ASCII characters are in decoded form (i.e., IRI).
This means that if the user enters a URL in the input field manually, its non-ASCII characters will be percent encoded as well. However, in this case the user is expected to manually escape all reserved characters because the input field can't tell the difference between what is intended to be a reserved separator and what isn't. For example, a server might expect &-separated fields, and if the user enters such fields manually in the URL field, they shouldn't be converted to %26.
When forming a query URL in the input dialog, user-entered text is fully percent-encoded because in that case the input is just a generic text string.
IssueID #410
|
|
|
|
IssueID #427
# Conflicts:
# res/about/version.gmi
|
|
|
|
|
|
|
|
|
|
IssueID #427
|
|
|
