QuasselDroid-ng issueshttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues2022-01-10T05:16:51Zhttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/243Display inline image preview2022-01-10T05:16:51ZTrigextrigex@protonmail.comDisplay inline image previewAn inline image preview, not unlike that of another irc client like The Lounge, or like Discord's inline image previews, would be fantastic! In the IRC channel I frequent, it is very image heavy and it really is a big pain to have to man...An inline image preview, not unlike that of another irc client like The Lounge, or like Discord's inline image previews, would be fantastic! In the IRC channel I frequent, it is very image heavy and it really is a big pain to have to manually click each link, especially with multiple images in a row.
This feature would pull images from posted links in chat.
Is there any technical reason for why this hasn't been implemented yet, or has there just been no demand to?2.0.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/238Pressing Up arrow key clears current/unsent message without saving it to mess...2022-01-10T05:17:20ZShane SynanPressing Up arrow key clears current/unsent message without saving it to message history### Steps
1. Connect keyboard with either physical arrow keys or (untested) software emulation
2. Open a buffer within Quasseldroid to reveal the message input box
3. Type and send a short message (ensuring Quasseldroid has a message ...### Steps
1. Connect keyboard with either physical arrow keys or (untested) software emulation
2. Open a buffer within Quasseldroid to reveal the message input box
3. Type and send a short message (ensuring Quasseldroid has a message in the input history)
4. Type another, different message, but don't send it
5. Press the Up arrow key
6. Observe the results
7. Press the Down arrow key
8. Observe the results
### Expected
* After pressing the Up arrow, the current message is replaced with the most recently sent message
* After pressing the Down arrow, the most recently sent message is replaced with the unsent, still-being-composed message
This matches the behavior of Quassel desktop.
### Actual
* :heavy_check_mark: After pressing the Up arrow, the current message is replaced with the most recently sent message
* :x: After pressing the Down arrow, the most recently sent message is replaced with.. **nothing - the unsent, still-being-composed message is now lost**
### Details
Quasseldroid [v1.3.3](https://git.kuschku.de/justJanne/QuasselDroid-ng/commit/b622ad63056b6054b06e09f8e1f1ef2b0c3aaf9a )
Using a USB keyboard with the USB OTG adapter that comes in the Pixel box, on Android 11, Pixel 4 XL.
*Priority is set to high due to the potential to lose chat messages in the middle of writing them on ChromeOS or with a USB/Bluetooth keyboard. This may be a smaller impact, though.*1.6.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/227Server Redirect Notices and User Redirect Notices should be independent2022-01-10T05:15:34ZPeGaSuSServer Redirect Notices and User Redirect Notices should be independentAs explained on IRC:
```
[12:15:49] <PeGaSuS> justJanne: I found a weird behaviour in Quasseldroid in my phone (Huawei P20 Lite). Menu > Client Settings > Message Redirection > Enable "Redirect User Notices"
[12:15:49] <PeGaSuS> Tap the ...As explained on IRC:
```
[12:15:49] <PeGaSuS> justJanne: I found a weird behaviour in Quasseldroid in my phone (Huawei P20 Lite). Menu > Client Settings > Message Redirection > Enable "Redirect User Notices"
[12:15:49] <PeGaSuS> Tap the back arrow. Menu > Client Settings > Message Redirection > "Redirect User Notices" and "Redirect Server Notices" will be enabled.
[12:15:49] <PeGaSuS> Disable "Redirect Server Notices", tap back arrow, Menu > Client Settings > Message Redirection > All redirects will be disabled
[12:17:10] <PeGaSuS> shouldn't "User Notices" and "Server Notices" be independent?
```1.6.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/245ipv6 in connection list gets formatted as f00::ba2:4242 instead of [f00::ba2]...2022-05-17T17:21:18ZJanne Mareike Koschinskiipv6 in connection list gets formatted as f00::ba2:4242 instead of [f00::ba2]:4242https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/241Confirmation Dialog for joining channels2021-08-09T16:45:11ZJanne Mareike KoschinskiConfirmation Dialog for joining channelshttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/237Up/down arrow keys don't move cursor in multi-line message edit mode2022-01-10T05:17:24ZShane SynanUp/down arrow keys don't move cursor in multi-line message edit mode### Steps
1. Connect keyboard with either physical arrow keys or (untested) software emulation
2. Open a buffer within Quasseldroid to reveal the message input box
3. Type and send a short message (ensuring Quasseldroid has a message ...### Steps
1. Connect keyboard with either physical arrow keys or (untested) software emulation
2. Open a buffer within Quasseldroid to reveal the message input box
3. Type and send a short message (ensuring Quasseldroid has a message in the input history)
4. Expand the message input box to switch to multi-line edit mode
5. Type a long enough message that it wraps across several lines (e.g. copy-paste a few words)
6. With the input caret/cursor on the bottom, press the Up arrow key
7. Observe the results
### Expected
The input caret/cursor navigates upwards through the text, as happens with e.g. QKSMS on Android or Quassel desktop and Kate on KDE.
Only when the input caret/cursor is at the very top of the message (or anytime in single-line edit mode) should the message history be accessed.
### Actual
Quasseldroid interprets the up arrow as a request to switch to the message history, despite being in multi-line edit mode.
### Details
Quasseldroid [v1.3.3](https://git.kuschku.de/justJanne/QuasselDroid-ng/commit/b622ad63056b6054b06e09f8e1f1ef2b0c3aaf9a )
Using a USB keyboard with the USB OTG adapter that comes in the Pixel box, on Android 11, Pixel 4 XL.
*Feel free to edit the priority as desired - I'm not sure how many folks use Quasseldroid with a keyboard - ChromeOS + USB/Bluetooth keyboards on Android, possibly?*1.6.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/231Make swipe left and right work from any point of the view2022-01-10T05:14:20ZToni SpetsMake swipe left and right work from any point of the viewI've noticed that it's *really* hard to get the user list or the server/channel list open with swipes because it requires you to start the swipe from the very edge of the screen.
Slack and Discord both allow you to start swiping from an...I've noticed that it's *really* hard to get the user list or the server/channel list open with swipes because it requires you to start the swipe from the very edge of the screen.
Slack and Discord both allow you to start swiping from any part of the screen (to left or right) and it will slide open either the channel or user list.
This is a small UX improvement that would make Quasseldroid immensely easier to use one handed.
Thanks!2.0.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/223Expanded (multi-line) message input box won't collapse with swipe down except...2022-01-10T05:20:14ZShane SynanExpanded (multi-line) message input box won't collapse with swipe down except under Send button## Steps
1. Connect to core
2. Swipe up message input box
3. Swipe down message input box by dragging `Write a message…` down
4. Observe message input box state, expanded or collapsed
5. If message input box is collapsed, swipe up m...## Steps
1. Connect to core
2. Swipe up message input box
3. Swipe down message input box by dragging `Write a message…` down
4. Observe message input box state, expanded or collapsed
5. If message input box is collapsed, swipe up message input box again
6. Swipe down message input by dragging underneath the `>` Send button
## Expected
For both steps 3 and 6, the expanded message input box collapses.
## Actual
The expanded message input box does not react to drags in step 3, but step 6 will collapse the input box.2.0.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/217reconnect jumps to latest messages2022-01-10T05:21:34Zhyperfektreconnect jumps to latest messagesIf the connection to the core is reacquired while reading in a channel, the view reloads and jumps to the latest messages.
This is undesirable especially on mobile connections, where it might happen very frequently.
Version: 1.2.24If the connection to the core is reacquired while reading in a channel, the view reloads and jumps to the latest messages.
This is undesirable especially on mobile connections, where it might happen very frequently.
Version: 1.2.242.0.0https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/211Allow disabling/enabling multiple reconnection triggers2019-06-17T18:42:51ZJanne Mareike KoschinskiAllow disabling/enabling multiple reconnection triggersJanne Mareike KoschinskiJanne Mareike Koschinskihttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/206Allow disabling background execution2019-06-07T20:25:57ZJanne Mareike KoschinskiAllow disabling background executionJanne Mareike KoschinskiJanne Mareike Koschinskihttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/205Background execution notification/icon visibility can't be configured on pre-6.02019-06-07T20:19:54ZJanne Mareike KoschinskiBackground execution notification/icon visibility can't be configured on pre-6.0Janne Mareike KoschinskiJanne Mareike Koschinskihttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/199Implement message attachments and link unfurling2019-04-16T07:42:31ZJanne Mareike KoschinskiImplement message attachments and link unfurlinghttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/198Add per-channel notification options2019-04-16T07:41:54ZJanne Mareike KoschinskiAdd per-channel notification options- mute channel
- always notify on message in this channel- mute channel
- always notify on message in this channelhttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/197Add search in nicklist2019-04-16T07:40:29ZJanne Mareike KoschinskiAdd search in nicklisthttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/196Add workaround to avoid keyboard showing every time2019-04-16T07:39:51ZJanne Mareike KoschinskiAdd workaround to avoid keyboard showing every timehttps://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/195Add workaround for IPv6 enabled cores that only listen on IPv42019-04-16T07:39:28ZJanne Mareike KoschinskiAdd workaround for IPv6 enabled cores that only listen on IPv4https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/159Empty/invalid values should be rejected in several fields2022-01-10T05:15:00ZShane SynanEmpty/invalid values should be rejected in several fields# Test case
## Steps
1. Connect to core
2. Go to overflow menu → `Core Settings`
### `Network` (servers)
1. Add a new network
2. Set `Network Name`
3. Don't add any servers
4. Press `Save`
*This one may be more difficult to imp...# Test case
## Steps
1. Connect to core
2. Go to overflow menu → `Core Settings`
### `Network` (servers)
1. Add a new network
2. Set `Network Name`
3. Don't add any servers
4. Press `Save`
*This one may be more difficult to implement and can be set aside to a new issue if desired.*
Quassel desktop actually even catches this if you delete all servers from a network after adding it:
> ### Invalid Network Settings
> **The following problems need to be corrected before your changes can be applied:**
>
> * All networks need at least one server defined
### `Network` (name)
1. Add a new network
2. Don't set `Network Name`
3. Add a dummy server
4. Press `Save`
### Network → `Server`
1. Add a new server to an existing network
2. Don't fill in `Host`
3. Press `Save`
### `Identity`
1. Add a new identity
2. Don't fill in `Identity name`
3. Press `Save`
### `Chatlists`
1. Add a new chat list
2. Don't fill in `Name`
3. Press `Save`
*Technically, this one is accepted by the Quassel core, but the desktop GUI requires specifying a name.*
### Ignore List → `Ignore Rule` (ignore rule)
1. Add a new ignore rule
2. Don't fill in `Ignore Rule`
3. Press `Save`
*Technically, this one is accepted by the Quassel core, but the desktop GUI requires specifying an ignore rule.*
### Ignore List → `Ignore Rule` (scope)
**This one needs fixed in upstream Quassel, too. It can be ignored for now, or fixed.**
1. Add a new ignore rule
2. Fill in `Ignore Rule`
2. Set Scope to `Network Scope`
2. Don't fill in `Scope Rule`
3. Press `Save`
*Technically, this one is accepted by the Quassel core, and the desktop GUI does not require specifying an ignore rule scope, but it probably should.*
### `Aliases` → `Alias` (name)
1. Add a new alias
2. Don't fill in `Name`
3. Press `Save`
Bonus: this logs a crash report in Quasseldroid due to a non-null value set to null. See [the crash issue for the specifics](https://git.kuschku.de/justJanne/QuasselDroid-ng/issues/161 ).
### `Aliases` → `Alias` (expansion)
1. Add a new alias
2. Don't fill in `Expansion`
3. Press `Save`
Bonus: this logs a crash report in Quasseldroid due to a non-null value set to null. See [the crash issue for the specifics](https://git.kuschku.de/justJanne/QuasselDroid-ng/issues/161 ).
## Expected
Quasseldroid rejects the empty fields in the above cases.
## Actual
Quasseldroid accepts the empty fields in the above cases, highlighting with red/whatever method Android uses to indicate a field is required.
# Additional
The Android approaches appears to be using `setHint` and [`setError`](https://developer.android.com/reference/android/widget/TextView#setError(java.lang.CharSequence) ).https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/142Delete selected messages from log2022-01-10T05:15:04ZHannah von RethDelete selected messages from logWith the recent spam wave it would be interesting to be able to delete selected messages from the log.With the recent spam wave it would be interesting to be able to delete selected messages from the log.https://git.kuschku.de/justJanne/QuasselDroid-ng/-/issues/127Option to mark all channels as read, per network basis2022-01-10T05:15:01ZPeGaSuSOption to mark all channels as read, per network basis* [ ] Normally every user is in several channels on a network, and some are more important than others. Would be nice to have an option to mark as channels as read, per network basis, after we take a look into the most important ones.* [ ] Normally every user is in several channels on a network, and some are more important than others. Would be nice to have an option to mark as channels as read, per network basis, after we take a look into the most important ones.