|
Yes, sorry. This demonstrates the importance of reading the entire
thread before responding ;-] Anywhoo, most of the detection methods I referenced still apply. But here's another angle: My guess is that you could be temporarily sending a response (page) to the browser, instead of issuing a literal 300 series redirect. (Many sites employ this technique: load a blank page just long enough to throw a cookie in there, then have _javascript_ swap out the href a millisecond later. You may see "redirecting..." on the screen for a sec (which is really just a link to the end - in case JS is disabled). Depending on the speed of your connection, you may have seen this effect when clicking on Google, FB or LinkedIn links. So if you do the same thing, you could use JS (occasionally cgi) to get the literal size of the device's viewport. Rather than jumping thru hoops to match the user agent with a big list of ever-changing possibilities, just work with the thing that really matters: the size of the window. http://viewportsizes.com/mine/ HTH, Al On 2/3/2016 9:55 AM, Jason King wrote:
-- -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en --- You received this message because you are subscribed to the Google Groups "Open BlueDragon" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. |
Re: [OpenBD] Determining Device Type via CFML
'Alan Holden' via Open BlueDragon Wed, 03 Feb 2016 16:00:32 -0800
- [OpenBD] Determining Device Type via CFM... Jason Allen
- Re: [OpenBD] Determining Device Typ... Benjamin Davis
- Re: [OpenBD] Determining Device... Matthew Roach
- Re: [OpenBD] Determining De... Jason Allen
- Re: [OpenBD] Determinin... 'Alan Holden' via Open BlueDragon
- Re: [OpenBD] Deter... Jason King
- Re: [OpenBD] D... 'Alan Holden' via Open BlueDragon
- [OpenBD] Re: Determining Device Typ... Martin Webb
