Yeah do you mind doing that? There is already a test for Qt at the top of
the file, you could leverage that.
On May 2, 2014 10:11 PM, "Jonathan" <notifications@github.com> wrote:

> In inst/www/shared/shiny.js:
>
> > @@ -503,6 +503,11 @@
> >            protocol = 'wss:';
> >
> >          var defaultPath = window.location.pathname;
> > +        // some older WebKit browsers return the pathname already decoded;
> > +        // if we find invalid URL characters in the path, encode them (twice,
> > +        // to survive decoding by WebSocket below)
>
> That's a good question. It could be that the double-encoding isn't
> necessary on other browsers, but since I'm not aware of any browsers other
> than older WebKit implementations that have the bug it's hard to know for
> certain. If we wanted to be more conservative here we could scope the fix
> to Qt specifically--what do you think?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/rstudio/shiny/pull/466/files#r12254840>
> .
>