I've run into a number of gnarly issues in IE 8 and earlier where
jQuery leaves a residual alpha filter on elements after fading them
back in. Some of the IE bugs are annoying like odd aliasing around
text, etc. This morning though I came across a really nasty bug
whereby it seemed like IE was lock
...;
> return {
> top: top, right: right, bottom: bottom, left: left,
> 0: top, 1: right, 2: bottom, 3: left,
> toString: function() { return [top, right, bottom, left].join(' '); }
>
> };
>
> ~Daniel Friesen (Dantman, Nadir-Seen-Fire)
>
> Stephen Mc
this method can determine if it is compound or not based upon if it is
handed a collection or scalar value. Then the method using the value
can grab the appropriate piece of information and not need to re-
implement the parsing/retrieval logic.
On May 7, 9:51 am, Stephen McKamey wrote:
> Yes,
Yes, I agree that the use-case is in question. We ran into this when
a using the autogrow plugin:
http://plugins.jquery.com/project/autogrow
This plugin should be modified to check the appropriate sides and
handle correctly.
On the other hand, I don't think that crashing is an appropriate
We've run into an issue where, when a style ("padding" in this case)
with multiple parts ("5px 3px" in this case) is being set by a
stylesheet (rather than inline) is accessed in IE6/7/8, jQuery 1.3.2
causes the exception "Error: Invalid argument." The exception is
thrown in the middle of "the aw
I've spent way too long on this, but I was convinced that it was a bug
and I wanted to know if it was in my code, jQuery, or Google Chrome.
I've managed to factor out all of "my code" and all that is left is
this tiny little snippet which dies only on Google Chrome. Do I have
some syntactical iss
