Update SizeWithUnit.parseStringSize to allow 'initial' and 'auto'

[Flamenco]

I have a javascript function that directly modifies element element CSS styles. If I set the width or height to 'initial', Vaadin throws an error when reading the element.

The initial and auto incoming values can be simply replaced with an empty string. The empty string is allowed in the SharedUtil.SIZE_PATTERN regex and has the same effect.

I will submit a fix, but I want make sure there is no disagreement.

[Legioth]

Do you mean that you have javascript that sets the inline style of some elements to initial or auto of the root of some component after some other value has been set by Vaadin Framework?

In that case, you might also have other problems than SIZE_PATTERN since the framework will always reset the size to the value set from the server whenever there's any state change for that component.

On the other hand, both values you suggest are valid CSS size values, so from that point of view there shouldn't be any objections against allowing those, as long as it doesn't cause any unintended side effects.

[Flamenco]

I have updated the vaadin element from another library. Vaadin reads the client-side style value of 'initial' and throws an exception when parsing it.

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