vaadin / framework

Vaadin 6, 7, 8 is a Java framework for modern Java web applications.
http://vaadin.com/
Other
1.78k stars 729 forks source link

GridLayout on iPad #9830

Closed boxofstops closed 4 years ago

boxofstops commented 7 years ago

The following sample is showing with a large gap between the two buttons on an iPad.

Other browsers, including an iPhone look fine.

        GridLayout gridLayout = new GridLayout(2, 1);
        //HorizontalLayout gridLayout = new HorizontalLayout(); // Workaround 1
        gridLayout.setSpacing(true);

        Button button1 = new Button();
        button1.setCaption("Button 1");
        //button1.setWidth("200px"); // Workaround 2
        gridLayout.addComponent(button1);

        Button button2 = new Button();
        button2.setCaption("Button 2");
        //button2.setWidth("200px"); // Workaround 2
        gridLayout.addComponent(button2);

On the iPad, you see the buttons momentarily as double width, then they shrink, but the GridLayout keeps the larger cell size.

With a HorizontalLayout the same thing happens with the button widths, but layout shrinks back OK - workaround 1 above.

Also, if the buttons have a definite width on the buttons, the GridLayout sizes everything correctly from the start - workaround 2.

This is with Vaadin 8.1.1.

ipad-screenshot iphone-screenshot Sample project: vaadin8-spring-demo.zip

This issue relates to this forum thread: https://vaadin.com/forum#!/thread/16526300

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):

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!

stale[bot] commented 4 years ago

The issue was automatically closed due to inactivity. If you found some new details to it or started working on it, comment on the issue so that maintainers can re-open it.