Firefox browser window does not process WM_PRINTCLIENT message correctly on some hardware configurations




8 years ago
2 years ago


(Reporter: Andrey Ledentsov, Unassigned)


4.0 Branch
Windows Vista

Firefox Tracking Flags

(Not tracked)




8 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB6.5; .NET CLR 1.1.4322; FDM; .NET CLR 2.0.50727; OfficeLiveConnector.1.3; OfficeLivePatch.0.0; .NET CLR 3.0.04506.30; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; InfoPath.2)
Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b6) Gecko/20100101 Firefox/4.0b6

I send WM_PRINTCLIENT message to browser window and expect that it will render itself into a provided device context. On some Windows 7 and Window Vista systems it never does that.

Reproducible: Always

Steps to Reproduce:
1. My extension (xpcom component implemented in DLL) have own window,
2. when it is being drawn it sends WM_PRINTCLIENT to main browser window
to force it to draw into provided device context which is a DC of the extension's window.

Actual Results:  
browser window is not drawn in responce to WM_PRINTCLIENT message.
It happens on some systems only.

Expected Results:  
browser window must process WM_PRINTCLIENT message and draw itself into a provided device context

It does not depend on particual OS version and bits (have tried about 10 different combinations). I do not see any system, but seems that it depends on graphic adapter type.
Everything works fine with Firefox 2 and 3, and with all Firefox versions including Firefox 4 beta 6 on Windows XP.


7 years ago
Version: unspecified → 4.0 Branch
This bug was reported using a pre-release version of Firefox 4. Now that Firefox 4.0.1 final has been released, can you please update and retest your bug? A fresh profile would be a good starting place to test, If you continue to see the issue, can you please update this bug with your results?

Filter: firefox4prebugsunco

Comment 2

2 years ago
If you still see this problem when using a current version, please post new information
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.