briar issueshttps://code.briarproject.org/groups/briar/-/issues2018-06-12T11:32:28Zhttps://code.briarproject.org/briar/briar/-/issues/357Introduction feature is not very visible2018-06-12T11:32:28ZakwizgranIntroduction feature is not very visibleTesters could not easily discover the introduction feature.Testers could not easily discover the introduction feature.Milestone ETorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/356Make it clearer who will be introduced2018-06-12T11:32:28ZakwizgranMake it clearer who will be introducedA tester asked for the ability to cancel an introduction if he had chosen the wrong contacts.A tester asked for the ability to cancel an introduction if he had chosen the wrong contacts.Milestone DTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/355Keyboard closes when private message is sent2018-06-12T11:32:28ZakwizgranKeyboard closes when private message is sentA tester complained that he had to open the keyboard again for each new message.A tester complained that he had to open the keyboard again for each new message.Milestone Cakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/354Layout improvements for private message composition2018-06-12T11:32:28ZakwizgranLayout improvements for private message compositionThe testing report says that the send icon is too big and the text has too little padding.The testing report says that the send icon is too big and the text has too little padding.Milestone Dhttps://code.briarproject.org/briar/briar/-/issues/353Tester expected enter button to send private message2018-06-12T11:32:28ZakwizgranTester expected enter button to send private messageA tester tried to send a private message via the enter button and wondered why it didn't send. The message was no longer visible because the text entry was limited to a single line and pressing enter had created a new line.
Investigat...A tester tried to send a private message via the enter button and wondered why it didn't send. The message was no longer visible because the text entry was limited to a single line and pressing enter had created a new line.
Investigate how other messaging apps handle this. Does enter send the message, or do they start a new line and expand the text entry?https://code.briarproject.org/briar/briar/-/issues/350Contact list still showed unread message after message had been read2018-06-12T11:32:29ZakwizgranContact list still showed unread message after message had been readA tester got an unread message notification, switched directly to the converstion, read the message, switched to the contact screen, and there was still an unread message indicator next to the contact's name.
This may be a race condit...A tester got an unread message notification, switched directly to the converstion, read the message, switched to the contact screen, and there was still an unread message indicator next to the contact's name.
This may be a race condition between messages being marked as read and the contact list loading the message headers.Milestone ETorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/347Show progress indicator while loading QR code2018-06-12T11:32:29ZakwizgranShow progress indicator while loading QR codehttps://code.briarproject.org/briar/briar/-/issues/345Identity selector when adding contacts is confusing2018-06-12T11:32:29ZakwizgranIdentity selector when adding contacts is confusingTesters found the identity selector confusing when adding contacts.Testers found the identity selector confusing when adding contacts.Milestone DTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/344Tester could not find contact screen2018-06-12T11:32:29ZakwizgranTester could not find contact screenA tester could not find the contact screen when he was already there. The contact list was empty, but the "No contacts" empty state message should have been visible, and the window title should have been "Contacts". I'm not sure what we ...A tester could not find the contact screen when he was already there. The contact list was empty, but the "No contacts" empty state message should have been visible, and the window title should have been "Contacts". I'm not sure what we can do to make this clearer.
Related to #327.Milestone Dhttps://code.briarproject.org/briar/briar/-/issues/343Explain why password is too weak2018-06-11T10:15:17ZakwizgranExplain why password is too weakTesters wanted to know the minimum requirements for passwords. If the user's password is too weak, explain why.
We could solve this by showing "password is too short" if it's below a minimum length, "password is too common" if it's on...Testers wanted to know the minimum requirements for passwords. If the user's password is too weak, explain why.
We could solve this by showing "password is too short" if it's below a minimum length, "password is too common" if it's on a blacklist of common passwords, or "password is too simple" if it's neither too short nor too common but the strength estimate is low due to insufficient variety of characters.https://code.briarproject.org/briar/briar/-/issues/342Organise strings.xml to make life easier for translators2018-01-28T11:30:28ZakwizgranOrganise strings.xml to make life easier for translatorsGroup the strings according to where they appear in the app so that translators can see the context in which each string is used. We'll also need a section for strings that appear in multiple places, such as dialog button labels.
Subt...Group the strings according to where they appear in the app so that translators can see the context in which each string is used. We'll also need a section for strings that appear in multiple places, such as dialog button labels.
Subtask of #341.Milestone DTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/341Co-ordinate initial translations2018-06-12T11:32:29ZakwizgranCo-ordinate initial translationsMilestone Dhttps://code.briarproject.org/briar/briar/-/issues/340Progress wheels have transparent backgrounds2018-06-12T11:32:29ZakwizgranProgress wheels have transparent backgroundsViews containing progress wheels, which are supposed to have opaque backgrounds filling the screen, instead have transparent backgrounds. Possibly caused by recent changes to unify the background colour.
![device-2016-05-03-182935](/u...Views containing progress wheels, which are supposed to have opaque backgrounds filling the screen, instead have transparent backgrounds. Possibly caused by recent changes to unify the background colour.
![device-2016-05-03-182935](/uploads/17731df75bf5650e7e20813997d5c2c0/device-2016-05-03-182935.png)
![device-2016-05-03-182952](/uploads/1287fc090a9f8cc81e218ff6c6c3b315/device-2016-05-03-182952.png)
Milestone Cakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/339Forum Sharing Integration Tests2018-06-12T11:32:29ZTorsten GroteForum Sharing Integration TestsMilestone CTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/337Avatar Placeholders for Forums2018-06-12T11:32:29ZTorsten GroteAvatar Placeholders for ForumsTo make forums visually more pleasing, they should have avatars that use the first letter of their name and a deterministically chosen color as a background. Here's a mockup:
![avatars](https://code.briarproject.org/akwizgran/briar/up...To make forums visually more pleasing, they should have avatars that use the first letter of their name and a deterministically chosen color as a background. Here's a mockup:
![avatars](https://code.briarproject.org/akwizgran/briar/uploads/7c7eb7eb7029c015bc2ed48a1115073c/forums_list_with_Circles.jpg)
Tthis works better with unsaturated colors. I would suggest saturation < 50%. For the identicons we pick random red, green and blue values in the bottom 3/4 of the range, which ensures the colours are somewhat desturated and dark enough to contrast with a light background.Milestone CTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/336Remove TestingActivity2018-06-12T11:32:29ZakwizgranRemove TestingActivityThis has been replaced by the new feedback reporter.This has been replaced by the new feedback reporter.Milestone Cakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/335UX improvements for crash reports and feedback2018-06-12T11:32:29ZakwizgranUX improvements for crash reports and feedbackIssues to consider:
* Crash report activity appears before accepting the dialog
* Button text for dialog?
* Send icon instead of share icon?
* FAB floats in wrong position when keyboard is open on small screens
* Are crash report ...Issues to consider:
* Crash report activity appears before accepting the dialog
* Button text for dialog?
* Send icon instead of share icon?
* FAB floats in wrong position when keyboard is open on small screens
* Are crash report settings needed?
* Feedback activity uses transitions for separate task
Milestone Chttps://code.briarproject.org/briar/briar/-/issues/334Navigation menu causes crash with support library 23.3.02018-06-12T11:32:29ZakwizgranNavigation menu causes crash with support library 23.3.0After "upgrading" the support library to 23.3.0, clicking any button in the navigation drawer causes a crash with the following stacktrace:
```
java.lang.IllegalStateException: Could not find a method onNavigationClick(View) in the a...After "upgrading" the support library to 23.3.0, clicking any button in the navigation drawer causes a crash with the following stacktrace:
```
java.lang.IllegalStateException: Could not find a method onNavigationClick(View) in the activity class android.support.v7.widget.TintContextWrapper for onClick handler on view class android.support.v7.widget.AppCompatButton with id 'nav_btn_contacts'
at android.view.View$1.onClick(View.java:4012)
at android.view.View.performClick(View.java:4785)
at android.view.View$PerformClick.run(View.java:19884)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5343)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:905)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:700)
Caused by: java.lang.NoSuchMethodException: onNavigationClick [class android.view.View]
at java.lang.Class.getMethod(Class.java:664)
at java.lang.Class.getMethod(Class.java:643)
at android.view.View$1.onClick(View.java:4005)
at android.view.View.performClick(View.java:4785)
at android.view.View$PerformClick.run(View.java:19884)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5343)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:905)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:700)
```Milestone Dhttps://code.briarproject.org/briar/briar/-/issues/333Font color2018-06-12T11:32:29ZMegaloxFont colorWe have to define system wide font colorsWe have to define system wide font colorsMilestone DTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/332Looper error in SplashScreenActivity on 5.0.1 with support library 23.2.12018-06-12T11:32:29Zstr4dLooper error in SplashScreenActivity on 5.0.1 with support library 23.2.1```
org.briarproject E/ACRA: ACRA caught a InflateException for org.briarproject
android.view.InflateException: Binary XML file line #2: Error inflating class PreferenceScreen
at android.support.v7.preference.PreferenceInflater.cr...```
org.briarproject E/ACRA: ACRA caught a InflateException for org.briarproject
android.view.InflateException: Binary XML file line #2: Error inflating class PreferenceScreen
at android.support.v7.preference.PreferenceInflater.createItem(PreferenceInflater.java:262)
at android.support.v7.preference.PreferenceInflater.onCreateItem(PreferenceInflater.java:281)
at android.support.v7.preference.PreferenceInflater.createItemFromTag(PreferenceInflater.java:290)
at android.support.v7.preference.PreferenceInflater.inflate(PreferenceInflater.java:161)
at android.support.v7.preference.PreferenceInflater.inflate(PreferenceInflater.java:117)
at android.support.v7.preference.PreferenceManager.inflateFromResource(PreferenceManager.java:115)
at android.support.v7.preference.PreferenceManager.setDefaultValues(PreferenceManager.java:328)
at android.support.v7.preference.PreferenceManager.setDefaultValues(PreferenceManager.java:287)
at org.briarproject.android.SplashScreenActivity$2.run(SplashScreenActivity.java:93)
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Constructor.newInstance(Native Method)
at java.lang.reflect.Constructor.newInstance(Constructor.java:288)
at android.support.v7.preference.PreferenceInflater.createItem(PreferenceInflater.java:256)
at android.support.v7.preference.PreferenceInflater.onCreateItem(PreferenceInflater.java:281)
at android.support.v7.preference.PreferenceInflater.createItemFromTag(PreferenceInflater.java:290)
at android.support.v7.preference.PreferenceInflater.inflate(PreferenceInflater.java:161)
at android.support.v7.preference.PreferenceInflater.inflate(PreferenceInflater.java:117)
at android.support.v7.preference.PreferenceManager.inflateFromResource(PreferenceManager.java:115)
at android.support.v7.preference.PreferenceManager.setDefaultValues(PreferenceManager.java:328)
at android.support.v7.preference.PreferenceManager.setDefaultValues(PreferenceManager.java:287)
at org.briarproject.android.SplashScreenActivity$2.run(SplashScreenActivity.java:93)
Caused by: java.lang.RuntimeException: Can't create handler inside thread that has not called Looper.prepare()
at android.os.Handler.<init>(Handler.java:200)
at android.os.Handler.<init>(Handler.java:114)
at android.support.v7.preference.PreferenceGroup.<init>(PreferenceGroup.java:61)
at android.support.v7.preference.PreferenceGroup.<init>(PreferenceGroup.java:87)
at android.support.v7.preference.PreferenceScreen.<init>(PreferenceScreen.java:84)
at java.lang.reflect.Constructor.newInstance(Native Method)
at java.lang.reflect.Constructor.newInstance(Constructor.java:288)
at android.support.v7.preference.PreferenceInflater.createItem(PreferenceInflater.java:256)
at android.support.v7.preference.PreferenceInflater.onCreateItem(PreferenceInflater.java:281)
at android.support.v7.preference.PreferenceInflater.createItemFromTag(PreferenceInflater.java:290)
at android.support.v7.preference.PreferenceInflater.inflate(PreferenceInflater.java:161)
at android.support.v7.preference.PreferenceInflater.inflate(PreferenceInflater.java:117)
at android.support.v7.preference.PreferenceManager.inflateFromResource(PreferenceManager.java:115)
at android.support.v7.preference.PreferenceManager.setDefaultValues(PreferenceManager.java:328)
at android.support.v7.preference.PreferenceManager.setDefaultValues(PreferenceManager.java:287)
at org.briarproject.android.SplashScreenActivity$2.run(SplashScreenActivity.java:93)
```
Reverting to 23.1.1 stops the error.Milestone Cakwizgranakwizgran