You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GWT emulation of isWhitespace is listing characters explicitly to avoid discrepancies between Java and JS notion of "whitespace", but there is one inconsistency with Java 8 and one inconsistency with Java 11.
For comparison the table below also shows which characters are recognized as whitespace using chr.match(/\s/) in JS (Chrome).
AFAICT, U+180E was a space (Unicode Zs category) priori to Unicode 6.3.0, and Java 8 was based on Unicode 6.2.0 (Java 9 used Unicode 8)
I'd go with the more recent Unicode stance and not consider U+180E a space, even if it means GWT with -sourceLevel 8 behaves differently from a JDK 8 (but that would likely be the same as running Java 8 bytecode on a JDK 8 vs a more recent JDK)
Activity
niloc132 commentedon Jul 8, 2024
With regards to
\u180E, do we consider Java 8 to be broken here? Or do we think that GWT should be aware if it is running "as Java8" or "as Java 11"?tbroyer commentedon Jul 8, 2024
AFAICT, U+180E was a space (Unicode Zs category) priori to Unicode 6.3.0, and Java 8 was based on Unicode 6.2.0 (Java 9 used Unicode 8)
I'd go with the more recent Unicode stance and not consider U+180E a space, even if it means GWT with
-sourceLevel 8behaves differently from a JDK 8 (but that would likely be the same as running Java 8 bytecode on a JDK 8 vs a more recent JDK)String method emulation for Java 11, align Character.isWhitespace wit…