Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Learn More

Autoscrolling is broken since 119.0

  • 7 trả lời
  • 0 gặp vấn đề này
  • 15 lượt xem
  • Trả lời mới nhất được viết bởi mattdanielsdba

more options

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.

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.

Giải pháp được chọn

You can check the Web Console and the Network Monitor (Tools -> Web Developer) for messages about blocked content or content that fails to load.

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.

Đọc câu trả lời này trong ngữ cảnh 👍 0

Tất cả các câu trả lời (7)

more options

Does it still happen in Troubleshoot Mode?

You can test older versions with mozregression to find the change responsible.

Hữu ích?

more options

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.

Hữu ích?

more options

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.

Hữu ích?

more options

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. :-(

Được chỉnh sửa bởi mattdanielsdba vào

Hữu ích?

more options

Does the autoscrolling work on other browsers?

Hữu ích?

more options

Giải pháp được chọn

You can check the Web Console and the Network Monitor (Tools -> Web Developer) for messages about blocked content or content that fails to load.

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.

Hữu ích?

more options

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.

Hữu ích?

Đặt một câu hỏi

Bạn phải đăng nhập vào tài khoản của bạn để trả lời bài viết. Vui lòng bắt đầu một câu hỏi mới, nếu bạn chưa có tài khoản.