Based on [jQuery migration plugin][1] , I found this.

    jQuery.uaMatch = function( ua ) {
        ua = ua.toLowerCase();
        var match = /(chrome)[ \/]([\w.]+)/.exec( ua ) ||
            /(webkit)[ \/]([\w.]+)/.exec( ua ) ||
            /(opera)(?:.*version|)[ \/]([\w.]+)/.exec( ua ) ||
            /(msie) ([\w.]+)/.exec( ua ) ||
		    ua.indexOf(&quot;compatible&quot;) &lt; 0 &amp;&amp; /(mozilla)(?:.*? rv:([\w.]+)|)/.exec( ua ) || [];
	    return {
		    browser: match[ 1 ] || &quot;&quot;,
		    version: match[ 2 ] || &quot;0&quot;
	    };
    };
    if ( !jQuery.browser ) {
	    var 
        matched = jQuery.uaMatch( navigator.userAgent ),
	    browser = {};
	    if ( matched.browser ) {
		    browser[ matched.browser ] = true;
		    browser.version = matched.version;
	    }
    	// Chrome is Webkit, but Webkit is also Safari.
	    if ( browser.chrome ) {
		    browser.webkit = true;
    	} else if ( browser.webkit ) {
	       	browser.safari = true;
    	}
    	jQuery.browser = browser;
    }


  [1]: http://code.jquery.com/jquery-migrate-1.1.1.js

### If you really need good old $.browser 
According to the [docs][1], this feature was deprecated in **1.3**,
and totally removed in **1.9**, although it is still available in the [official jQuery Migrate plugin](https://github.com/jquery/jquery-migrate).

### If you want to do it right
Depending on [browser detection][3] is [not a good idea][4]. Feature detection is the way to go ([Modernizr](http://www.modernizr.com/) is a great tool for that). jQuery had a `$.support()` method to provide some feature detection, but it is now deprecated as well. [They also suggest using Modernizer.][5]

### If you really need browser detection
Fixing browser quirks is not a valid use case for browser detection, but there are other use cases. Use any Javascript browser detection tool (like [bowser](https://github.com/lancedikson/bowser)), as this functionality does not depend on jQuery at all.

  [1]: http://api.jquery.com/jQuery.browser/
  [2]: http://davecardwell.co.uk/javascript/jquery/plugins/jquery-browserdetect/
  [3]: http://jibbering.com/faq/notes/detect-browser/
  [4]: http://www.quirksmode.org/js/support.html
  [5]: http://api.jquery.com/jQuery.support/

There isn&#39;t a direct replacement. You should be using feature detection rather than browser detection (do you have a good reason to need to know the browser?), so you can use the [`$.support` property](http://api.jquery.com/jQuery.support/). (It says as much in the API doco for `$.browser`.)

[jQuery.support][1]


  [1]: http://api.jquery.com/jQuery.support/

you can use navigator variable from javascript    

    console.log(navigator)

but if you want to check the compatiblility with a function of jquery you can use the support var like

    $.support.ajax

 

The [jquery-browser-plugin][1] is a good drop in replacement


  [1]: https://github.com/gabceb/jquery-browser-plugin

Many try/except/finally-clauses not only &quot;uglify&quot; my code, but i find myself often using identical exception-handling for similar tasks. So i was considering reducing redundancy by &quot;outsourcing&quot; them to a ... decorator.

Because i was sure not to be the 1st one to come to this conclusion, I googled and found this - imho - ingenious [recipe][1] which added the possibility to handle more than one exception.

But i was surprised why this doesn&#39;t seem to be a wide known and used practice per se, so i was wondering if there is maybe an aspect i wasn&#39;t considering? 

1. Is it bogus to use the decorator pattern for exception-handling or did i just miss it the whole time? Please enlighten me! What are the pitfalls? 

2. Is there maybe even a package/module out there which supports the creation of such exception-handling in a reasonable way?

  [1]: http://code.activestate.com/recipes/408937-basic-exception-handling-idiom-using-decorators/

&quot;outsourcing&quot; exception-handling to a decorator

Here I am, with another question about aggregation and association. I wanted to learn some basics of UML, so I started reading &quot;UML distilled&quot; by Martin Fowler. I read both chapters about classes, and there is one thing that I can&#39;t fully grasp I think, and that is aggregation vs association. In the book there is this quote:

&gt; In the pre-UML days, people were usually rather vague on what was aggregation and what was
association. Whether vague or not, they were always inconsistent with everyone else. As a result,
many modelers think that aggregation is important, although for different reasons. So  the UML
included aggregation (Figure 5.3) but with hardly any semantics. As Jim Rumbaugh says, &quot;Think of it
as a modeling placebo&quot; *[Rumbaugh, UML Reference].*

As I understand from this quote and topics that I read on Stack Overflow it doesn&#39;t matter which one of those two relations I use, they mean basically the same, or is there any situation where the usage of aggregation instead of association would be justified and/or I could not change one to the other without changing the &quot;meaning&quot; of a class diagram?

I am asking this, because this book is from 2003 and some things could have changed during those few years.


UML aggregation vs association

The jQuery document tags `$.browser` as deprecated. So what&#39;s the replacement for it?




What&#39;s the replacement for $.browser

<p>The jQuery document tags <code>$.browser</code> as deprecated. So what's the replacement for it?</p>


I was trying to use jQuery&#39;s page scroll inside some pages and could successfully make a smooth page scroll. The only problem I have now is when attempting to do that from different page. What I mean by that is if I click on a link in a page, it should load the new page and then scroll to the specific div element.

Here is the code I used to scrolling inside the page:

    var jump=function(e)
    {
           //prevent the &quot;normal&quot; behaviour which would be a &quot;hard&quot; jump
           e.preventDefault();
       //Get the target
       var target = $(this).attr(&quot;href&quot;);
       //perform animated scrolling
       $(&#39;html,body&#39;).animate(
       {
               //get top-position of target-element and set it as scroll target
               scrollTop: $(target).offset().top
       //scrolldelay: 2 seconds
       },2000,function()
       {
               //attach the hash (#jumptarget) to the pageurl
               location.hash = target;
       });

    }
    
    $(document).ready(function()
    {
           $(&#39;a[href*=#]&#39;).bind(&quot;click&quot;, jump);
           return false;
    });

I hope the idea is clear.

Thanks 

**Very important Note**:
This code I posted above works great inside the same page, but what I&#39;m after is to click a link from one page and go to another one and then scroll to the target. I hope it is clear now. Thanks 

jQuery scroll to ID from different page

I&#39;m trying to find a way to use jQuery autocomplete with callback source getting data via an ajax json object list from the server.

Could anybody give some directions?

I googled it but couldn&#39;t find a complete solution.

jQuery autocomplete with callback ajax json

In terms of performance, what are the gains (or just differences) between:

    $(&#39;.myEl&#39;).click();

and 

    $(&#39;.myEl&#39;).trigger(&#39;click&#39;);

Are there any at all?

jQuery advantages/differences in .trigger() vs .click()

I keep getting the error alert. There is nothing wrong with the MYSQL part, the query gets executed and I can see the email addresses in the db.

**The client side:**

    &lt;script type=&quot;text/javascript&quot;&gt;
      $(function() {
        $(&quot;form#subsribe_form&quot;).submit(function() {
          var email = $(&quot;#email&quot;).val();
    
          $.ajax({
            url: &quot;subscribe.php&quot;,
            type: &quot;POST&quot;,
            data: {email: email},
            dataType: &quot;json&quot;,
            success: function() {
              alert(&quot;Thank you for subscribing!&quot;);
            },
            error: function() {
              alert(&quot;There was an error. Try again please!&quot;);
            }
          });
          return false;
        });
      });
    &lt;/script&gt;

**The server side:**

    &lt;?php 
    $user=&quot;username&quot;;
    $password=&quot;password&quot;;
    $database=&quot;database&quot;;
    
    mysql_connect(localhost,$user,$password);
    mysql_select_db($database) or die( &quot;Unable to select database&quot;);
    
    $senderEmail = isset( $_POST[&#39;email&#39;] ) ? preg_replace( &quot;/[^\.\-\_\@a-zA-Z0-9]/&quot;, &quot;&quot;, $_POST[&#39;email&#39;] ) : &quot;&quot;;
    
    if($senderEmail != &quot;&quot;)
    	$query = &quot;INSERT INTO participants(col1 , col2) VALUES (CURDATE(),&#39;&quot;.$senderEmail.&quot;&#39;)&quot;;
    mysql_query($query);
    mysql_close();
    
    $response_array[&#39;status&#39;] = &#39;success&#39;;    
    
    echo json_encode($response_array);
    ?&gt;

How do I return a proper success/error message for JQuery .ajax() using PHP?

How to get an element with its `name` attribute with jQuery?

Is there anything (like `#` for id and `.` for class) for name in jQuery?


How do I select an element with its name attribute in jQuery?

I have 5 addons/extensions for FF, Chrome, IE, Opera, and Safari. 

How can I recognize the user browser and redirect (once an install button has been clicked) to download the corresponding addon?

How to detect Safari, Chrome, IE, Firefox and Opera browser?

I want to bounce users of our web site to an error page if they&#39;re using a version of `Internet Explorer` prior to v9. It&#39;s just not worth our time and money to support `IE pre-v9`. Users of all other non-IE browsers are fine and shouldn&#39;t be bounced. Here&#39;s the proposed code:

    if(navigator.appName.indexOf(&quot;Internet Explorer&quot;)!=-1){		//yeah, he&#39;s using IE
    	var badBrowser=(
    		navigator.appVersion.indexOf(&quot;MSIE 9&quot;)==-1 &amp;&amp;	//v9 is ok
    		navigator.appVersion.indexOf(&quot;MSIE 1&quot;)==-1	//v10, 11, 12, etc. is fine too
    	);
    						
    	if(badBrowser){
    		// navigate to error page
    	}
    }

Will this code do the trick?

To head off a few comments that will probably be coming my way:

 1. Yes, I know that users can forge their `useragent` string. I&#39;m not concerned.
 2. Yes, I know that programming pros prefer sniffing out feature-support instead of browser-type but I don&#39;t feel this approach makes sense in this case. I already know that all (relevant) non-IE browsers support the features that I need and that all `pre-v9 IE` browsers don&#39;t. Checking feature by feature throughout the site would be a waste.
 3. Yes, I know that someone trying to access the site using `IE v1` (or &gt;= 20) wouldn&#39;t get &#39;badBrowser&#39; set to true and the warning page wouldn&#39;t be displayed properly. That&#39;s a risk we&#39;re willing to take.
 4. Yes, I know that Microsoft has &quot;conditional comments&quot; that can be used for precise browser version detection. IE no longer supports conditional comments as of `IE 10`, rendering this approach absolutely useless.

Any other obvious issues to be aware of?

Detect IE version (prior to v9) in JavaScript

I&#39;m looking for a function which return boolean value if user has mobile browser or not.

I know that I can use `navigator.userAgent` and write that function by using regex, but user-agents are too various for different platforms. I doubt that match all possible devices would be easy, and I think this problem has been solved before many times so there should be some kind of complete solution for such task.

I was looking at [this site](http://detectmobilebrowsers.com), but sadly the script is so cryptic that I have no idea how to use it for my purpose, which is to create a function which return true / false.

Detecting a mobile browser

I had several clients complain yesterday that some code stopped working. Apparently it comes down to plug-ins using the now deprecated `jQuery.browser` which stopped working yesterday when jQuery 1.9 was released.

I (quickly) looked at the 1.9 change docs and it *seems* like they want me to substitute some pretty heavy libraries just for that **one** function.

Is there a recommended lightest weight plug-in or code snippet to restore that functionality?

For what these sites need, it&#39;s very basic; I only need the most basic detection of IE vs FF vs everyone else.

Suggestions?

Easiest/Lightest Replacement For Browser Detection jQuery 1.9?

I&#39;m developping a JS-app that needs to work both on the client side and the server side (in Javascript on a browser and in Node.js), and I would like to be able to reuse the parts of the code that are used for both sides.

I have found out that `window` was a variable only accessible on Browsers, and `global` in node, so I can detect in which environment the code is executing (assuming that no script declares the `window` variable)

They are two problems.

 1. How should I detect in which browser the code is running. For example, is this code OK. (This code is inline, meaning that it is surrounded by some global code, reused for both environments)

		if window?
			totalPath= &quot;../examples/#{path}&quot;
		else
			totalPath= &quot;../../examples/#{path}&quot;

 2. How can I use global variables for both environments ? Now, I&#39;m doing the following, but this really doesn&#39;t feel right.

        if window?
    	    window.DocUtils = {}
    	    window.docX = []
    	    window.docXData= []
        else
    	    global.DocUtils= {}
    	    global.docX = []
    	    global.docXData = []

Content Type	Original Author	Original Content on Stackoverflow
Question	Rocky	View Question on Stackoverflow
Solution 1 - Jquery	takien	View Answer on Stackoverflow
Solution 2 - Jquery	kapa	View Answer on Stackoverflow
Solution 3 - Jquery	nnnnnn	View Answer on Stackoverflow
Solution 4 - Jquery	Emil Vikström	View Answer on Stackoverflow
Solution 5 - Jquery	Spidfire	View Answer on Stackoverflow
Solution 6 - Jquery	Claus	View Answer on Stackoverflow

What's the replacement for $.browser

Jquery Problem Overview

Jquery Solutions

Solution 1 - Jquery

Solution 2 - Jquery

If you really need good old $.browser

If you want to do it right

If you really need browser detection

Solution 3 - Jquery

Solution 4 - Jquery

Solution 5 - Jquery

Solution 6 - Jquery

UML aggregation vs association

"outsourcing" exception-handling to a decorator

Attributions