Replies: 2 comments
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
ARC (Actions Runner Controller)EDIT: I forgot to change this from the default. I think "Other" is the correct feature/topic area. I don't think I can remove the "ARC (Actions Runner Controller)" tag that was added.Other
Discussion Details
Until a few weeks ago, when viewing the log from a failed job, after the page automatically scrolls to the bottom, I could easily get back to the top in less than a second with cmd+up (on mac os).
Now, that scrolls up a few hundred log lines and then stops, and pressing it again scrolls up a few more hundred lines.
Scrolling up with a touchpad gesture or shift+space is similarly affected.
Workaround:
If I hold down cmd+up I eventually get to the top, but it's not ideal.
If reverting whatever changed this isn't an option, I wonder if the new problem is related to the variable amount of vertical distance used by log lines that wrap. I wonder if no longer wrapping would fix this. But viewing with wrap on is often useful too, so that still wouldn't be ideal.
All reactions