Learn more about these different git repos.
Other Git URLs
I'm starting to use Pagure a little more for some ticket-based uses, and I'm beginning to pick up on some things in the UI that I hadn't before. I should hopefully be adding more easyfix sort of issues to help improve usability.
When writing issues or adding comments to issues or pull request, it's an annoyance to resize the text box – the area for when the cursor appears to resize the box appears dependent on a single point.
For writing out longer issues, comments, or other feedback, it's helpful to resize the text box to the full size of the text. I'm noticing in firefox-48.0-5.fc24, it's not "easy" to resize the text box. You have to align the cursor on a very specific point of the text box. While a very minor, trivial issue, it's annoying and becomes more obvious if you're filing a few tickets or adding comments with a lot of information.
firefox-48.0-5.fc24
If you are talking about this: <img alt="Screenshot_from_2016-08-10_12-31-49.png" src="/pagure/issue/raw/6b6d49754fac96ceb4e12b97cf5a328ecc996d7ed0af36241ee9fb510548b8ee-Screenshot_from_2016-08-10_12-31-49.png" />
I wonder if this isn't entirely something that is handled by the browser, I do not know how much we can do.
I'm pretty sure this is entirely controlled by bootstrap.
Edit: Well, OK, you can style the handle and make it arbitrarily large, but the browser still controls the actually clickable region and as far as I can tell there's no way to change the size of this region. So there might be a browser extension to change this, but I haven't found one.
Pingou, yes -- the resize handle in your screenshot is done by the browser, but that handle does have more than enough of a hit target.
What i think is the issue here is that sometimes, that triangle hit target in your screenshot is not showing up in the bottom right corner. The hit target is still there when it isn't visible, it is just really small and hard to hit.
I think something with the showing and hiding of the markdown preview is causing this, because if you activate the preview for a comment, then deactivate it, the larger hit target shows again.
I think I no longer have the problem, do you?
Looking back, I can't remember how the specific problem looked. Since 5.0 was a heavy UI/UX rework, I'm happy to call this one "fixed" and close it. If I notice it again, I can reopen.
Metadata Update from @wombelix: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.