Flicker

Doesn't anyone have a suggestion for the IE6 flicker problem when mousing
over menus quickly?

I tried the Javascript solution I found but it didn't work. It was to put
this in the area.



--
Shelly

Re: Flicker

Shelly wrote:

> Doesn't anyone have a suggestion for the IE6 flicker problem when mousing
> over menus quickly?
>
> I tried the Javascript solution I found but it didn't work. It was to put
> this in the area.

Glue the two images together, and just set the background-position to
change on hover. That way IE6 doesn't fetch the image every time you
mouse over it.

--
Els http://locusmeus.com/

Re: Flicker

Els wrote:
> Shelly wrote:
>
>> Doesn't anyone have a suggestion for the IE6 flicker problem when
>> mousing over menus quickly?
>>
>> I tried the Javascript solution I found but it didn't work. It was
>> to put this in the area.
>
> Glue the two images together, and just set the background-position to
> change on hover. That way IE6 doesn't fetch the image every time you
> mouse over it.

What two images?
What do you mean by "glue"?

I have a menu on the side with three menu items. When clicked, two of them
expand into submenus. (This problem is also there for the submenus). Each
submenu has a hyperlink. Moving the mouse rapidly up and down causes the
flicker of the entire screen. The menu items are nothing more than text
with a background. The colors change on hover. So, I don't know what you
mean with "glue the two images".

--
Shelly

Re: Flicker

Shelly wrote:
> Els wrote:
>> Shelly wrote:
>>
>>> Doesn't anyone have a suggestion for the IE6 flicker problem when
>>> mousing over menus quickly?
>>>
>>> I tried the Javascript solution I found but it didn't work. It was
>>> to put this in the area.
>>
>> Glue the two images together, and just set the background-position to
>> change on hover. That way IE6 doesn't fetch the image every time you
>> mouse over it.
>
> What two images?

The one you see before hovering/mousing over the menu, and the one you
see while hovering/mousing over it.

> What do you mean by "glue"?

'stick' :-)

> I have a menu on the side with three menu items. When clicked, two of them
> expand into submenus. (This problem is also there for the submenus). Each
> submenu has a hyperlink. Moving the mouse rapidly up and down causes the
> flicker of the entire screen.

Ah see, you didn't explain that in your first post, and you didn't
give a link either, so I just assumed you were talking about rollover
images, which do indeed tend to flicker on mouseover in IE6.

> The menu items are nothing more than text
> with a background. The colors change on hover. So, I don't know what you
> mean with "glue the two images".

Nothing really - forget it. I have no idea what your menu is doing. I
thought you were using images. Maybe because I saw the word
"BackgroundImageCache" in your JavaScript snippet?

If you can give a URL, someone else might see/know what is happening
and give you a solution.

--
Els http://locusmeus.com/

Re: Flicker

Els wrote:
> Shelly wrote:
>> Els wrote:
>>> Shelly wrote:
>>>
>>>> Doesn't anyone have a suggestion for the IE6 flicker problem when
>>>> mousing over menus quickly?
>>>>
>>>> I tried the Javascript solution I found but it didn't work. It was
>>>> to put this in the area.
>>>
>>> Glue the two images together, and just set the background-position
>>> to change on hover. That way IE6 doesn't fetch the image every time
>>> you mouse over it.
>>
>> What two images?
>
> The one you see before hovering/mousing over the menu, and the one you
> see while hovering/mousing over it.
>
>> What do you mean by "glue"?
>
> 'stick' :-)
>
>> I have a menu on the side with three menu items. When clicked, two
>> of them expand into submenus. (This problem is also there for the
>> submenus). Each submenu has a hyperlink. Moving the mouse rapidly
>> up and down causes the flicker of the entire screen.
>
> Ah see, you didn't explain that in your first post, and you didn't
> give a link either, so I just assumed you were talking about rollover
> images, which do indeed tend to flicker on mouseover in IE6.
>
>> The menu items are nothing more than text
>> with a background. The colors change on hover. So, I don't know
>> what you mean with "glue the two images".
>
> Nothing really - forget it. I have no idea what your menu is doing. I
> thought you were using images. Maybe because I saw the word
> "BackgroundImageCache" in your JavaScript snippet?
>
> If you can give a URL, someone else might see/know what is happening
> and give you a solution.

I did in the first post (not this thread). It is
www.festivalnetwork.com/events.php Do it in IE6. There is no problem in
IE7 and FF. To make it happen more quickly, expand the Events by Region by
clicking on it. This happens with top level and sub menus. Just move the
mouse up and down over the menu quickly.

--
Shelly

Re: Flicker

Well bust mah britches and call me cheeky, on Tue, 20 Nov 2007 19:45:37
GMT Shelly scribed:

>> If you can give a URL, someone else might see/know what is happening
>> and give you a solution.
>
> I did in the first post (not this thread). It is
> www.festivalnetwork.com/events.php Do it in IE6. There is no
> problem in IE7 and FF. To make it happen more quickly, expand the
> Events by Region by clicking on it. This happens with top level and
> sub menus. Just move the mouse up and down over the menu quickly.

I did this with some css in your stylesheet:

#SideLink a:hover {
color: #FFFFFF;
text-decoration:none;
XXpadding: 3px 0 0 0;
text-align:left;
text-indent: 5px;
}

(Notice the XX - a temp. negation) and it stopped flickering on a
downloaded copy.

--
Bone Ur
Cavemen have formidable pheromones.

Re: Flicker

Bone Ur wrote:
> Well bust mah britches and call me cheeky, on Tue, 20 Nov 2007
> 19:45:37 GMT Shelly scribed:
>
>>> If you can give a URL, someone else might see/know what is happening
>>> and give you a solution.
>>
>> I did in the first post (not this thread). It is
>> www.festivalnetwork.com/events.php Do it in IE6. There is no
>> problem in IE7 and FF. To make it happen more quickly, expand the
>> Events by Region by clicking on it. This happens with top level and
>> sub menus. Just move the mouse up and down over the menu quickly.
>
> I did this with some css in your stylesheet:
>
> #SideLink a:hover {
> color: #FFFFFF;
> text-decoration:none;
> XXpadding: 3px 0 0 0;
> text-align:left;
> text-indent: 5px;
> }
>
> (Notice the XX - a temp. negation) and it stopped flickering on a
> downloaded copy.

Awesome!!!! I thank you ever so much. I put it in exactly as you have it
above. Can you please explain in a little more detail (for my education)
just what putting XX in front does?

--
Shelly

Re: Flicker

Well bust mah britches and call me cheeky, on Tue, 20 Nov 2007 21:45:32
GMT Shelly scribed:

>>>> If you can give a URL, someone else might see/know what is
>>>> happening and give you a solution.
>>>
>>> I did in the first post (not this thread). It is
>>> www.festivalnetwork.com/events.php Do it in IE6. There is no
>>> problem in IE7 and FF. To make it happen more quickly, expand the
>>> Events by Region by clicking on it. This happens with top level and
>>> sub menus. Just move the mouse up and down over the menu quickly.
>>
>> I did this with some css in your stylesheet:
>>
>> #SideLink a:hover {
>> color: #FFFFFF;
>> text-decoration:none;
>> XXpadding: 3px 0 0 0;
>> text-align:left;
>> text-indent: 5px;
>> }
>>
>> (Notice the XX - a temp. negation) and it stopped flickering on a
>> downloaded copy.
>
> Awesome!!!! I thank you ever so much. I put it in exactly as you
> have it above. Can you please explain in a little more detail (for my
> education) just what putting XX in front does?

It's just a cheater way of removing the line from counting. Browsers don't
parse malformed css so this is like eliminating it. I wouldn't advise
publishing the page that way; remove the line or change it so it no longer
has the bad effect. -And you're quite welcome.

--
Bone Ur
Cavemen have formidable pheromones.

Re: Flicker

Bone Ur wrote:

>>> XXpadding: 3px 0 0 0;

/* padding: 3px 0 0 0; */

> It's just a cheater way of removing the line from counting. Browsers
> don't parse malformed css so this is like eliminating it. I wouldn't
> advise publishing the page that way; remove the line or change it so
> it no longer has the bad effect. -And you're quite welcome.

Using comment markers to 'remove' it is better. Doing so leaves no
doubt as to your intentions, and also protects you from next year's
browser, which might disregard /all/ CSS from that point on.

--
-bts
-Motorcycles defy gravity; cars just suck

Re: Flicker

Beauregard T. Shagnasty wrote:
> Bone Ur wrote:
>
>>>> XXpadding: 3px 0 0 0;
>
> /* padding: 3px 0 0 0; */
>
>> It's just a cheater way of removing the line from counting. Browsers
>> don't parse malformed css so this is like eliminating it. I wouldn't
>> advise publishing the page that way; remove the line or change it so
>> it no longer has the bad effect. -And you're quite welcome.
>
> Using comment markers to 'remove' it is better. Doing so leaves no
> doubt as to your intentions, and also protects you from next year's
> browser, which might disregard /all/ CSS from that point on.

I'm using a beta of Next Year's Browser. Damned think can't even *find*
this year's web sites... ;)

--
Blinky
Killing all posts from Google Groups
The Usenet Improvement Project - http://improve-usenet.org

Re: Flicker

Well bust mah britches and call me cheeky, on Wed, 21 Nov 2007 03:06:49 GMT
Beauregard T. Shagnasty scribed:

>>>> XXpadding: 3px 0 0 0;
>
> /* padding: 3px 0 0 0; */
>
>> It's just a cheater way of removing the line from counting. Browsers
>> don't parse malformed css so this is like eliminating it. I wouldn't
>> advise publishing the page that way; remove the line or change it so
>> it no longer has the bad effect. -And you're quite welcome.
>
> Using comment markers to 'remove' it is better. Doing so leaves no
> doubt as to your intentions, and also protects you from next year's
> browser, which might disregard /all/ CSS from that point on.

Agreed. I use it only for "easier" preliminary testing on browsers whose
reactions I know from experience. (Saves keystrokes.)

For any permanent change, the line should be dealt with correctly.

--
Bone Ur
Cavemen have formidable pheromones.

Re: Flicker

Bone Ur wrote:
> Well bust mah britches and call me cheeky, on Wed, 21 Nov 2007
> 03:06:49 GMT Beauregard T. Shagnasty scribed:
>
>>>>> XXpadding: 3px 0 0 0;
>>
>> /* padding: 3px 0 0 0; */
>>
>>> It's just a cheater way of removing the line from counting.
>>> Browsers don't parse malformed css so this is like eliminating it.
>>> I wouldn't advise publishing the page that way; remove the line or
>>> change it so it no longer has the bad effect. -And you're quite
>>> welcome.
>>
>> Using comment markers to 'remove' it is better. Doing so leaves
>> no doubt as to your intentions, and also protects you from next
>> year's browser, which might disregard /all/ CSS from that point on.
>
> Agreed. I use it only for "easier" preliminary testing on browsers
> whose reactions I know from experience. (Saves keystrokes.)
>
> For any permanent change, the line should be dealt with correctly.

What I normally do to eliminate a line but not remove it is to enclose it in
a /* */ set.

As far as handling it correctly, what was wrong with the line:

padding: 3px 0 0 0;

that caused it to flicker?

--
Shelly

Re: Flicker

Well bust mah britches and call me cheeky, on Wed, 21 Nov 2007 18:24:38
GMT Shelly scribed:

>>>>>> XXpadding: 3px 0 0 0;
>>>
>>> /* padding: 3px 0 0 0; */
>>>
>>>> It's just a cheater way of removing the line from counting.
>>>> Browsers don't parse malformed css so this is like eliminating it.
>>>> I wouldn't advise publishing the page that way; remove the line or
>>>> change it so it no longer has the bad effect. -And you're quite
>>>> welcome.
>>>
>>> Using comment markers to 'remove' it is better. Doing so leaves
>>> no doubt as to your intentions, and also protects you from next
>>> year's browser, which might disregard /all/ CSS from that point on.
>>
>> Agreed. I use it only for "easier" preliminary testing on browsers
>> whose reactions I know from experience. (Saves keystrokes.)
>>
>> For any permanent change, the line should be dealt with correctly.
>
> What I normally do to eliminate a line but not remove it is to enclose
> it in a /* */ set.

That's the right way to comment-out a line in the