Skip to content
This repository

JS to handle the redirection to the mobile version of your site

tree: 3e42b4e5a9
README.md

JS Mobile Redirection

This "redirection_mobile" script will cover a basic scenario of full JS mobile redirection. It needs to be located in the desktop version of the site.

The user will be redirected to the mobile version of the site if it's trying to access the site from a mobile device (tablets have NOT been included by default). This check is mainly done sniffing the User-Agent string.

In some cases the user wants to access to the Desktop version of the site from a mobile device (sometimes the desktop version has more functionality). The script handles this situation as well.

To keep the user in the desktop version for the whole session, sessionStorage object has been used, specifically an item will be stored to distinguish if we're browsing through the desktop site. There is a fallback for old browsers that don't support sessionStorage, and a cookie will be used. The cookie that makes the access to the desktop version from a mobile device possible will expiry in one hour or you configure the expiry time.

To use this function, you need to import the "redirection_mobile.js" in your page and call the SA.redirection_mobile() function. The function accepts a configuration object with few properties:

  • mobile_prefix : prefix appended to the hostname, such as "m" to redirect to "m.domain.com". "m" is the default value if the property is not specified.
  • mobile_url : mobile url to use for the redirection (without the protocol), such as "whatever.com"/example to redirect to "whatever.com/example". If "mobile_prefix" is existing as well, "mobile_prefix" will be ignored. Empty string is the default value.
  • mobile_scheme : url scheme (http/https) of the mobile site domain, such as "https" to redirect to "https://m.domain.com". The protocol of the current page is the default value.
  • noredirection_param : parameter to pass in the querystring of the URL to avoid the redirection (the value must be equal to "true" to avoid redirection). Default value is "noredirection". Eg: http://domain.com?noredirection=true It's also the name of the item in the localStorage (or cookie name) used to avoid mobile redirection.
  • cookie_hours : number of hours the cookie needs to exist after redirection to desktop site. "1" is the default value.
  • tablet_redirection : boolean value that enables/disables(default) the redirection for tablet such as iPad, Samsung Galaxy Tab, Kindle or Motorola Xoom. - Default:false. The value needs to be a string (so wrapped in double or single quotes). If 'tablet_url' parameter not specified, the user will be redirected to the same URL as for mobile devices.
  • tablet_url : url to use for the redirection in case user is using a tablet to access the site. Default value is ""
  • keep_path : boolean to determine if the destination url needs to keep the path from the original url. Default value is 'false'
  • keep_query : boolean to determine if the destination url needs to keep the querystring from the original url. Default value is 'false'
  • beforeredirection_callback : if specified, callback launched before the redirection happens. If a falsy value is returned from the callback the redirection doesn't happen.

Below you can see an example that can clarify on how to use the script to redirect the user to "http://mobile.domain.com" from "http://domain.com":

    
        <script src="/js/redirection_mobile.js"></script>
    
    
        <script>
             SA.redirection_mobile ({
                noredirection_param:"noredirection",
                mobile_prefix : "mobile",
                cookie_hours : "2" 
            });
        </script>
    

Considering the previous code, from version 0.6, if you hit a page such as "http://domain.com/?noredirection=true" the redirection won't happen. For all the browser session, if sessionStorage is supported by the browser, the redirection won't occur. If sessionStorage (HTML5) is not supported, a cookie "noredirection=true" will be stored for 2 hours and it will block the redirection to the mobile site.

Another example, if you'd like to redirect the user to "https://whatever.com/example" this is the invocation you need:

    
        <script>
             SA.redirection_mobile ({
                mobile_url : "whatever.com/example",
                mobile_prefix : "https"
            });
        </script>
    

If you'd like to redirect the user to "https://whatever.com/example" even when using an Ipad or a generic tablet:

    
        <script>
             SA.redirection_mobile ({
                tablet_redirection : "true",
                mobile_url : "whatever.com/example",
                mobile_prefix : "https"
            });
        </script>
    

If you'd like to avoid the redirection to happen from a callback, this is the invocation you need:

    
        <script>
             SA.redirection_mobile ({
                beforeredirection_callback : (function(){alert("!"); return false;})
            });
        </script>
    

Find below an example that handles when we want to redirect the user to two different URLs depending on the device the user is using (mobile or tablet):

    
        <script>
             SA.redirection_mobile ({
                mobile_url : "mobile.whatever.com",
                tablet_url : "tablet.whatever.com",
            });
        </script>
    

If the user is accessing to a page such as "whatever.com/page1" and we want it to be redirected to "mobile.whatever.com/page1", that's how we should call redirection_mobile():

    
        <script>
             SA.redirection_mobile ({
                mobile_prefix : "mobile",
                keep_path : true,
                keep_query : true
            });
        </script>
    

Alternatively you can use "redirection_mobile_self.js", that is an anonyimous self-executing function and it uses the default values for the different properties:

  • "mobile_prefix" : "m"
  • "noredirection_param" : "noredirection"
  • "cookie_hours" : 1
  • "mobile_url" : ""
  • "mobile_scheme" : protocol of the current page
  • "tablet_redirection" : "false"
  • "keep_path" : false
  • "keep_query" : false
  • "tablet_url" : ""
  • "beforeredirection_callback" : n/a

It doesn't need any configuration or any invocation, so you just need to drop "it "redirection_mobile_self.js" on your webserver and call the script from your HTML.

    
        <script src="/js/redirection_mobile_self.js"></script>
    

I also created "redirection_mobile_testable.js" that is just a copy from "redirection_mobile.js", but it's using few arguments such as "document", "window", "navigator" for testing purpose. Test cases have been written using QUnit.

The scripts have their minified versions (YUI compressor has been used).

Who is using it?

Holden Australia (http://www.holden.com.au), Cityweb (http://www.citywebs.co.uk/), OXiane (http://www.oxiane.com), etc..

Licence?

Dual licensed under the MIT and GPL Version 3 licenses.

Update 21/11/2010:

All main mobile devices have been considered.

Update 20/12/2010:

Fixed a critical issue on IE

Update 06/01/2011:

Version 0.5 released

Update 21/01/2011:

Version 0.6 released - IMPORTANT Change in parameters -- "redirection_paramName" will replace "param"

Update 11/02/2011:

Version 0.7 released - Added support for Nintendo WII and more HTC phones.

Update 02/04/2011:

Version 0.8 released - Added support for "ipad_redirection" and "beforeredirection_callback" properties. Ipad excluded from the standard redirection

Update 04/04/2011:

Version 0.8.5 released - "ipad_redirection" changed into "tablet_redirection" to extend the feature to multiple tablets. "beforeredirection_callback" changed slightly to let avoid the redirection.

Update 12/04/2011:

Version 0.8.6 released - JSLint fixes

Update 25/07/2011:

Version 0.9.5 released - "keep_path", "keep_query" and "tablet_url" parameters been added. Also 'noredirection_param' is used now instead of 'redirection_paramName'

Feel free to fork it!

Something went wrong with that request. Please try again.