opacity

[Darko]

Hi,

I'm trying to get and set an element's opacity, but I'm stuck with,
what a hell of surprise, Internet Explorer. As for getting the
element's opacity, I have the following (not working) lines of code:

if ( targetObject.fi lters && targetObject.fi lters.length 0 )
opacity =
targetObject.fi lters.item("DXI mageTransform.M icrosoft.Alpha" ).Opacity;

Setting it, I tried:

if ( targetObject.fi lters && targetObject.fi lters.length 0 )
targetObject.se tAttribute( "style", "filter: alpha(opacity=" +
opacity + ")" );

None work. I have digged these out from some MSDN article, but they
aren't working, at least they don't work in to me available IE 6.0. Do
you have better (i.e. working) ways of yours?

Thanks

Darko

[Stevo]

Darko wrote:

I'm trying to get and set an element's opacity, but I'm stuck with,
what a hell of surprise, Internet Explorer. As for getting the
element's opacity, I have the following (not working) lines of code:

I don't know what was wrong there, but I see you think that opacity is
only available for IE. There's an equivalent feature in Mozilla browsers
using custom CSS properties. You'll have to sniff for the browsers and
branch your code to handle it (totally) differently, but it's definitely
possible. Not that I've ever used it, but I have seen itt.

[VK]

On Nov 19, 10:38 pm, Darko <darko.maksimo. [e-mail] te:

As for getting the
element's opacity, I have the following (not working) lines of code:

if ( targetObject.fi lters && targetObject.fi lters.length 0 )
opacity =
targetObject.fi lters.item("DXI mageTransform.M icrosoft.Alpha" ).Opacity;

Setting it, I tried:

if ( targetObject.fi lters && targetObject.fi lters.length 0 )
targetObject.se tAttribute( "style", "filter: alpha(opacity=" +
opacity + ")" );

None work. I have digged these out from some MSDN article

Do you still remember which one?

but they
aren't working, at least they don't work in to me available IE 6.0.

Of course they don't: setAttribute method has nothing to do with it.

Do you have better (i.e. working) ways of yours?

Not mine, but tested working:

http://www.quirksmode.org/js/opacity.html

[Stevo]

VK wrote:

Not mine, but tested working:
http://www.quirksmode.org/js/opacity.html

I knew I'd seen it somewhere :)

[Thomas 'PointedEars' Lahn]

VK wrote:

On Nov 19, 10:38 pm, Darko <darko.maksimo. [e-mail] te:

>As for getting the
element's opacity, I have the following (not working) lines of code:

if ( targetObject.fi lters && targetObject.fi lters.length 0 )
opacity =
targetObject.f ilters.item("DX ImageTransform. Microsoft.Alpha ").Opacity;

Setting it, I tried:

if ( targetObject.fi lters && targetObject.fi lters.length 0 )
targetObject.se tAttribute( "style", "filter: alpha(opacity=" +
opacity + ")" );

None work. I have digged these out from some MSDN article

Do you still remember which one?

Probably
http://msdn2.microsoft.com/en-us/lib...ipting_Filters or
a previous version.

>but they
aren't working, at least they don't work in to me available IE 6.0.

Of course they don't: setAttribute method has nothing to do with it.

To be precise, setAttribute() does not seem to work there *for IE*.

>Do you have better (i.e. working) ways of yours?

Not mine, but tested working:

http://www.quirksmode.org/js/opacity.html

However, it does not make sense in passing ranges from 0 to 10 and then
computing the required value twice. With the division for `opacity', there
is even a rounding error involved, needlessly. It makes more sense have
`value' range from 0 to 1 (thereby to pass the percentage x% as 0.0x to the
function); the computation will have to be done only once (for `filter'),
and the used values will be as exact as the layout engine allows it:

function setOpacity(valu e)
{
testObj.style.o pacity = value;
testObj.style.f ilter = 'alpha(opacity= ' + value * 100 + ')';
}
PointedEars
--
Prototype.js was written by people who don't know javascript for people
who don't know javascript. People who don't know javascript are not
the best source of advice on designing systems that use javascript.
-- Richard Cornford, cljs, <f8************ *******@news.de mon.co.uk>

[dhtmlkitchen]

On Nov 19, 11:38 am, Darko <darko.maksimo. [e-mail] te:

Hi,

I'm trying to get and set an element's opacity, but I'm stuck with,
what a hell of surprise, Internet Explorer. As for getting the
element's opacity, I have the following (not working) lines of code:

if ( targetObject.fi lters && targetObject.fi lters.length 0 )
opacity =
targetObject.fi lters.item("DXI mageTransform.M icrosoft.Alpha" ).Opacity;

Setting it, I tried:

if ( targetObject.fi lters && targetObject.fi lters.length 0 )
targetObject.se tAttribute( "style", "filter: alpha(opacity=" +
opacity + ")" );

None work. I have digged these out from some MSDN article, but they
aren't working, at least they don't work in to me available IE 6.0. Do
you have better (i.e. working) ways of yours?

Does the element have a layout? In IE terms, it's gotta have position
or height/width for proprietary hasLayout to be be true.

DXImageTransfor m can work for background images, too, but doesn't let
you set any other background-properties (like background-position).

Regarding other comments on this thread: Opacity is CSS3, not a moz-
specific css. it works in Mozilla, Webkit and Opera.

Garrett

Thanks

Darko

[Darko]

On Nov 20, 4:03 pm, Stevo <[e-mail]:

Darko wrote:

I'm trying to get and set an element's opacity, but I'm stuck with,
what a hell of surprise, Internet Explorer. As for getting the
element's opacity, I have the following (not working) lines of code:

I don't know what was wrong there, but I see you think that opacity is
only available for IE. There's an equivalent feature in Mozilla browsers
using custom CSS properties. You'll have to sniff for the browsers and
branch your code to handle it (totally) differently, but it's definitely
possible. Not that I've ever used it, but I have seen itt.

No, I don't think that. I use "opacity" regularly for other browsers,
but
it doesn't work with IE. So I googled out that IE needs this filter
thing,
which they claim works by accessing .filters subobject, but it seems
as if it
does not. So I gave up and did as it was only possible, using
..style.filter = ..., which I like less than the proposed solution from
MSDN
(which doesn't work). Never mind.

[Darko]

On Nov 19, 8:38 pm, Darko <darko.maksimo. [e-mail] te:

Hi,

I'm trying to get and set an element's opacity, but I'm stuck with,
what a hell of surprise, Internet Explorer. As for getting the
element's opacity, I have the following (not working) lines of code:

if ( targetObject.fi lters && targetObject.fi lters.length 0 )
opacity =
targetObject.fi lters.item("DXI mageTransform.M icrosoft.Alpha" ).Opacity;

Setting it, I tried:

if ( targetObject.fi lters && targetObject.fi lters.length 0 )
targetObject.se tAttribute( "style", "filter: alpha(opacity=" +
opacity + ")" );

None work. I have digged these out from some MSDN article, but they
aren't working, at least they don't work in to me available IE 6.0. Do
you have better (i.e. working) ways of yours?

Thanks

Darko

As for opacity, now that I gave in and had it .style.filter = "...",
it finally
works well with IE, too. Another problem though - Konqueror. It seems
to ignore:
opacity
-moz-opacity
-khtml-opacity
filter

Wtf. does it need? Does Konqueror actually support element's opacity?
I wouldn't mind
the bloody Konqueror not working properly with my site, but as I
understand Safari uses
the same KHTML engine, so I reckon if Konqueror doesn't work (as it
doesn't), then Safari
won't neither. Am I right? Or Safari uses a KHTML branch that actually
supports the standard?

Thanks

[Peter Michaux]

On Dec 4, 11:47 pm, David Mark <dmark.cins...@ gmail.comwrote:

On Dec 4, 8:22 pm, Peter Michaux <petermich...@g mail.comwrote:

On Dec 4, 12:17 am, dm...@cinsoft.n et wrote:

On Nov 21, 4:35 pm, Peter Michaux <petermich...@g mail.comwrote:

[snip]

// if (early release edition of Firefox && val === 1) {
// // This trick is from Scriptaculous
// // Some version of Firefox (before 1.5?) flickers

I've seen this recently. It drove me to distraction while I was
working on a special effects module. I don't think it was an early
release though. I am pretty sure it was the latest major release.

I've never managed to make it flicker on any version.

It only seems to happen when animating the opacity with a timer and
only when starting from 1. Start from .99999 or whatever and it goes
away. I eventually changed the timing of something and got it worked
out of my effects module without resorting to the .99999 hack.

// // when animatingopacit yup to a value of 1.
// // If this trick is to be used the test will probably be
// // expensive and should only be preformed the first time.
// //
// // Apparently using this trick increases the weight of
// // the DOM, for rendering speed?

I am not sure what that means, but as I recall, setting .999999
instead of 1 makes no visible difference, other than to eliminate the
annoying flicker.

Someone told me or I read that by setting several elements with
opacity makes the DOM "heavier". I can only assume they mean it takes
longer to render or that it takes more RAM or something like that. The
idea of limiting this 0.99999 trick to only the versions of FF that
need it was to avoid adding this "weight" to browsers that don't need
the trick. The importance given to this "weight" issue sounded a
little like flaky to me.

I think it does take a little more work to render a semi-transparent
element, but the idea of using .999999 in lieu of 1 is silly.

I believe the flicker issue included animating from an opacity below 1
up to 1 in which case the animation needed to stop before 1. I can't
say this is silly.

[snip]

For the most part it does. Doing it for table rows or groups of table
rows would seem an odd thing to do anyway. Add a disclaimer about
table rows at the top and you are done. Feel free to add it to your
repository.

I'm starting a branch for opacity. I think it will serve as a good
first DHTML example.

Peter

[Peter Michaux]

On Dec 7, 11:59 am, Peter Michaux <petermich...@g mail.comwrote:

Yes by using this wrapper it would allow someone to write an
implementation like this.

function myApply(obj, f) {
obj._temp = f;
// some number of arguments
obj._temp(args, arguments[1], arguments[2],
arguments[3], arguments[4]);
delete obj._temp;

}

Never mind the bugs :)

--
Peter
Code Worth Recommending Project
http://cljs.michaux.ca/trac