| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Added support for HTML5 push/replaceState for proper deep linkin features
* Automated test script now works at least on chrome
* Uses html5 push/popstate to implement uri fragment feature
* fire legacy fragment change events also via popstate events rpc calls
* send new fragments via pushstate mechanism
* formatting
* Formatting and adding test and workaround for IE bug
* Formatting and depracated UriFragmentListener
* Aligned naming in the new API
* Ignored IE due to web driver bug
Tested a workaround with javascript based window.location.href fetch,
but that don’t seem to work stable enough.
|
|
|
|
| |
Change-Id: I41a509c5a1dbb4388f11517dd62894ad2713f9aa
|
|
|
|
| |
Change-Id: I6f430c77caaad6d610133f340eba960f2268897e
|
|
|
|
|
|
|
|
|
| |
Without this change, some browsers, like GoogleBot, don't properly render the page.
Instead of weird JS exception (and hit to server with 404) we should at least try
to render the app with all browser. As webikit/chromium based browsers are
nowadays most popular, falling back to "safari" permutation.
Change-Id: I4275110962432b2552d51715a86a8e815fe539ad
|
|
|
|
| |
Change-Id: Id0f178dfc3910ee7492c860d381b2d413e82ba73
|
|
|
|
| |
Change-Id: I2ca0b41c3cc2ed851646ced2e0693a93b1853c95
|
|
Change-Id: I36c426086a2b957f6f738d17470c499a01ddac3b
|