[grid] sort icon is cutoff by column selector

[vaadin-bot]

Originally by spungin

---

See screen shot for details. Column to the right is sorted and their is no way to 'scroll'. It seems the width calculation does not take the column picker menu into account.

---

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

[vaadin-bot]

Originally by spungin

---

Attachment added: Screen+Shot+2015-06-23+at+6.40.11+PM.png (94.1 KiB) https://trac-attachments.vaadin.com/trac/18333/Screen+Shot+2015-06-23+at+6.40.11+PM.png screenshot

[stale[bot]]

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!

[glebfox]

Hi,

Vaadin 8.8.3, the issue is still reproduced.

When there is no vertical scroll, then sort icon of the last column if overlapped by grid sidebar button (aka Column Selector)

import com.vaadin.annotations.Theme;
import com.vaadin.annotations.VaadinServletConfiguration;
import com.vaadin.server.VaadinRequest;
import com.vaadin.server.VaadinServlet;
import com.vaadin.ui.Grid;
import com.vaadin.ui.UI;
import com.vaadin.ui.themes.ValoTheme;

import javax.servlet.annotation.WebServlet;
import java.util.Arrays;
import java.util.List;

@Theme(ValoTheme.THEME_NAME)
public class MyUI extends UI {

    @Override
    protected void init(VaadinRequest vaadinRequest) {
        List<Person> people = Arrays.asList(
                new Person("Nicolaus Copernicus", 1543),
                new Person("Galileo Galilei", 1564),
                new Person("Johannes Kepler", 1571));

        Grid<Person> grid = new Grid<>();

        grid.setItems(people);
        grid.addColumn(Person::getName).setCaption("Name").setHidable(true);
        grid.addColumn(Person::getBirthYear).setCaption("Year of birth").setHidable(true);

        grid.setSizeFull();

        setContent(grid);
    }

    private class Person {
        private final String name;
        private final int birthYear;

        public Person(String name, int birthYear) {
            this.name = name;
            this.birthYear = birthYear;
        }

        public String getName() {
            return name;
        }

        public int getBirthYear() {
            return birthYear;
        }
    }

    @WebServlet(urlPatterns = "/*", name = "MyUIServlet", asyncSupported = true)
    @VaadinServletConfiguration(ui = MyUI.class, productionMode = false)
    public static class MyUIServlet extends VaadinServlet {
    }
}

[stale[bot]]

Hello there!

We are sorry that this issue hasn't progressed lately. We are prioritizing issues by severity and the number of customers we expect are experiencing this and haven't gotten around to fix this issue yet.

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!