Obsolete
Status Update
No update yet.
Comments
tr...@gmail.com
I have forwarded your request to our engineering team. I cannot provide an E.T.A. or guarantee that this feature will be deployed. Rest assured that your feedback is always seriously taken. Any future updates will be posted on this thread.
tr...@gmail.com
Is there any progress with that feature request?
ta...@gmail.com
I'm also very interested in having this extension in cloudsql for postgres since it's blocking the emigration of one of ours databases
tu...@google.com
+1 to voting for the ip4r extension. Currently not supported in Cloud SQL and we make use of it.
tf...@gmail.com
Any updates on this? It's blocking a migration from RDS to google cloud.
Description
In Android 4.4 with the new WebView, loadUrl with "javascript:" URLs will URL-decode the string before execution. Where previously %-escapes where sent unchanged to the JavaScript, they will now be decoded first, which can result in an accidental re-encoding of e.g. ISO-8859-1-based %-escapes into Unicode characters. That means, if e.g. a pre-encoded URL containg encoded binary data or ISO-8859-1 is sent as argument to a JavaScript, this might then be sent re-encoded as UTF-8 to the server, breaking things.
The work-around is to use the new evaluateJavascript method of Android 4.4
Nevertheless, this is an incompatible, and so it seems, undocumented change of a public API which can introduce subtle bugs into existing applications. The change should be properly documented in the JavaDoc of the method.