Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic refreshes make the page content flicker and reset the scroll position to the top of the page #1828

Closed
cquirosj opened this issue Apr 24, 2024 · 2 comments · Fixed by #1826
Labels
Bug Type: Bug

Comments

@cquirosj
Copy link
Contributor

Describe the bug

Description

When looking at individual messages within the failed messages page, the page flickers, and the scrolled position resets to the top.

Expected behavior

If the page has enough information to be scrollable, the scroll position should not be altered during background refreshes.

Actual behavior

Automatic refreshes makes the page content to flickler and resets scroll position to the top

Versions

1.38.2

Steps to reproduce

Navigate to Failed Messages tab and open a failed message in the headers tab, then scroll the page and wait for 5 seconds

Relevant log output

No response

Additional Information

Workarounds

Possible solutions

Additional information

@cquirosj cquirosj added the Bug Type: Bug label Apr 24, 2024
@cquirosj cquirosj added this to the vNext milestone Apr 24, 2024
@cquirosj cquirosj reopened this Apr 24, 2024
@cquirosj cquirosj changed the title Automatic refreshes makes the page content to flickler and resets scroll position to the top Automatic refreshes makes the page content flicker and reset the scroll position to the top May 1, 2024
@cquirosj cquirosj changed the title Automatic refreshes makes the page content flicker and reset the scroll position to the top Automatic refreshes make the page content flicker and reset the scroll position to the top of the page May 1, 2024
@cquirosj
Copy link
Contributor Author

cquirosj commented May 7, 2024

This is being released as part of ServicePulse version 1.38.3

@cquirosj cquirosj closed this as completed May 7, 2024
@cquirosj
Copy link
Contributor Author

cquirosj commented May 8, 2024

ServicePulse 1.38.3 is now released

@cquirosj cquirosj removed this from the vNext milestone Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Type: Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant