Just read your bug report on the firefox site and got a bit more clarity on your problem. I think what will ultimately fix it for you is changing the .CLICK to .MOUSE_DOWN. My scenario was almost identical to yours upon further review.

Hope this helps!

i too can confirm this annoying bug!

this code:

package {
import dk.esk.display.Square;

import flash.display.Sprite;
import flash.events.MouseEvent;

public class mouseevents extends Sprite {

//constructor
public function mouseevents() {
var button:Square = new Square(100, 100); //this is just a sprite with a rect graphic that has a width of 100 and a height of 100

addChild(button);

button.addEventListener(MouseEvent.MOUSE_OVER, over);
button.addEventListener(MouseEvent.MOUSE_OUT, out);
button.addEventListener(MouseEvent.MOUSE_DOWN, click);
}

//private methods
private function over(e:MouseEvent):void {
trace("OVER");
}

private function out(e:MouseEvent):void {
trace("OUT");
}

private function click(e:MouseEvent):void {
trace("Click");
}
}
}

also traces:
CLICK
OUT
OVER

when i click the button.

i did add: object { outline:none; }, it doesn't work.
i did try with ROLL_OVER and ROLL_OUT, it doesn't work.

Really really strange!! Anybody found a temporary hack? I have opened posts on both Kirupa.com and gotoandlearn.com, hoping to attract some other people with the same issues

This is very annoying. We had this problem with one of our major projects. Here is what I did as a work around:

I created a private variabled called _isClickEvent and typed it as a Boolean. Then in my clickHandler I wrote _isClickEvent = true; Then in the mouseOutHandler I wrote if (_isClickEvent) {_isClickEvent = false; return;} . Not the prettiest solution but it did the trick. Basically what I am doing is setting a Boolean to true in the click handler, then in the outHandler which gets fired right away (for no reason) I catch it and return the method, leaving all the code intact for when we actually call it.

Hope this helps some people. Sorry if any of my spelling is wrong, still working, quick post

Hej.

http://bugs.adobe.com/jira/browse/FP-4145

+ http://groups.google.com/group/ruflash/browse_thread/thread/c9a239638e7ecd0d here's approx translation:

Subject: several bugs FP10 in FF under Mac
...
2. Haven't posted yet.
*link*
Switch several times between BY TIME and BY SIZE at the bottom. I see rendering bugs in FF like http://dl.dropbox.com/u/5334698/Picture%201.png (pieces of objects) It's OK under Safari. In FF it's also OK in fullscreen mode or with wmode direct or gpu...

3. Affecting ActionScript. CallLater call sometimes doesn't work (custom function, but the algorithm seems correct) *code below*

And the thing is — all 3 bugs are can "be cured" by entering fullscreen mode. So, maybe they all have one cause.

The click bug also presents under some browsers on PC, but I can't check.. and people seems can't really get the bug =| If the click bug is more annoying, then second & third are quite critical to user experience I would say!

That would be awesome!