I've encountered a very, very strange bug with enyo's router on Android Browser. My application has multiple 'pages' each with its own route. One of the paths in my application is:
episode/:episode. The token regexp -
/\:[a-zA-Z0-9]*/g - detects this particular path as dynamic on every browser except for the native Android browser.
Basically, when the path is added to the router and the test is evaluated by the router itself, it fails.
However, if I then test the token manually by typing it in the console, it works just fine and the test passes. Very strange...
The solution, in my case, was to remove the 'global' flag from the regexp:
/\:[a-zA-Z0-9]*/ The router seems to work just fine that way, and Android browser once again recognizes
episode/:episode as a dynamic path.
Is this something worthy of opening a ticket? Or is it too exotic to be worth it? I'm not sure if I can easily recreate a minimal test-case, considering the fact that things work fine for everyone else and even work fine in the console in the very browser that's causing the problem.