1217547 - Windows shell buttons (minimize/maximize/close) disappear when Windowblinds theme is applied if OMTC is enabled

Status: RESOLVED INCOMPLETE

(Core :: Widget, defect)

Description

[Trammel May]

Attachment: SkywallNoButtons.PNG

Actual Result:
The minimize, expand and close UI buttons at the top right hand corner of the Firefox window are not visible.

Expected Result:
The user should be able to see the minimize, expand and close buttons.

Steps to Recreate:
1. Download/install Windowblinds and complete trial registration. 
2. Select and apply the "Acrylic 7" theme. 
3. Launch Firefox Developer from cmd. 
4. Go to addons.mozilla.org and apply "The Rusty Wall" theme. 
5. Observe, the UI buttons are not visible. 

Special Notes:
New graphics driver updates were found online, however they are incompatible with the operating system.

Comment 1

[Trammel May]

Attachment: SkywallAboutSupport.txt

Comment 2

[Trammel May]

Attachment: SkywallDxDiag.txt

Comment 3

[u279076]

It looks like Windows 7 is the end of the line for your graphics chipset.

Does this happen if you turn off hardware acceleration in Firefox preferences?
Does this happen with any older version of Firefox? https://archive.mozilla.org/pub/firefox/releases/
Does this happen with any other applications (eg. Chrome)?
Does this only happen with Windowblinds installed?

Comment 4

[Trammel May]

(In reply to Anthony Hughes, QA Mentor (:ashughes) from comment #3)
> It looks like Windows 7 is the end of the line for your graphics chipset.
> 
> Does this happen if you turn off hardware acceleration in Firefox
> preferences?
> Does this happen with any older version of Firefox?
> https://archive.mozilla.org/pub/firefox/releases/
> Does this happen with any other applications (eg. Chrome)?
> Does this only happen with Windowblinds installed?

Yes, this does still happen when hardware acceleration is turned off. 
Yes, this happens on previous builds as well. 
This does not happen on chrome or other applications. 
Yes, This only happens when Windowblinds has a theme applied.

Comment 5

[u279076]

Thanks, please let us know if this happens on any other systems following the same steps.

Comment 6

[Trammel May]

(In reply to Anthony Hughes, QA Mentor (:ashughes) from comment #5)
> Thanks, please let us know if this happens on any other systems following
> the same steps.

Will do!

Comment 7

[u279076]

I can reproduce this in a Windows 8 VM so I don't think it's a hardware problem. It also doesn't need a lightweight theme installed. Simply default Firefox with a Windowblinds theme applied is enough. It seems like this might be an old regression in Firefox as 29.0 does not reproduce this bug but 35.0 does. I'll see if I can narrow this down.

Comment 8

[u279076]

This is a regression from Firefox 32:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=cb9f34f73ebe&tochange=9d8d16695f6a

Comment 9

[u279076]

(In reply to Anthony Hughes, QA Mentor (:ashughes) from comment #8)
> This is a regression from Firefox 32:
> https://hg.mozilla.org/mozilla-central/
> pushloghtml?fromchange=cb9f34f73ebe&tochange=9d8d16695f6a

This is where we enabled OMTC by default. Turning off OMTC works around this issue.

Comment 10

[u279076]

Bas, do you have any ideas about this?

Comment 11

[Bas Schouten (:bas.schouten)]

(In reply to Anthony Hughes, QA Mentor (:ashughes) from comment #10)
> Bas, do you have any ideas about this?

WindowBlinds functions much like malware in the sense that it intercepts a whole bunch of Windows APIs and inserts all kinds of problematic things in there.

I've attempted to contact StarDock in the past to try and get them to improve their stuff but they've never replied. Honestly we should just tell people to switch off HWA manually if they are installing things that do all kinds of things no piece of software should ever do.

Comment 12

[u279076]

I suspect this is a DUPE of bug 1077245. If there's nothing we plan to do to fix this then I suggest we just close both as WONTFIX. Any objections?

Comment 13

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

41 was EOL'd last week. This is now a wontfix for FF41.

Comment 15

[Trammel May]

QA Confirmed: Not fixed