Framework: Unnecessary sroll down after refreshRowCache() in Table with Chrome 56+ browser

Created on 28 Feb 2017  路  9Comments  路  Source: vaadin/framework

Vaadin version 7.7.7
Browser version Chrome 56 and newer.

How to reproduce

  1. Create UI with Table which contains 1000 rows
  2. Open it with Chrome 56+ browser or other browser with chrome 56+ engine.
  3. Scroll down, so Table requests next page(for example scroll down to item 100).
  4. Click 'refresh' button to make table.refreshRowCache()
  5. As you can see, table scrolls down without any user action after table.refreshRowCache() is done.
  6. You can not reproduce such behaviour with other non-chrome engine browser(IE, Firefox, etc).

Working example http://178.236.245.251:8383/tabletest/
Source code:
vaadin-app.zip

Stale

Most helpful comment

We had a similar problem with Table. It was caused by Chrome's "scroll anchoring" feature, which is enabled by default since Chrome 56. We solved it by adding the following rule to our CSS:

.v-table, .v-table * { overflow-anchor: none; }

All 9 comments

I'm also seeing this on Vaadin 6.x and Vaadin 7.x

Struggling to make sense of their issue tracking but it looks like maybe
https://bugs.chromium.org/p/chromium/issues/detail?id=687061

can someone from vaadin team investigate this issue?
I forced my users to use firefox.

Having this problem with Vaadin 6.8.15 and 8.0.6 on Chromium 58.0.3029.110
Both versions look good on Firefox 53.0.3

Struggling to make sense of their issue tracking but it looks like maybe
https://bugs.chromium.org/p/chromium/issues/detail?id=687061

The bug @rubberony found seems to have been fixed in the latest Chrome (but the bug still persists for me). I'd rather not have to make my users switch their preferred browser.

We had a similar problem with Table. It was caused by Chrome's "scroll anchoring" feature, which is enabled by default since Chrome 56. We solved it by adding the following rule to our CSS:

.v-table, .v-table * { overflow-anchor: none; }

@gWestenberger Nice one! This appears to work. I did find find a chrome issue that explains this. Sorry about the previous one guys.
https://bugs.chromium.org/p/chromium/issues/detail?id=594886

@gWestenberger We can not express how we happy about this! Thank you very much!

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

  • Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
  • Provide more details how to reproduce the issue.
  • Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
  • Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
  • Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
  • If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!

Was this page helpful?
0 / 5 - 0 ratings