Impossible to navigate in issue comments while writing one #750

Open
opened 2 years ago by KaKi87 · 2 comments
KaKi87 commented 2 years ago

When writing a comment, the user should be able to re-read and eventually copy/paste text from the previous comments without having to close the commenting modal and loosing the text.

Please see OctoDroid for GitHub to experience the expected behavior.

Thanks

When writing a comment, the user should be able to re-read and eventually copy/paste text from the previous comments without having to close the commenting modal and loosing the text. Please see OctoDroid for GitHub to experience the expected behavior. Thanks
mmarif added the
🎯 Enhancement
label 2 years ago
Collaborator

without having to close the commenting modal and loosing the text

Hi, you're not loosing the text. It will be saved in 'Drafts' and you can always get it back from there, but i get your point.

It would be helpful though if you're not referencing to OctoDroid, as this won't help most of us (e.g. those, who don't use OctoDroid) much. It costs too much time to install and test an app just for implementing a feature. Tell us precisely how you want the feature to "look and feel" and attach screenshots. If you're doing it this way, your feature may be implemented much faster.

> without having to close the commenting modal and loosing the text Hi, you're not loosing the text. It will be saved in 'Drafts' and you can always get it back from there, but i get your point. It would be helpful though if you're not referencing to OctoDroid, as this won't help most of us (e.g. those, who don't use OctoDroid) much. It costs too much time to install and test an app just for implementing a feature. Tell us precisely how you want the feature to "look and feel" and attach screenshots. If you're doing it this way, your feature may be implemented much faster.
opyale added the
📡 Needs-feedback
label 2 years ago
Poster

It would be helpful though if you’re not referencing to OctoDroid, as this won’t help most of us (e.g. those, who don’t use OctoDroid) much.

Really ?

  • Here, we're using GitNex.
  • Which means, we're using Android.
  • Which also means, we're using Gitea.
  • But, Gitea is hosted on GitHub.
  • So, wouldn't we be using GitHub on Android too ?

I'm using OctoDroid as an example for GitNex just as GitHub is used as an example for Gitea.

But, here's a screenshot anyway.

> It would be helpful though if you’re not referencing to OctoDroid, as this won’t help most of us (e.g. those, who don’t use OctoDroid) much. Really ? - Here, we're using GitNex. - Which means, we're using Android. - Which also means, we're using Gitea. - But, Gitea is hosted on GitHub. - So, wouldn't we be using GitHub on Android too ? I'm using OctoDroid as an example for GitNex just as GitHub is used as an example for Gitea. But, here's a screenshot anyway. ![](https://codeberg.org/attachments/3b0bf091-bcd6-42c8-b071-9f212ccede9d)
6543 removed the
📡 Needs-feedback
label 2 years ago
qwerty287 changed title from [Issue] Impossible to navigate in comments while writing one to Impossible to navigate in issue comments while writing one 7 months ago
qwerty287 added the
💻 UI/UX
label 7 months ago
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: gitnex/GitNex#750
Loading…
There is no content yet.