Stephen Hicks

I took a look at the demos page and I'm not able to reproduce this. Can you give more specifics, like which browser you're using, and which element has the...

Mirroring the comment our goog.ui maintainer made on the internal issue: > goog.ui is in maintenance mode and we're not fixing minor issues anymore. If you send a PR we...

I think your link is a little bit off, since `scheme` isn't defined in terms of `unreserved`, but is *is* defined in Appendix A as `ALPHA *( ALPHA / DIGIT...

I'm not clear on what the solution should be. As I understand it, goog.Html5History should probably be preferred over goog.History, so workaround #2 is out. And as you point out,...

Looks like the problem is on line 168, where we assume that each character is a byte and we OR together four characters (left-shifted 0, 8, 16, and 24 bits)....

Looking further, this is a problem with most or all of our hash implementations. I had hoped to simply deal with higher characters only when we see them, but since...

This is definitely a "help wanted" sort of issue, though a number of these will be difficult due to internal usages.

That's a good idea. We actually hide the warnings during compilation internally (preferring to instead expose them during code review) so we don't have as much visibility into that. Feel...

For now the best bet is probably to suppress it. Internally we're working on infrastructure to be able to add ES6 code into existing files, but that won't likely finish...

The reason is basically internal hemorrhaging. We needed to stop the bleeding. We'd tried other means to communicate "don't use this" and none of them were effective enough - we...