Grid editor misalignment when opened by double-clicking a cell partially in view

vaadin-bot commented 9 years ago

Originally by @Ansku

Steps to reproduce:

Open GridEditorFrozenColumnsUI (you may set frozen column count to 0 as this is not related to those, you just need an editable Grid with a horizontal scrollbar)
Double-click the last partially visible column
Cancel the editing
Move the scrollbar enough to get the next column partially visible
Double-click the new partially visible cell of the same row that you edited in step 2 -> cells in editor will shift so that even the next column is visible, while the rest of the Grid will only shift enough to make the clicked column visible -> misalignment

The area with save and cancel button will shift also, but stay in same position in relation to the editor cells that they would be if the editor cells weren't shifted too much -> the whole area ends up too far left (with some Grid contents to the point of not being visible at all), and there's no background colour on the leftover bit which leaves the Grid row underneath to show through.

If you scroll the grid to the point where the editor and main Grid are again in alignment, editor contents will stay where they are supposed to say for any further scrolling from there on -- until you repeat the original steps again.

This far I have only been able to reproduce this when scrolling to right, double-clicking partially visible cells on the left edge and scrolling a bit more left from there to double-click again doesn't seem to have the same results.

Tested with Chrome 43 on Windows 7, in branches 7.5 and master, and also in a separate project with 7.5.2.

IE11 in master branch already has misalignment with first double-click, and I couldn't reproduce this at all on brief testing with Firefox 39.

Imported from https://dev.vaadin.com/ issue #18506

vaadin-bot commented 9 years ago

Originally by @Ansku

Attachment added: misalignment.png (56.0 KiB) https://trac-attachments.vaadin.com/trac/18506/misalignment.png

vaadin-bot commented 9 years ago

Originally by @thinwire

Checking this out, but can't promise anything, since I remember this being caused by intrinsic browser behavior. Might require some redesign or respecification.

vaadin-bot commented 9 years ago

Originally by @thinwire

Move to proper account

stale[bot] commented 6 years ago

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!