I guess this is a general problem with Virtual DOM architecture which you seem to have adapted for the new UI; my browser’s text search (Ctrl-F thing) doesn’t work with the build log anymore unless the target text is already visible onscreen. This is frustrating when you have 10k lines of log outputs to navigate through for troubleshooting.
Disquss is aware of this problem and activates the in-app text search by intercepting Ctrl-F instead. If I do
Find in this Page via the browser menu bar to circumvent the in-app text search, I have the same problem; my browser can’t find scrolled-out messages.
Sure I can download the log, open a terminal, cd to the
Downloads directory, type the correct file name and then run
less against it. But the whole purpose of the new UI should be improving UX, right…?
I think I have to go back to the traditional UI.