briar issueshttps://code.briarproject.org/groups/briar/-/issues2017-12-18T07:40:23Zhttps://code.briarproject.org/briar/briar/-/issues/881ForumActivityTest fails due to custom toolbar2017-12-18T07:40:23ZakwizgranForumActivityTest fails due to custom toolbar```
java.lang.IllegalStateException: This Activity already has an action bar supplied by the window decor. Do not request Window.FEATURE_SUPPORT_ACTION_BAR and set windowActionBar to false in your theme to use a Toolbar instead.
at and...```
java.lang.IllegalStateException: This Activity already has an action bar supplied by the window decor. Do not request Window.FEATURE_SUPPORT_ACTION_BAR and set windowActionBar to false in your theme to use a Toolbar instead.
at android.support.v7.app.AppCompatDelegateImplV7.setSupportActionBar(AppCompatDelegateImplV7.java:197)
at android.support.v7.app.AppCompatActivity.setSupportActionBar(AppCompatActivity.java:129)
at org.briarproject.briar.android.activity.BriarActivity.setUpCustomToolbar(BriarActivity.java:109)
at org.briarproject.briar.android.forum.ForumActivity.onCreate(ForumActivity.java:66)
at android.app.Activity.performCreate(Activity.java:5933)
at org.robolectric.util.ReflectionHelpers.callInstanceMethod(ReflectionHelpers.java:195)
at org.robolectric.util.ActivityController$1.run(ActivityController.java:122)
at org.robolectric.shadows.ShadowLooper.runPaused(ShadowLooper.java:304)
at org.robolectric.shadows.CoreShadowsAdapter$2.runPaused(CoreShadowsAdapter.java:45)
at org.robolectric.util.ActivityController.create(ActivityController.java:118)
at org.robolectric.util.ActivityController.create(ActivityController.java:129)
at org.briarproject.briar.android.forum.ForumActivityTest.setUp(ForumActivityTest.java:93)
```Milestone FTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/879Implement Threaded Unread Handling2017-12-18T07:40:23ZTorsten GroteImplement Threaded Unread HandlingBased on the feature specification from #478, this ticket is for the actual implementation of this feature.
![mockup](https://code.briarproject.org/akwizgran/briar/uploads/89ad16273315aa10922a222c2ba090f3/forum_01_up_and_down.jpg)
...Based on the feature specification from #478, this ticket is for the actual implementation of this feature.
![mockup](https://code.briarproject.org/akwizgran/briar/uploads/89ad16273315aa10922a222c2ba090f3/forum_01_up_and_down.jpg)
When the user scrolls the forum list, visible unread entries will be marked read after playing their animation. The unread counters on the two floating buttons are updated accordingly. If the user presses the floating button, the list scrolls to the nearest unread message in that direction which plays its animation. While the list scrolls, no messages that are passed will be marked as read.
When a new message arrives, the counters are updated accordingly when the new message is not visible in the current viewport. If it is visible, its animation plays and it is marked as read. If the message arrives in a closed thread, the root message has an unread counter signaling the availability of unread messages in that thread.
If there are no more unread messages in one direction, the respective floating button will be hidden.
When the user opens the forum next time, the list should scroll to the most recently read message (easy to implement via MessageTracker). It's a good compromise between taking the user somewhere familiar, and taking her to the latest content. But scrolling to the first unread message, as we've discussed previously, would also be reasonable.Milestone FTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/877Save invitation outcome to invitation message and make available to UI2017-12-18T07:40:23ZTorsten GroteSave invitation outcome to invitation message and make available to UIThe shareable of an invitation can only be opened when an invitation was accepted and we still subscribe to the shareable.
To be able to set `canBeOpened` to a proper value, the user's response needs to be recorded in the invitation's m...The shareable of an invitation can only be opened when an invitation was accepted and we still subscribe to the shareable.
To be able to set `canBeOpened` to a proper value, the user's response needs to be recorded in the invitation's metadata.
For the group invitation protocol the response could be stored in `InviteeProtocolEngine#onLocalAccept()` at the same time as marking the invitation unavailable to answer, then retrieved in `GroupManagerImpl#parseInvitationRequest()`.Milestone FTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/876Group Invitation not marked unavailable2017-12-18T07:40:23ZTorsten GroteGroup Invitation not marked unavailableInviteeProtocolEngine: the invitation isn't marked unavailable if the creator dissolves the group while the invitee's in the INVITED state.InviteeProtocolEngine: the invitation isn't marked unavailable if the creator dissolves the group while the invitee's in the INVITED state.Milestone FTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/875Sharing state doesn't update while sharing status or memberlists are open2019-02-28T13:27:49ZMegaloxSharing state doesn't update while sharing status or memberlists are openIt updated when we closed and reopened the screen again.
* [X] Update membership/sharing state
* [ ] Update member's online stateIt updated when we closed and reopened the screen again.
* [X] Update membership/sharing state
* [ ] Update member's online stateAndroid 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/874Forums: Make tree indicator more visible2017-12-18T07:40:24ZMegaloxForums: Make tree indicator more visibleThe testers noticed that the tree indicator isn't visible enough.
I suggest we make the grey of the lines, the number and the outline of the circle at least 30% darker.The testers noticed that the tree indicator isn't visible enough.
I suggest we make the grey of the lines, the number and the outline of the circle at least 30% darker.Android Beta 1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/871RSS feed lost2017-08-04T13:52:53ZMegaloxRSS feed lostOur testers imported a regulary updated RSS feed on Friday. We opened the blogs again on monday and no new posts of the RSS feed had arrived.Our testers imported a regulary updated RSS feed on Friday. We opened the blogs again on monday and no new posts of the RSS feed had arrived.Android Beta 2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/870Blog Posts Sometimes Not Shown in the UI2021-05-05T16:13:19ZMegaloxBlog Posts Sometimes Not Shown in the UISometimes posts don't get displayed at all (there should be a single blog post in the gap):
![Blogs_missing_post](/uploads/85b793cfd26ee88984e406cd4e25cb0e/Blogs_missing_post.png)Sometimes posts don't get displayed at all (there should be a single blog post in the gap):
![Blogs_missing_post](/uploads/85b793cfd26ee88984e406cd4e25cb0e/Blogs_missing_post.png)https://code.briarproject.org/briar/briar/-/issues/869UI Bug after deleting a private group2019-02-27T11:36:18ZMegaloxUI Bug after deleting a private group![UI_bug_in_private_groups_Screenshot_2016-12-16-10-54-45](/uploads/4abaade452eb0a79a93faacec39054a6/UI_bug_in_private_groups_Screenshot_2016-12-16-10-54-45.png)![UI_bug_in_private_groups_Screenshot_2016-12-16-10-54-45](/uploads/4abaade452eb0a79a93faacec39054a6/UI_bug_in_private_groups_Screenshot_2016-12-16-10-54-45.png)Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/868Add contact: "Face-to-face" is confusing2017-12-18T07:40:24ZMegaloxAdd contact: "Face-to-face" is confusingWe discussed this somewhere before (couldn't find this at the moment) but one tester thought he had to take a picture of his contact when he read something about "face-to-face"We discussed this somewhere before (couldn't find this at the moment) but one tester thought he had to take a picture of his contact when he read something about "face-to-face"https://code.briarproject.org/briar/briar/-/issues/867RSS feed: Posts from the RSS feed stayed in the blog after deleting the RSS feed2017-12-18T07:40:24ZMegaloxRSS feed: Posts from the RSS feed stayed in the blog after deleting the RSS feedThe testers had no problem deleting an RSS feed, but they expected the posts from the RSS feed to disappear.The testers had no problem deleting an RSS feed, but they expected the posts from the RSS feed to disappear.Android Beta 1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/866RSS feed: Tester B did not like the "spamming" of his feed after A imported a...2017-12-18T07:40:24ZMegaloxRSS feed: Tester B did not like the "spamming" of his feed after A imported an RSS feedThe testers had no problem to import RSS feeds. But when A imported a feed B got 28 notifications for new blog entries (we stopped counting after 28). He didn't like this at all.The testers had no problem to import RSS feeds. But when A imported a feed B got 28 notifications for new blog entries (we stopped counting after 28). He didn't like this at all.Android Beta 1https://code.briarproject.org/briar/briar/-/issues/863Blog: Single view has no up-arrow in the appbar2018-06-11T10:53:26ZMegaloxBlog: Single view has no up-arrow in the appbarTesters could not go back to the blog without going to another top level navdrawer destination and back.Testers could not go back to the blog without going to another top level navdrawer destination and back.https://code.briarproject.org/briar/briar/-/issues/861No verification icons in contact list2018-06-11T11:06:30ZMegaloxNo verification icons in contact listThere are no verification icons in the contact list. Is this intentional?There are no verification icons in the contact list. Is this intentional?https://code.briarproject.org/briar/briar/-/issues/860Spelling mistake2017-12-18T07:40:24ZMegaloxSpelling mistakeWe noticed a spelling mistake in the german localisation. Did anyone check this?We noticed a spelling mistake in the german localisation. Did anyone check this?https://code.briarproject.org/briar/briar/-/issues/857Introduction: No notification for contact established confirmation.2018-04-28T00:15:25ZMegaloxIntroduction: No notification for contact established confirmation.A introducted B to C. B accepted. Then C accepted. B did not receive a notification that C is now her contact.A introducted B to C. B accepted. Then C accepted. B did not receive a notification that C is now her contact.Android 1.0Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/855Reveal relationship: testers did not understand concept2017-12-18T07:40:24ZMegaloxReveal relationship: testers did not understand conceptThe first thing the testers saw was the visibility indicator in the group. They didn't understand what that meant at all.
Then we told them to go to the "reveal contact" section. The onboarding dialog was displayed but they did not und...The first thing the testers saw was the visibility indicator in the group. They didn't understand what that meant at all.
Then we told them to go to the "reveal contact" section. The onboarding dialog was displayed but they did not understand what it meant.
The creator of the group saw in her "reveal contact" menu that she had one person that was checked and greyed out. She did not know why that was or what it meant.
<br/>
To put it in a nutshell: This wont work in any way without a very good explanation. If we presume that users don't read manuals at all we can kick the whole feature because it will only confuse the users.https://code.briarproject.org/briar/briar/-/issues/853Disabled menu items are not greyed out on all devices2017-12-18T07:40:24ZMegaloxDisabled menu items are not greyed out on all devicesIf the user has only one contact she can't make an introduction. Nonetheless the "Make introduction" button in the overflow menu is visble. It just doesn't do anything if the user taps it.If the user has only one contact she can't make an introduction. Nonetheless the "Make introduction" button in the overflow menu is visble. It just doesn't do anything if the user taps it.Android Beta 1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/852More room for private group titles by hiding more icons behind the overflow2018-06-11T10:47:18ZMegaloxMore room for private group titles by hiding more icons behind the overflow![Screenshot_20161214-110339](/uploads/9060cc7f36edff23221cbc9f0a339cc8/Screenshot_20161214-110339.png)
The member list icon can be hidden behind the overflow. The compose icon should always be visible.![Screenshot_20161214-110339](/uploads/9060cc7f36edff23221cbc9f0a339cc8/Screenshot_20161214-110339.png)
The member list icon can be hidden behind the overflow. The compose icon should always be visible.https://code.briarproject.org/briar/briar/-/issues/851The refresher in BriarRecyclerView is leaking memory2017-12-18T07:40:24ZErnir ErlingssonThe refresher in BriarRecyclerView is leaking memoryThis is a sub-ticket of #839This is a sub-ticket of #839Milestone F