for webxdc, the system-back-button should do the same
as the back-button in the title bar - just close the webxdc.
without this commit, it loads the previous page, which is often unexpected -
eg. many games use reload() for simplicity,
so you would have press one time 'back' for each round :)
even if there may be situations where this may be useful,
we do not want to encourage webxdc to rely on the system-back-button -
eg. desktop or ios currently just do not have this button.
technically, this pr changes the default -
so, for all classes derived from WebViewActivity, the system-back-button will
now behave as the title-bar-back-button.
for the local-help, this behavior is changed explictly -
i think, for HTML-mails, the 'just close' approach is also better.
show the chat name in front of the webxdc name to
- prevent phishing (the window will not show just the name of your bank)
- give the user an idea about where the webxdc sends messages to
(important eg. when using the same webxdc from different chats)
the UI does not check before selection if a message can be resent,
this is subject to change and not worth the effort.
instead, just an error is shown.
for the ID_NEVER_SHOW_AS_ACTION_* - this is a bit ugly,
however, the few alternatives i tried were even more uglier,
Java and Array-primitives are just not great.
as it is not changed often, it is probably not worth the effort to dive deeper.
* Fix off-by-one-error
* Wait longer with refreshing shortcuts to make sure that it doesn't affect the start of the activity
* Don't unnecessarily clear "screenshot security" flag
If this setting is off, the flag will never be added, so no need to
remove it.
Marking the message as seen starts ephemeral timer if it is not
already started.
Due to the bug in the core, sometimes messages were marked as seen
without starting ephemeral timer. This can also happen due to other
errors, like database access timeout.
Always calling markseenMsgs whenever the message is displayed, even if
it is already seen, ensures that ephemeral timer is started
eventually.
* enable Window.sessionStorage, Window.localStorage and IndexedDB APIs
* scope localStorage per message
when using a custom scheme as `webxdc`,
different messages will share the same localStorage,
even though different domains are in use.
not sure if that is an Android bug, however,
using `https` as the scheme scopes messages correctly,
so we are just using that.
- in bubbles, just say "Webxdc",
the text is replaced by the summary set by the app -
this is also the reason, why more useful information are not-so-good here,
it will not be shown often, and that may be irritating.
in case of the bytesize - we also do not show bytesize stickers etc.,
users can get it always at message-info.
- for drafts, we say "Tap to open",
maybe a start-button may be nice as well, however, that is some more work,
and it is not even clear we want to keep that button in the bubbles.
B. Petersen