Describe the bug
when reading messages in a channel and clicking on a message* to view the message details the top of the details text doesnt dissapear 'hitting' the top buttons (back/reply/del ) when scrolling down but stays visible underneath those buttons.
*off course this only shows with messages that have enough hops to get a scrollable amount of text..
Which device are you using
LilyGO T-Deck
Which Firmware are you using
0.97 To Reproduce
Steps to reproduce the behavior:
Go to 'MSGS'
Click on 'CHANNEL....'
cLICK A MESSAGE
Scroll down to '....'
look at text in the top of the screen
not a real bug, just nitpicking..
**Describe the bug**
when reading messages in a channel and clicking on a message* to view the message details the top of the details text doesnt dissapear 'hitting' the top buttons (back/reply/del ) when scrolling down but stays visible underneath those buttons.
*off course this only shows with messages that have enough hops to get a scrollable amount of text..
**Which device are you using**
LilyGO T-Deck
**Which Firmware are you using**
0.97
**To Reproduce**
Steps to reproduce the behavior:
1. Go to 'MSGS'
2. Click on 'CHANNEL....'
3. cLICK A MESSAGE
5. Scroll down to '....'
6. look at text in the top of the screen
not a real bug, just nitpicking..
<!-- github-sync-id:3898037118 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Describe the bug
when reading messages in a channel and clicking on a message* to view the message details the top of the details text doesnt dissapear 'hitting' the top buttons (back/reply/del ) when scrolling down but stays visible underneath those buttons.
*off course this only shows with messages that have enough hops to get a scrollable amount of text..
Which device are you using
LilyGO T-Deck
Which Firmware are you using
0.97
To Reproduce
Steps to reproduce the behavior:
not a real bug, just nitpicking..
fixed in v0.9.8!
can anyone confirm that this bug is fixed in the v0.9.8 prerelease?
yes, it's fixed!