Please can the admins consider removing the Show the stacktrace button in event logs!
It's totally not needed and is a real pain in the neck having to press this button everytime! It's a completely pointless extra step!
See this screenshot as an example:

We try to look at the reason for doing this step and think it's maybe to safe guard mobile devices from loading a web page with a big height? Either way, it's totally not needed for a developer working on a computer system!
Here's a proposal re-design:

What we have done is basically three things:
Removed Show the stacktrace button in event logs! This is a pointless step and instead just display the full stacktrace (that's why we have clicked on the web page in the first place - from the event log list page).
This removes a flash of unstyled content (FOUC) error that always shows to users! Because October CMS first displays the full stack trace and then switches to this pointless button user experience - we see this everytime, we use the event logs and it's not a nice user experience!
We added a the return to event log button to the top and bottom of the screen - this is to help people on mobile devices having to scroll with their fingers to return to the previous list page! Note we are going to add some basic logic and say if the web page height is bigger than the screen's device size then display the top return to event log button - otherwise don't display it as the bottom return to event log button will be displaying on the webpage! e.g.
Lastly, I now open this issue up for discussion and hopefully other people find the current layout annoying as well.
Feel free to submit a PR that we can review.
This is by design, sorry. For non-technical users they only need to be concerned with the error. It helps when instructing clients to read the logs and it focuses their attention on the right place. We went out of our way to build this button for this reason
@daftspunk would it be ok to have an option in one of the config files, to turn this feature on/off for advanced users?
@ayumi-cloud as a suggestion, you can make a plugin that removes the button and shows the stacktrace by default.
Most helpful comment
This is by design, sorry. For non-technical users they only need to be concerned with the error. It helps when instructing clients to read the logs and it focuses their attention on the right place. We went out of our way to build this button for this reason