Hi,
If I remember correctly, Firefox has an issue with opacity at '1' - I
guess I assumed that it was the case in more browsers. I'll add
another catch in to fix it (sigh)
Have you ever thought about using deans object-Detection-tip for things like
this:
Joel Birch schrieb:
In Mac Firefox, when an element is anything other than opacity:1, the
text is rendered 'thinner' or lighter in weight. This means that, for
example, when you fadeUp, text is 'light' in weight until opacity:1
is reached. The transition from opacity:.999 to opacity:1
Joel Birch schrieb:
In Mac Firefox, when an element is anything other than opacity:1, the
text is rendered 'thinner' or lighter in weight. This means that, for
example, when you fadeUp, text is 'light' in weight until opacity:1
is reached. The transition from opacity:.999 to opacity:1
Sounds like a float rounding error...
no, this is by design, from source:
if (z.now == 1) z.now = 0.;
I only wonder why...
-- Klaus
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
no, this is by design, from source:
if (z.now == 1) z.now = 0.;
I only wonder why...
If I remember correctly, Firefox has an issue with opacity at '1' - I
guess I assumed that it was the case in more browsers. I'll add
another catch in to fix it (sigh)
Here's the ticket for it:
In Mac Firefox, when an element is anything other than opacity:1, the
text is rendered 'thinner' or lighter in weight. This means that, for
example, when you fadeUp, text is 'light' in weight until opacity:1
is reached. The transition from opacity:.999 to opacity:1 is very
noticeable as
Sounds like a float rounding error...
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
