[Prototype-core] Element.setOpacity have a strange behaviour on prototype 1.6.1RC2

2009-05-13 Thread david
The original setOpacity function just reset the opacity value in case the value is one. Which means that you use the class value (if exist) : setOpacity: function(element, value) { element = $(element); element.style.opacity = (value == 1 || value === '') ? '' : (value 0.1)

[Prototype-core] Re: Element.setOpacity have a strange behaviour on prototype 1.6.1RC2

2009-05-13 Thread Tobie Langel
Have you tried running the unit tests in all browsers with your changes? On May 13, 12:32 pm, david david.brill...@gmail.com wrote: The original setOpacity function just reset the opacity value in case the value is one. Which means that you use the class value (if exist) :   setOpacity:

[Prototype-core] Re: Element.setOpacity have a strange behaviour on prototype 1.6.1RC2

2009-05-13 Thread david
Hi tobie, one click install for Window seems good, and it didn't seems to complicate after, I just look the documentation in the prototype website. I just make some research on the net, and i found VirtualBox, for testing on different OS version and browser. Is it the good choice, or is there a

[Prototype-core] Re: Element.setOpacity have a strange behaviour on prototype 1.6.1RC2

2009-05-13 Thread Simon Charette
Virtual Box is fine. You should have no problems testing many Windows and linuxes distros. I've not tried with Mac and you might have to get another virtualisation tool and get a Special Version of Mac OS since Mr. Jobs doesn't allow Mac software running on non-Mac hardware. Anyway, thats the