I’m not sure that Stardock has dumped the skinning of all browsers because I’m seeing that the Internet Explorer titlebar is still getting skinned by Windowblinds. Instead, it appears to be “cherry picking” which apps get skinned and which apps are abandoned. While Stardock is able to do this, the consumer is also able to seek skinning solutions elsewhere. I consider this to be a lose-lose scenario for both Stardock and the consumer. It seems like a better solution could be implemented.
I am afraid we are not cherry picking anything.
Google Chrome opted to paint its own titlebar including background vs painting their tabs over the OS one, at that point they opted out of any sort of OS level skinning. They do have a command line parameter to disable this, but if this goes away then that will be it for Chrome. Especially after their recent funny business with blocking every third party app recently.
Firefox has caught a similar disease and I believe have plans to block third party dlls too which will likewise render their entire process unskinnable. Due to how their non titlebar mode works, we cannot make it look right in the default out of the box look so had to opt for the best new user experience which is for firefox to not skin vs customers thinking WB is broken or complaining on the forums.
Internet Explorer on the other hand is one of the best behaved apps which shows how you are supposed to paint tabs etc in the titlebar.
General rule of thumb is, if the app decides to take over the entire painting of the titlebar rather than using the OS apis to extend the client area into the titlebar to combine content then it will not skin. Complaints over that would have to go to the developers of those apps as they have chosen to paint something which looks like the OS one but isn't and reinvent the wheel for I suspect 5 seconds better battery life and/or adding in dark mode for their apps (again the wrong way!).
With regards to Firefox, the best we can do is add in a setting to disable the ignoring of the Firefox window which advanced users could enable (as they do for enabling the titlebar in FF in the first place).
A lot of work was put into seeing if we could have a better way to handle FireFox but it was the best we could come up with.