Scrolling causes ### to appear in cells that displayed contents before scrolling

[WoozyG]

I've only seen this when scrolling sideways, but have at least one user who can reproduce it scrolling vertically as well.

Upload the attached sample to https://demo.vaadin.com/spreadsheet/. It just contains a block of random number formulas and a couple of graphs.

Note that all columns are sized to properly accommodate the numbers.

Scroll right, then scroll back, however, in the latest Chrome, Firefox, and IE11, and some of the number cells now display "###" instead. Clicking on column dividers, without resizing the columns, displays the proper values again. ChartSamples.xlsx

IE11

[lucailmartini]

Hi @WoozyG , are you experiencing this also on the latest version? I'm asking because we believed that the problem was solved with #548 (ported on 2.x branch with #556) but we are still facing this problem randomly. However it is difficult to reproduce.

[WoozyG]

I'm using a custom build of 2.0 master, and haven't noticed this lately. There are formatting elements (mostly borders) that don't reappear properly when scrolling, however.

Changes in my production build are minor, some bug fixes from master that haven't been released yet in 2.x branch.

I also override many classes to add functionality and fix other issues, though, so my environment is not very clean for now. In a couple months I'll be able to work more on patches to port my customizations and bring my build closer to stock. Most of them are to support parsing more Excel formatting attributes, especially for charts and fonts, and add a JS library to handle chart axis and series label formatting based on Excel format strings. Some of that may impact the behavior of this bug.

[lucailmartini]

I have to rectify what I said in my previous comment. We are not able to replicate the problem with versions that include #548 . Yesterday I was using (by mistake) an old version of the spreadsheet. I am fairly positive that this problem is now solved (looking at the correction I do not think that your custom modification might impact that area). Maybe it could be reasonable to close this as duplicate and reopen if necessary. Best, Luca