A “desperate times call for desperate measures” hack

Last week I had to solve some tricky problems related to a Web application that needs to run locally on some tablets in kiosk mode without any Internet connection.

With the term kiosk mode I mean that the browser used to run the application, in this case Google Chrome, is wrapped in another application that is acting like a sandbox to prevent users from accessing the Operating System or any other application.

The Web application I am talking about is based on WordPress and on a custom Javascript engine handling some cool and shiny animations.

The problem was that some of the tablets were simply found, after a while, on the “T-Rex page” of Google Chrome:


Furthermore, given the kiosk mode, there was no simple way to go back to the previous page or to restart the application without disassembling the structure holding the tablets.

And the option to let the users play with the T-Rex wasn’t a good one for the client…

Anyway that was strange as we properly replaced all the external links inside the application with local references.

After a little bit of debugging directly on site (i.e. where the tablets were exposed to the public) I found the problem: the double click, or better the long click.

The long press would display the context menu of Chrome, letting the user access some interesting options like “Inspect element”, “View page source” and “Search with Google”. The last option in particular was the source of the over mentioned “T-Rex page”.

To fix the problem I wrote this little and trivial Javascript snippet:


The Javascript engine was based on jQuery and so I too relied on it for my snippet.

After successfully applying the fix on some of the tablets I noticed that there was still a problem. The right click was properly disabled everywhere except from the video player. Indeed the player, i.e. JWplayer, was still showing its specific context menu with an external link that was still causing the user to land on the “T-Rex page”. Here it is the bad context menu:


At the time I became aware of the problem I was on site without any Internet connection and so I couldn’t ask to Google for the proper solution. The first thing that came to my mind was to directly hack the player. We had already created a “local” version of the player to handle another error related to the fetch of the skins that was causing the player to break up.

JWplayer isn’t indeed designed to work offline.

After a few failures in disabling the player right click (I was working directly on the minified version of the local html5 player, i.e. jwplayer.html5.js) I decided to take a different approach.

I looked at the underlying link of the context menu option and I simply replaced it with the link to the current page.

It wasn’t easy because there were many different places where the link was hardcoded and where it was used but after a while I managed to find the last location where it was used right before it was printed out in the context menu.

Just for the record I replaced this line:


with this:


The over mentioned lines may vary based on the version of the player. The one we were using is the 6.12.4956.

I know this is a bad and ugly hack but It saved my day in a situation were I didn’t have the proper knowledge about the application to take the appropriate action.

I hope you will never find in a situation like the one I described but if you will, my personal advice is to follow your instinct and what Elsa say.


Cheers! 🙂

Leave a Reply