Autoscrolling is broken since 119.0
Hi, I am seeing issues with autoscrolling in 119.0. In Rundeck for example you can "follow" the output of playbooks that are running so you can dynamically see the log as it is written. The autoscrolling in this field has stopped working. When manually scrolling in the field, more messages appear but the autoscrolling is no longer functional. I have also seen it on other places, though I don't have remember good examples to add, so I don't believe it is Rundeck causing the issue--we also haven't updated rundeck recently in our environment, so it shouldn't have changed since before 119.0 was released. Let me know if there is more information I can provide to diagnose the issue.
Vybrané riešenie
You can check the Web Console and the Network Monitor (Tools -> Web Developer) for messages about blocked content or content that fails to load.
- https://firefox-source-docs.mozilla.org/devtools-user/web_console/
- https://firefox-source-docs.mozilla.org/devtools-user/network_monitor/
If necessary use "Ctrl+F5" or "Ctrl+Shift+R" (Mac: Command+Shift+R) to reload the page and bypass the cache to generate a fresh log.
Čítať túto odpoveď v kontexte 👍 0Všetky odpovede (7)
Does it still happen in Troubleshoot Mode?
You can test older versions with mozregression to find the change responsible.
zeroknight said
Does it still happen in Troubleshoot Mode? You can test older versions with mozregression to find the change responsible.
I still need to try the mozregression to find the change but it is indeed broken in Troubleshoot mode as well.
Does it still happen in a new profile? An easy way to test a new profile is to install Developer Edition and see if it happens there or refresh your existing profile.
I have tested builds dating back to 114 with mozregression and I still see the issue, I think maybe it is a consequence of my organization blocking firefox password management. I wouldn't think that would be related but otherwise it doesn't make sense why it is failed in all these previous builds where I'm sure it was working before. :-(
Upravil(a) mattdanielsdba dňa
Vybrané riešenie
You can check the Web Console and the Network Monitor (Tools -> Web Developer) for messages about blocked content or content that fails to load.
- https://firefox-source-docs.mozilla.org/devtools-user/web_console/
- https://firefox-source-docs.mozilla.org/devtools-user/network_monitor/
If necessary use "Ctrl+F5" or "Ctrl+Shift+R" (Mac: Command+Shift+R) to reload the page and bypass the cache to generate a fresh log.
I checked in Chrome and it also was not working there, in web developer console I can see a 404 for execution-show.css returned when I try to follow the output, which I think is the cause of the issue. I still need to figure out what is misconfigured on the Rundeck side but it isn't a Firefox issue.
Ak chcete odpovedať na príspevky, musíte sa prihlásiť do svojho účtu. Ak ešte nemáte účet, položte novú otázku.