Embedded swf and Firefox Scrolling issue on .aspx page

[rajs8566510]

Hello,

I have a swf file - AS2 (old one). I have embedded that with .aspx page and output from SQL database will be displayed on that SWF file.

It works fine with IE and Chrome but FF has an issue. When I use mouse wheel to go up and down the swf image will disappear until I done the scrolling.

Any solution? Please help.

Thank you !

[jeromiec83223024]

Sounds like a browser-related drawing bug.  It's hard to say without actually debugging it.  Nothing is jumping out at me from your snippet.

A URL that demonstrates the problem and some basics like Operating System and browser version would also be helpful.

[rajs8566510]

Thank you. I have a dynamic graph display on my page. Once I scroll down or up the page by pressing mouse wheel, the graph disappears for a second (until I release mouse wheel).

OS: WIN 10

Browser: 52.8.1 (32-bit)

Flash player: 30.0.0.113

Thank you!

[jeromiec83223024]

That doesn't help me.  I really need to be able to run it under a C++ debugger in order to understand what's going on.

[rajs8566510]

It looks like I have similar issue that mentions here:

1212813 - [e10s] Flash plugin windows flicker on and off during scrolling

Has this bug already addressed?

thanks!

[rajs8566510]

This is an exact issue that I'm facing:

Flash player scroll bug with videos

I tried based on your reply but no luck.

[jeromiec83223024]

For Mozilla 1212813, it's Mozilla's bug, and they marked it WONTFIX.

Again, I'd really need to be able to debug it under a C++ debugger to understand why it's failing and either report it to Mozilla with a root-cause analysis, or get it fixed on our end.  I would not assume that just because issues described in bugs and forum posts sound similar to the issue that you're experience, that they have the same cause.

This *isn't* a widespread issue that I'm aware of, so it's interesting.  Given the behavior you're describing, it's probably a Firefox bug, but I don't have enough evidence to back that up.  It's also possible that there's a problem with your implementation (I find this reasonably unlikely) or maybe it's a GPU driver issue.

Without the ability to reproduce the issue we're just guessing, and that's not going to get anything resolved.