try to match @blueboxd and push firefox compatibility to 10.7

[i3roly]

as of 136, 10.7 is mostly usable. there are a few near-fatal cases however:

• if the user manages to muck up their profile, or run an older firefox than they did previously, the profile checking in toolkit/xre will cause the browser to hang after you click "OK" (missing profile) or "create new profile". (fixed by the time i push either 136_0_BUILD3 or 136_0_RELEASE)
• there are still sharp corners in the titlebar.
• there is something strange going on with the javascript. the troubleshooting page is completely empty and fires an NS_ERROR_UNEXPECTED that has to be investigated
• the pocket feature is not visible. i have no idea as to why, but the links on the pocket splash page are present if you hover the cursor around the right area.

[Wowfunhappy]

if the user manages to muck up their profile, or run an older firefox than they did previously, the profile checking in toolkit/xre will cause the browser to hang after you click "OK" (missing profile) or "create new profile".

Depending on how stubborn this issue is, it may make sense to just write a separate implementation. For example, I could pretty easily write a Python script that:

1. Check if the lastVersion listed in compatibility.ini in the Firefox profile is newer than the version in Firefox.app/Contents/Resources/platform.ini.
2. If it is, display a dialog asking the user if they'd like to delete the profile and start Firefox, or quit.
3. If the user says to delete the profile, delete the profile folder.

Let me know if you'd like me to write a script like this! The one thing is that I might have to disallow using multiple profiles, unless Firefox can expose which profile it is about to open.

[Wowfunhappy]

there are still sharp corners in the titlebar.

@krackers can probably help with this!

For context, we're talking about:

See also: https://stackoverflow.com/questions/9447645/nswindow-alternative-to-setopaqueno/78213126#78213126