Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I'm not so sure it's a Samsung issue. Consider:</p> <p>HTC One S with Android 4.0.3, loads the m.cycletrader.com home page with no issues but crashes the search results page on search. There is a flash of content and then what appears to be a refresh and then a white screen. If I wait long enough, I'll get an endless loop redirect notice.</p> <p>Desktop browser (Firefox 25) using default user-agent string, loads the same home and search results pages with no issues.</p> <p>Desktop browser (Firefox 25) using User-Agent Switcher to report as HTC Sensation (Android 4.0.3) loads the same home page with no issues but crashes the search results page on search - just like the actual smartphone. There is the initial flash of content, then a whitescreen, and no source code is retained by the browser for diagnostics and inspection. We initially thought a javascript document.write was the culprit but it is present and does not cause this problem for other user-agents.</p> <p>The common denominator? Omniture. Disable Omniture on the search results page, the page loads with no issues. I wonder if Omniture is doing something hinky when it detects certain smartphones and perhaps, Android versions (v4.0.3 was given a clean bill of health earlier, but that was a year ago). </p> <p>I'd like to get to the bottom of this so we can either fix whatever it is in our Omniture implementation or fire off a bug report so that Omniture is put on notice that their code is breaking our site (m.cycletrader.com).</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload