594299 - (d3d9-layers)inFlasher doesn't flash

Status: RESOLVED INVALID

(Other Applications :: DOM Inspector, defect)

Description

[Alice0775 White]

Build Identifier: Mozilla/5.0 (Windows torNT 6.1; WOW64; rv:2.0b6pre)
Gecko/20100907 Firefox/4.0b6pre ID:20100907041859

inIFlasher doesn't flash.
If I set layers.accelerate-all to false, it works.


Reproducible: Always

Steps to Reproduce:
1. Start Minefield with new profile
2. Install DOM inspector ( https://addons.mozilla.org/ja/firefox/addon/6622/ )
3. Inspect any element

Actual Results:
 inIFlasher doesn't flash

Graphics

Adapter Description: ATI Radeon HD 4300/4500 Series
Vendor ID: 1002
Device ID: 954f
Adapter RAM: 512
Adapter Drivers: aticfx64 aticfx64 aticfx32 aticfx32 atiumd64 atidxx64 atiumdag
atidxx32 atiumdva atiumd6a atitmm64
Driver Version: 8.762.0.0
Driver Date: 8-3-2010
Direct2D Enabled: true
DirectWrite Enabled: true
GPU Accelerated Layers Enabled: 1/1  Direct3D 9

Comment 1

[Alice0775 White]

According to https://wiki.mozilla.org/Platform/2010-09-07#Firefox_Development,
Implement of Inspector was dropped from Firefox 4.

So, I think this should be fixed before release of Firefox4.

Comment 2

[Colby Russell :crussell (no longer Mozilla-ing)]

Eh?  Two things:
a) The devtools inspector (https://wiki.mozilla.org/Firefox/Projects/Inspector) uses a different method for its highlighter; it's not inFlasher.
b) Even if it were the case that the devtools inspector did use inFlasher, the fact that it was dropped from Firefox 4 would imply that this shouldn't be blocking, *not* that it should be...

Comment 3

[Shawn Wilsher :sdwilsh]

(In reply to comment #2)
> Eh?  Two things:
> a) The devtools inspector (https://wiki.mozilla.org/Firefox/Projects/Inspector)
> uses a different method for its highlighter; it's not inFlasher.
> b) Even if it were the case that the devtools inspector did use inFlasher, the
> fact that it was dropped from Firefox 4 would imply that this shouldn't be
> blocking, *not* that it should be...
Note that this is new breakage on a platform that inIFlasher actually worked on - windows.  This isn't really the same as bug 368608.

Comment 4

[Colby Russell :crussell (no longer Mozilla-ing)]

(In reply to comment #3)
> Note that this is new breakage on a platform that inIFlasher actually worked on
> - windows.  This isn't really the same as bug 368608.

The effect is the same though, right?  "Rewrite DOM Inspector's flasher"?  The platform fields for that bug are already All/All.

Comment 5

[Shawn Wilsher :sdwilsh]

(In reply to comment #4)
> The effect is the same though, right?  "Rewrite DOM Inspector's flasher"?  The
> platform fields for that bug are already All/All.
It's not clear to me that that is the case.

Comment 6

[Alice0775 White]

This is about Extention DOMi's  blinking feature.

I think this is not bug 368608 completely.
Because, Blinking of DOMi works before enabling D3D9.
And It still works if I disabled D3D9.

Comment 7

[Alice0775 White]

This is regression, 
is this block 2.0?

Comment 9

[Phillip]

Has this been fixed in nightly builds or preview releases?

I can confirm that unchecking "User hardware acceleration when available" is a workaround if blinking is not working. My video card is NVIDIA GeForce 9500 GS. I am developing a web application that heavily utilizes Canvas and SVG so I would much prefer not to have to disable hardware acceleration. Is there are less drastic workaround?

Comment 11

[Alice0775 White]

Flasher in DOMi was rewrited in Nightly 33.0a1

So, this bug is obsoleted.

Comment 12

[Alice0775 White]

s/rewrited/rewritten/