Get started
Loading...
Important Notice - Forums is archived

To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Product icon
TUTORIAL

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.

Where to include a web components css file when integrating a third party w by Martin Vyšný, 1 week ago
Recent Posts
Vaadin Forum3. Vaadin 6, 7, 8Framework UI

Form scrolls down when an unselected MasterDetailEditor row is clicked

Christophe Bismuth
9 years ago Apr 17, 2012 7:50pm

Dear Vaadin Team,

I'm giving a (deep) try to Vaadin 6.7.7 and JPAContainer 2.1.0.

The UI:
I've got a BeanValidationForm with height MasterDetailEditor objects in a BeanValidationForm.

The issue:
Let's say I create a few records in one of these master/detail editors. Now when I click one of the unselected rows, the form scrolls down, then I scroll the form up and try to click once again on my previous unselected (but now dash-bordered) row and then it gets selected.

Is there something I may have done wrong to produce this disturbing scrolling issue?

Tested with Google Chrome 18 and IE 9 (issue encountered with Vaadin 6.7.6 also).

Thank you,
Chris

Last updated on Apr, 17th 2012
Matti Tahvonen
9 years ago Apr 19, 2012 1:08pm

Hi,

Sounds like a some sort of focusing/selection issue in Table. Do you have a reduced test case for the issue? Or an online demo?

cheers,
matti

David Wall
9 years ago Apr 19, 2012 4:56pm

Wonder if this is related:

https://vaadin.com/forum/-/message_boards/view_message/849940

or perhaps

https://vaadin.com/forum/-/message_boards/view_message/461390

It seems that when forms are immediate, moving out of a field sends UIDL to the server and then various things are recalculated causing unexpected shifts. I think we got around some of these by ensuring the form is not immediate, and only setting only those fields that really need to be immediate. It does create an odd user experience to tab out of a field and then have fields move/resize. I think that using percentages rather than fixed sizes may be the culprit based on vaadin size recalculations, but sadly, the ability to set sizes by percentage is too compelling when you consider the different screen sizes people work on.