Ray the only problem I have with the jQuery detection or any JS detection, is that on my phone a Samsung Galaxy S. Both your site and any site that has begun using this detection from jQuery, means I actually have to kill the internet browser in my phone. I gave up trying to get you to fix this on your blog over 8 months ago, and find that it is easy for me to just filter sites out that use this jQuery method.

The reason being is that each time I hit my back button, the one that navigates app screens to the previous screen. Reloads the jQuery detection and redirects back to the mobile version, that means that I can never leave the browser in the manner that one should be able too.

I highly suggest that if anyone is going to be looking at Mobile Detection for their websites in the future, that you have a good look at the project that is desinged for this and that is the OWASPI project WURFL at http://wurfl.sourceforge.net/

Sorry to be so negative, but thats the reality of this.

The detection I'm using has _nothing_ to do with jQuery. You know that, right? It's pure server side code using the item listed above.

My site uses a session cookie when you leave the mobile site - but ONLY sets it if you click the exit mobile button the bottom right. Don't hit back. Can you just try that?

Will chat with you off list.

I should say that I assumed it was jQuery because the page loads, and then is redirected to the mobile site. Which indicated some JavaScript redirection was happening, and as you used jQuery, I assumed that this was happening by jQuery.

Seems you could always detect a mobile browser with the "cgi.http_user_agent" string and then use CFlocation to send the user to a mobile version of the application. I don't mean on every page request either, just send them to a jQuery mobile version on the first request.

I have been using jQuery mobile to build clients mobile versions of their current web applications and so far they love it.

@Andrew: jQuery mobile doesn't crash our companies Samsung Galaxy S browser, and the user can leave the page whenever they want?

After chatting with Ray off list, it wasnt jQuery which I mentioned above that I did assume it was it. The problem is ColdFusion and the fact that CFLocation is used, when doing it this way the mobile browser will end up in and endless loop when trying to go backwards.

It was wrong to make the intial assumption I did make.

What it wrong with cflocation, I have experienced no endless loops? You mention a problem with cflocation yet offer no alternative solution? Correct me if I am wrong but doesn't cflocation keep the original landing page's HTTP_REFERER?

I think ou are getting a little confused there, refferer has nothing to do with previous page URL. When you hit a page URL the browser has already began loading that URL, with a cflocation you are forcing another URL to then be loaded into the browser. You can test this very easily by creating a page that loads anothe URL, and try to hit the back button. You will find that the browser has detected that you are going to a page that has been redirected, and redirects you back to the same page you just came from.

That is just common knowledge and behaviour of a browser mechanics.

@Andrew: So if is not the way you think it should be done (which is what I think you are getting at) what is your solution to the problem?

It will depend on you and your application, but as I work with MVC type frameworks this is very easy to overcome with no extra effort on my part.

But a simple cfinlclude to load that data would work fine.

Look I have to make this very clear, this is not a dig at Ray or jQuery but something that I have noticed overtime. And there are a couple of high profile news sites that detect that you are browsing and redirect you to a new domain usual starting with m so if the domain was www.abc.com it would redirecto you to m.abc.com and when you try to hit the back button, you are taken back to the www.abc.com site which then redirects you back to m.abc.com

I am not telling anyone how to do this, or that they shouldn't do this. What I am saying is that you really should be aware that on a mobil device it is highly possible that this will frustrate the user to the website, and I have stopped browsing these sites because I was getting sick and tired of having to kill the task on the mobile each and everytime.

I guess at the end of the day, you are free to do what you please. but I just want it be known that this can be a problem that noone might have ever considered.

Silly rookies! No sense arguing...

Thanks for the helpful comment there Topper. As helpful as your last one. Are you trying to troll here or do you have a point?

Hey, thx for all. Can you share the source code of your demos?

Thx a lot =D

I did. :) Click the Menu button on the embedded slide viewer above.

Lindo!!! - BTF hehe, i never see this slide viewer before =D Thx a lot =D

Slidesix.com - darn good site for hosting presos - especially for developers. Also built by a friend of mine so I may be biased.

Hey, Ray... I'm trying to get the code, etc., from your jQuery Mobile presentation. I see where it says I should click the menu button in the slideshow to get the attachments, but the slideshow area now states that there are no slides, and the menu button doesn't respond.

Is there another way to get the source code/documents?

This looks to be an issue with SlideSix. Try again in a while. If you want the slides/code now, ping me via Twitter/IM with your email and I can send you a zip.

Fixed. Todd Sharp is Uber Man.

Oh, wait! Another refresh (which I had tried several times...) and the presentation came to life! :o)

Wow! Fast fix! Impressive! ;o)