GWT file lists only 5 of 6 user.agent values in its comments. (Vaadin 7.1.13)

[vaadin-bot]

Originally by basil.bourque

---

In a new Vaadin 7.1.13 project created by the Vaadin Plugin for NetBeans, when running in NetBeans 8 and Java 8 on Mac OS X (Mavericks)…

The "AppWidgetSet.gwt.xml" files contains comments guiding the programmer to add an element to specify a subset of user agents. The comments describe 5 such values for the "user.agent" tag: ie8,ie9,gecko1_8,safari,opera.

But that list contains 5 values while 6 permutations are reported as compiling in the NetBeans output pane. Apparently another value is missing from those comments.

---

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

[vaadin-bot]

Originally by basil.bourque

---

According to this page in the Book of Vaadin: https://vaadin.com/book/vaadin7/-/page/clientside.module.html …the missing value is "ie6".

But that contradicts the stated system requirements for Vaadin 7 as seen on this page: http://dev.vaadin.com/wiki/Vaadin7 … which states "Vaadin 7 will support Internet Explorer 8 and newer.".

[vaadin-bot]

Originally by @jdahlstrom

---

The value of the user.agent property in Vaadin.gwt.xml is "ie8,ie9,ie10,gecko1_8,safari,opera". So the missing one is ie10.

[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!

[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!