type,ticket,votes,component,version,milestone,created,_changetime,_description,_summary_
bug,10568,1,effects,1.6.4,1.next,2011-10-24T21:36:16Z,2012-03-10T04:23:58Z,"Versions affected: 1.6 - 1.6.4[[BR]]
Browsers: Firefox 7.0.1, Chromium 17.0.914.0, IE 9/8, Opera 11.52,[[BR]]
Operating system: Windows 7 SP1 and Windows XP SP3,[[BR]]
[[BR]]
[http://jsfiddle.net/jzjam/][[BR]]
[[BR]]
When calling animate('width', 'show') on hidden inline element it shows up immediately instead of animating the width. When hiding it works as expected.[[BR]]
I pinpointed it to line 8243 non-minimized jQuery source v.1.6.4:[[BR]]
{{{
jQuery.css( this, ""display"" ) === ""inline""
}}}
It checks whether ""display"" style equals ""inline"" but it gets ""none"".[[BR]]
I don't know what should be the proper way to fix it or even if it should be fixed, but I thought I should report it.",Animate width of hidden inline element
bug,9628,1,css,1.6.1,None,2011-06-20T21:38:25Z,2013-03-01T17:51:58Z,"Right now we're rounding off the answers from width(), height(), etc. to the nearest pixel - this makes it hard to do good positioning of elements (especially for animations). For example if you have 3 items that are width 33% inside of a 100px element we're returning 33px for each element. Theoretically an animation method might be able to return a more interesting result if they know that there are extra fractional-numbers getting rounded off.

I got a report on this directly from Mozilla but I agree with them that this particular change makes it hard to get to good numbers.

See also: #3239.","width(), height(), etc. shouldn't round"
bug,10550,1,attributes,1.6.4,None,2011-10-20T19:39:15Z,2013-03-15T13:59:10Z,"The current code to clone the checked state of an input[type=checkbox] is as follows:

{{{
if ( src.checked ) {
  dest.defaultChecked = dest.checked = src.checked;
}
}}}

This does not work in IE9 as setting object.checked = true does not actually check the object, but simply sets that property on the object as true.  To set the checkbox to true, you need to use 
{{{
object.setAttribute('checked','checked').
}}}

I have written a patch, and a test which fails under IE9 for this, and will submit a pull request shortly and link to it from this ticket.

Matt
",clone does not transfer checked state for input[type=checkbox] in IE9
bug,12974,1,css,1.8.3,None,2012-11-28T00:11:48Z,2013-05-21T07:17:20Z,"I am receiving inconsistent results between browsers when using $('html').outerHeight(true). My goal is to retrieve the actual rendered height of the document. I am avoiding $(document).height() because if the rendered height is smaller than the window height, the window height is returned. On firefox, $('html').outerHeight(true) works correctly, but on IE8 the window height is always returned. Observe using the example at:

[http://jondufresne.org/test.html]

If I run this in Firefox I see:

{{{
window:561
document:1044
html:1044
body:1028
}}}

Notice the html height matches the document height.

If I run this in IE8 I see:

{{{
window:806
document:1272
html:810
body:1256
}}}

Notice the height (approx) matches the window height and not the document height.",$('html').outerHeight(true) returns inconsistent results across browsers
bug,13428,1,event,1.9.1,None,2013-02-10T19:53:43Z,2013-04-10T12:44:19Z,"http://fiddle.jshell.net/rvX5Y/4/

{{{
$('input').on('focus', function(event, extra, data) {
    console.log(extra, data);
});
$('input').trigger('focus', ['extra', 'data']);
}}}

Works in version 1.8.3.

Does not work in version 1.9.0 and 1.9.1.

Expected behavior: Console shows ""extra data""

False Behavior: Console shows ""undefined undefined""

Browser: Firefox 18,
OS: OS X 10.8.2",focus event ignores additional data when triggered
bug,13450,1,ajax,1.9.0,None,2013-02-13T18:36:59Z,2013-05-02T20:37:47Z,"Press Ctrl+Shift+K in Mozilla Firefox to bring up the developer console.
Don't use F12 in Firebug.
{{{
<?php

function main() {
?>
<script src=""jquery-1.9.0.js""></script>
<input type=""button"" id=""moo"" value=""meow"">
<script>
$('#moo').on('click', function() {
  $.post('?op=test', { id: '2' });
});
</script>
<?php
}

function meow() {
  header('Content-Type:');
}

switch($_GET['op']) {
  case ""test"":
    meow();
    break;
  default:
    main();
    break;
}

?>
}}}
You will notice the console say ""no element found"".","""no element found"" in Firefox when $.post reply has no Content-Type"
feature,10190,2,ajax,1.6.3,1.next,2011-09-02T05:40:01Z,2012-10-16T00:16:54Z,"There is a ""'''upload'''"" property in the xhr object returned by new XMLHttpRequest() in supported browser.
But the object returned by $.ajax() seems didn't contain this property.
This property is important to get the state of file upload progress.","""upload"" property of the XMLHttpRequest"
feature,13801,1,core,1.9.1,1.10,2013-04-20T18:01:57Z,2013-05-22T13:48:30Z,"#9469 made a good (and ultimately successful) case for deprecating the `selector` property because of its needlessness and inherent unreliability. We should do the same with its sibling property `context` for exactly the same reasons.

Cf. [https://github.com/jquery/jquery/pull/1249], closed because `context` is still [http://api.jquery.com/context/ publicly documented].",Deprecate context property
feature,12723,1,css,git,2.next,2012-10-14T10:34:14Z,2013-04-29T15:57:53Z,"Prompted by rwaldron's comment here: https://bugzilla.mozilla.org/show_bug.cgi?id=797029#c10 , this discussion happened: http://lists.w3.org/Archives/Public/www-style/2012Oct/0364.html

Which discusses the addition of a new global CSS value keyword called ""default"", which is like ""initial"", except it takes the elements default attributes into consideration.

Instead of doing defaultDisplay to figure out what to set display to for .show(), we can simply do: ""display: default"". This would have the added benefit of not showing elements whose default display is actually ""none"", like script tags or style tags or input type=hidden tags. ","Consider using ""display: default"" (once implemented) to circumvent the defaultDisplay code path"
feature,12031,1,event,1.7.2,None,2012-07-06T15:31:59Z,2012-09-10T13:01:02Z,"Doing OOP with jQuery events requires a lot of $.proxy boilerplate. the .addEventListener interface allows passing
an object as a handler like so:


{{{
function SomeWidget( elem ) {
	this.elem = elem;
}

SomeWidget.prototype = {
	constructor: SomeWidget,

	renderTo: function( target ) {
		$(target).append(this.elem);
		this.elem.addEventListener( ""click"", this );
		this.elem.addEventListener( ""mousemove"", this );
	},

	mousemove: function( e ) {

	},

	click: function( e ) {

	},

	handleEvent: function( e ) {
		return this[e.type].apply( this, arguments );
	}
};
}}}

With jQuery you have to do this:


{{{
function SomeWidget( elem ) {
	this.elem = elem;
	//Each method needs to be bound to the instance. This also has overhead of creating many functions.
	this.mousemove = $.proxy( this.mousemove, this );
	this.click = $.proxy( this.click, this );
}

SomeWidget.prototype = {
	constructor: SomeWidget,

	renderTo: function( target ) {
		$(target).append(this.elem);
		$(this.elem).on( {
			click: this.click,
			mousemove: this.mousemove
		});
	},

	mousemove: function( e ) {

	},

	click: function( e ) {

	}
};
}}}

With jQuery supporting objects as event handlers, it would work like:


{{{
function SomeWidget( elem ) {
	this.elem = elem;
}

SomeWidget.prototype = {
	constructor: SomeWidget,

	renderTo: function( target ) {
		$(target).append(this.elem);
		$(this.elem).on( ""click mousemove"", this );
	},

	mousemove: function( e ) {

	},

	click: function( e ) {

	},

	handleEvent: function( e ) {
		return this[e.type].apply( this, arguments );
	}
};
}}}

And that's it. No $.proxy hacks, no redundant creation of functions just to retain binding.


",Allow objects as event handlers