I think that IE just responds to the second line setting the
filter:alpha() stuff. So in IE it should be rather unimportant if you
set opacity to 1 or 0.9999999999
This line seems to be for Mozilla.
But since Opera 9 this line is not correct anymore, since Opera
unlike other browsers, does not change the opacity value if set to null.
So this line should set the value to 0.999999 for Mozilla, null for
Safari and 1 fo Opera. 1 would be o.k. for Safari also, in my opinion.
Lorenz
On 22.08.2006, at 15:15, Brandon Aaron wrote:
>
>> I take back what I said about IE needing a value of 1.
>
> That should say... I take back what I said about IE needing a value of
> .99999 instead of 1.
>
> Brandon
>
> On 8/22/06, Brandon Aaron <[EMAIL PROTECTED]> wrote:
>> I take back what I said about IE needing a value of 1. I get the
>> white
>> spots/pixels in what seems to be only pure black areas no matter what
>> value I use.
>>
>> On 8/22/06, Brandon Aaron <[EMAIL PROTECTED]> wrote:
>>> It doesn't just do it on floated elements though. My element is
>>> positioned absolute. I haven't had the time to produce some unit
>>> tests. However, I have figured out that you do not want to set the
>>> opacity to .99999 instead of 1 for IE or you will get white spots in
>>> images with pure black. Mozilla/Firefox is the only one that needs
>>> .99999 instead of 1. All the other browsers need a non null value.
>>>
>>> Brandon
>>>
>>> On 8/22/06, Lorenz Knies <[EMAIL PROTECTED]> wrote:
>>>>
>>>> It seems to be a rendering bug in Safari related to the float:left
>>>> style.
>>>> Try Effect.Appear in the script.aculo.us demo. The DIV appears
>>>> correctly, then 'disappears'. Now just do a tiny resize on the
>>>> window
>>>> and the DIV is there again.
>>>> I would say this is a bug.
>>>>
>>>> Lorenz
>>>>
>>>> On 18.08.2006, at 15:08, Brandon Aaron wrote:
>>>>
>>>>> Sure I'll create some unit tests.
>>>>>
>>>>> Brandon
>>>>>
>>>>> On 8/18/06, Thomas Fuchs <[EMAIL PROTECTED]> wrote:
>>>>>> I think we should make a test case page for this, that has all
>>>>>> sorts
>>>>>> of opacity enabled/disabled elements
>>>>>> and see if everything works fine. Any volunteers? :)
>>>>>>
>>>>>> -Thomas
>>>>>>
>>>>>> Am 18.08.2006 um 09:42 schrieb Lorenz Knies:
>>>>>>
>>>>>>> Hi Brandon,
>>>>>>>
>>>>>>> I,ve had the same issue with opera.
>>>>>>> I changed the line like this without any problems so far:
>>>>>>>
>>>>>>> Element.setStyle(element, { opacity:
>>>>>>> (/Gecko/.test(navigator.userAgent) &&
>>>>>>> !/Konqueror|Safari|KHTML/.test(navigator.userAgent)) ?
>>>>>>> 0.999999 : null });
>>>>>>>
>>>>>>> to
>>>>>>>
>>>>>>> Element.setStyle(element, { opacity:
>>>>>>> (/Gecko/.test(navigator.userAgent) &&
>>>>>>> !/Konqueror|Safari|KHTML/.test(navigator.userAgent)) ?
>>>>>>> 0.999999 : 1 });
>>>>>>>
>>>>>>> Perhaps this works for Safari too.
>>>>>>>
>>>>>>> Lorenz
>>>>>>>
>>>>>>> On 16.08.2006, at 15:40, Brandon Aaron wrote:
>>>>>>>
>>>>>>>> I've been putting this off for several days now, waiting to
>>>>>>>> check
>>>>>>>> dev.rubyonrails.org before I posted here but it is still down.
>>>>>>>>
>>>>>>>> I am using Effect.Appear and it is working great except in
>>>>>>>> Safari
>>>>>>>> where it fades in and then disappears. I traced it back to the
>>>>>>>> Element.setOpacity function. Is there a reason why Safari is
>>>>>> singled
>>>>>>>> out and given a null value for opacity instead of 1 or
>>>>>> 0.999999? This
>>>>>>>> is where the problem is happening and can be seen directly from
>>>>>> the
>>>>>>>> demo page itself
>>>>>>>> (http://wiki.script.aculo.us/scriptaculous/show/
>>>>>>>> CombinationEffectsDemo).
>>>>>>>> I simply changed this line:
>>>>>>>>
>>>>>>>> Element.setStyle(element, { opacity:
>>>>>>>> (/Gecko/.test(navigator.userAgent) &&
>>>>>>>> !/Konqueror|Safari|KHTML/.test(navigator.userAgent)) ?
>>>>>>>> 0.999999 : null });
>>>>>>>>
>>>>>>>> to this:
>>>>>>>>
>>>>>>>> Element.setStyle(element, { opacity: 0.999999 });
>>>>>>>>
>>>>>>>> And this working perfectly for me in Safari 2 and 1.3 and it
>>>>>> didn't
>>>>>>>> hurt any of the other supported browsers. I don't have 1.2 to
>>>>>> test it
>>>>>>>> in.
>>>>>>>>
>>>>>>>> However, I believe that Element.setStyle should have the
>>>>>>>> responsiblity
>>>>>>>> of normalizing special cases like opacity. More details here:
>>>>>>>> http://www.brandonaaron.net/articles/2006/08/12/effect-appear-
>>>>>>>> safari-fix
>>>>>>>>
>>>>>>>> Brandon
>>>>>>>> _______________________________________________
>>>>>>>> Rails-spinoffs mailing list
>>>>>>>> [email protected]
>>>>>>>> http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Rails-spinoffs mailing list
>>>>>>> [email protected]
>>>>>>> http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
>>>>>>
>>>>>> --
>>>>>> Thomas Fuchs
>>>>>> wollzelle
>>>>>>
>>>>>> http://www.wollzelle.com
>>>>>>
>>>>>> questentier on AIM
>>>>>> madrobby on irc.freenode.net
>>>>>>
>>>>>> http://www.fluxiom.com :: online digital asset management
>>>>>> http://script.aculo.us :: Web 2.0 JavaScript
>>>>>> http://mir.aculo.us :: Where no web developer has gone before
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Rails-spinoffs mailing list
>>>>>> [email protected]
>>>>>> http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
>>>>>>
>>>>> _______________________________________________
>>>>> Rails-spinoffs mailing list
>>>>> [email protected]
>>>>> http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
>>>>
>>>>
>>>>>>>
>>>>
>>>
>>
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---
