briar issueshttps://code.briarproject.org/groups/briar/-/issues2020-10-22T13:48:39Zhttps://code.briarproject.org/briar/briar/-/issues/1799Allow the app to be locked as soon as it goes into the background2020-10-22T13:48:39ZakwizgranAllow the app to be locked as soon as it goes into the backgroundA user asked for the option to activate the app lock as soon as the app goes into the background.A user asked for the option to activate the app lock as soon as the app goes into the background.https://code.briarproject.org/briar/briar/-/issues/1798Delete account if wrong password is entered several times2020-11-15T13:41:23ZakwizgranDelete account if wrong password is entered several timesA user asked for the option to delete the account automatically if the wrong password is entered several times.A user asked for the option to delete the account automatically if the wrong password is entered several times.https://code.briarproject.org/briar/briar/-/issues/1797Forward private messages2020-10-15T10:16:15ZakwizgranForward private messagesA user asked for the ability to forward private messages. (When support for image attachments is released, I'm guessing the ability to forward individual attachments might also be useful.)A user asked for the ability to forward private messages. (When support for image attachments is released, I'm guessing the ability to forward individual attachments might also be useful.)https://code.briarproject.org/briar/briar/-/issues/1796Add option to disable animations2020-11-15T13:41:47ZakwizgranAdd option to disable animationsTwo Google Play users asked for the option to disable transition animations.Two Google Play users asked for the option to disable transition animations.https://code.briarproject.org/briar/briar-gtk/-/issues/74Audio notification when contacts come online2021-01-23T13:45:52ZBriar EnthusiastAudio notification when contacts come onlineParticularly, the rustling sound from Ricochet:
[https://raw.githubusercontent.com/ricochet-im/ricochet/master/sounds/online.wav](https://raw.githubusercontent.com/ricochet-im/ricochet/master/sounds/online.wav)
It's sooooo nice.Particularly, the rustling sound from Ricochet:
[https://raw.githubusercontent.com/ricochet-im/ricochet/master/sounds/online.wav](https://raw.githubusercontent.com/ricochet-im/ricochet/master/sounds/online.wav)
It's sooooo nice.https://code.briarproject.org/briar/briar/-/issues/1792Stepper isn't read in a meaningful order by screen readers2020-11-15T13:47:05ZakwizgranStepper isn't read in a meaningful order by screen readersThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the "stepper" that shows the steps in the process of adding a contact remotely isn't read in a meaningful order by screen...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the "stepper" that shows the steps in the process of adding a contact remotely isn't read in a meaningful order by screen readers. TalkBack navigation reads the steps "1 - Exchange links, 2 - Choose nickname" as "1, 2, Exchange links, Choose nickname".https://code.briarproject.org/briar/briar/-/issues/1791Non-text content should have a textual alternative2020-11-15T13:48:30ZakwizgranNon-text content should have a textual alternativeThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) found several places in the app where non-text content lacks a textual alternative:
- [ ] Password strength indicator
- [ ] Checkmarks...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) found several places in the app where non-text content lacks a textual alternative:
- [ ] Password strength indicator
- [ ] Checkmarks in the power management setup screen
- [ ] Checkmarks in the stepper when adding a contact remotely
- [ ] Diagram explaining how QR codes should or should not be exchanged
If any of these involve a lot of work we can create subtasks.https://code.briarproject.org/briar/briar/-/issues/1790Check whether text has enough contrast for accessibility2020-11-15T13:48:54ZakwizgranCheck whether text has enough contrast for accessibilityThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the placeholder text in input fields appears to have low contrast, but this couldn't be verified as the app doesn't allow...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the placeholder text in input fields appears to have low contrast, but this couldn't be verified as the app doesn't allow screenshots. There may be other places in the app, such as the coloured status messages in the pending contact list, where we're not meeting accessibility guidelines for contrast.
Contrast should be at least 4.5:1 for "normal" text or 3.0:1 for "large" text, defined as 18px or 14 px + bold. The light and dark themes need to be checked.https://code.briarproject.org/briar/briar/-/issues/1789Changes to status messages aren't visible to screen readers2020-11-15T13:49:20ZakwizgranChanges to status messages aren't visible to screen readersThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that when status messages such as those shown in the pending contact list ("Connecting", etc) are updated, screen readers aren...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that when status messages such as those shown in the pending contact list ("Connecting", etc) are updated, screen readers aren't automatically aware that the text has changed.
One way to make screen readers aware that text has changed is to give focus to the changed element. The "Password is too weak" message on the setup screen is an example of a status message that's correctly handled by screen readers.https://code.briarproject.org/briar/briar/-/issues/1788Text fields should have labels2020-11-15T13:51:14ZakwizgranText fields should have labelsThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the way we style text fields, showing placeholder text but not a label, is an accessibility issue because the placeholder...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the way we style text fields, showing placeholder text but not a label, is an accessibility issue because the placeholder text disappears when the user starts to type, leaving no indication of the field's purpose.
This is my fault - I argued for removing the labels because I think the way they move and change size when the field gains or loses focus interacts badly with automatically giving focus to the first text field.https://code.briarproject.org/briar/briar/-/issues/1787Transport indicators are not accessible to colourblind people2020-11-15T13:51:37ZakwizgranTransport indicators are not accessible to colourblind peopleThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the transport indicators in the nav drawer rely on colour alone to indicate their state. A second visual cue should be pr...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the transport indicators in the nav drawer rely on colour alone to indicate their state. A second visual cue should be provided for colourblind users.https://code.briarproject.org/briar/briar/-/issues/1786Some buttons lack name/role/value for accessibility2020-11-15T13:52:36ZakwizgranSome buttons lack name/role/value for accessibilityThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) found several examples of buttons that weren't marked with an appropriate name, role and value to enable screen readers to handle them ...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) found several examples of buttons that weren't marked with an appropriate name, role and value to enable screen readers to handle them properly:
- [ ] The `(i)` button for showing information lacks a role (should be "button")
- [ ] The `+` button for adding contacts lacks a name
- [ ] The speed dial buttons for adding contacts lack a role for the text and a name for the icon
- [ ] The buttons in the navigation menu lack a role
- [ ] The transport indicators lack a value
- [ ] In the private group list and possibly elsewhere, the action bar's overflow menu button and the menu items lack roles
- [ ] The button for opening/closing the emoji keyboard lacks a name
- [ ] The "Reply" button (in forums and private groups?) lacks a role
- [ ] When the buttons for scrolling up/down to the previous/next unread message are hidden, they're still visible to screen readers but don't work, and don't have a name, role or value
- [ ] The reblog button has the name "Add a comment" rather than "Reblog"
If any of these are tricky to handle we can create subtasks.https://code.briarproject.org/briar/briar/-/issues/1784Tor settings: Please add a sentence to explain the meaning of 'bridges' to no...2020-11-15T13:53:04ZRobert PollakTor settings: Please add a sentence to explain the meaning of 'bridges' to non-technical usersLike "Connecting via bridges is less prone to surveillance."
Also, what would be an advantage of not using bridges?Like "Connecting via bridges is less prone to surveillance."
Also, what would be an advantage of not using bridges?https://code.briarproject.org/briar/briar/-/issues/1778Onboarding tap target wrongly positioned2021-08-19T11:13:14ZakwizgranOnboarding tap target wrongly positionedThe onboarding tap target for the connections screen is meant to be centered on the Tor icon. On the Samsung Galaxy Ace 2 (Android 4.1.2) it's centered on the top left corner of the nav drawer instead.
I can reproduce this reliably on t...The onboarding tap target for the connections screen is meant to be centered on the Tor icon. On the Samsung Galaxy Ace 2 (Android 4.1.2) it's centered on the top left corner of the nav drawer instead.
I can reproduce this reliably on the device, but it doesn't happen on the emulator running the same API version (16).
![device-2020-09-24-124455](/uploads/4b87fcb4d94c44028ae2fb0cc72dbbb1/device-2020-09-24-124455.png)https://code.briarproject.org/briar/briar-gtk/-/issues/73Redesign contact list2022-01-28T10:54:10ZNicoRedesign contact listInspiration by the GNOME Project:
![mobile-shell-convergence](/uploads/c7c585bd2133b1e37cd70487b7baf6a5/mobile-shell-convergence.png)
Source: https://gitlab.gnome.org/Teams/Design/os-mockups/-/blob/f69fa82f8676582d900af8716522a27ddd77d...Inspiration by the GNOME Project:
![mobile-shell-convergence](/uploads/c7c585bd2133b1e37cd70487b7baf6a5/mobile-shell-convergence.png)
Source: https://gitlab.gnome.org/Teams/Design/os-mockups/-/blob/f69fa82f8676582d900af8716522a27ddd77d87f/mobile-shell/mobile-shell-convergence.pnghttps://code.briarproject.org/briar/briar-gtk/-/issues/69Update delivery state of messages2021-01-23T13:49:02ZNicoUpdate delivery state of messagesBriar Headless still lacks web events of delivery state changes, therefore https://code.briarproject.org/briar/briar-gtk/-/merge_requests/68 doesn't update delivery states automatically.Briar Headless still lacks web events of delivery state changes, therefore https://code.briarproject.org/briar/briar-gtk/-/merge_requests/68 doesn't update delivery states automatically.https://code.briarproject.org/briar/briar/-/issues/1776NPE in exit transition2021-11-04T11:03:23ZakwizgranNPE in exit transition* Android version: 10
* Phone model: Huawei ELE-L29
* Briar version: 1.2.9 (9d96ce6)
Stacktrace:
```
java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.app.Activity.isTopOfTask()' on a null object referenc...* Android version: 10
* Phone model: Huawei ELE-L29
* Briar version: 1.2.9 (9d96ce6)
Stacktrace:
```
java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.app.Activity.isTopOfTask()' on a null object reference
at android.app.ExitTransitionCoordinator.notifyComplete(ExitTransitionCoordinator.java:437)
at android.app.ExitTransitionCoordinator.onReceiveResult(ExitTransitionCoordinator.java:91)
at android.os.ResultReceiver$MyRunnable.run(ResultReceiver.java:50)
at android.os.Handler.handleCallback(Handler.java:900)
at android.os.Handler.dispatchMessage(Handler.java:103)
at android.os.Looper.loop(Looper.java:219)
at android.app.ActivityThread.main(ActivityThread.java:8347)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:513)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1055)
```Android 1.4https://code.briarproject.org/briar/briar-gtk/-/issues/66Automatically start at system boot2020-11-15T14:08:37ZNicoAutomatically start at system bootShould be opt-out.
Currently, I use this:
_~/.config/autostart/briar-gtk.desktop_
```desktop
[Desktop Entry]
Type=Application
Name=briar-gtk
Exec=/usr/bin/flatpak run app.briar.gtk
```Should be opt-out.
Currently, I use this:
_~/.config/autostart/briar-gtk.desktop_
```desktop
[Desktop Entry]
Type=Application
Name=briar-gtk
Exec=/usr/bin/flatpak run app.briar.gtk
```https://code.briarproject.org/briar/briar/-/issues/1774Shreding data when deleting history2020-11-15T14:10:49ZStevanShreding data when deleting historyI'd recommend that when you click delete history on briar chats data gets shreded, if that already is not the case.
This will make data recovery impossible.I'd recommend that when you click delete history on briar chats data gets shreded, if that already is not the case.
This will make data recovery impossible.https://code.briarproject.org/briar/briar-gtk/-/issues/64Make it possible to undo contact deletion2020-11-15T14:12:48ZNicoMake it possible to undo contact deletionWe would then not need to confirm whether the contact should be deleted (#63).We would then not need to confirm whether the contact should be deleted (#63).