Closed derinb closed 8 years ago
I just duplicated Firefox entries to create SeaMonkey entries. Some does not make sense. Feel free to suggest please.
Please remove the ones that don't make sense. Also, please test your patches before submitting pull requests.
Well, the appversion<3.1b2
entries does not make sense because I suppose it imply the FF version numbers. I am not sure also what they are doing actually?
There are too many operating systems. I cant test patches on FreeBSD and and SunOS. But tests on Windows are OK.
Entries actually make sure skin folder is registered for SeaMonkey. Currently it does theoretically for all OSes.
I can simply remove appversion<3.1b2
entries and make a single entry for Mac. What do you suggest?
I'm not familiar enough with Seamonkey to suggest something. I'd rather focus on a great experience in Firefox.
Adding Seamonkey support is fine, but the patch needs to be clean and not interfere with Firefox.
Testing on exotic operating systems is not necessary, but as far as I can tell this patch is not about those. We need to make sure PP works fine on Windows, Mac and Linux, so that's what we should test on.
Hello Andreas,
This PR only includes only SeaMonkey Guid. As you suggested I am making sure Firefox is not affected.
I have tested it on Windows 10 and Mac OS X. Working fine for SeaMonkey. Please accept the PR. I will fix any issues for SeaMonkey if I detect or any SeaMonkey user reports.
chrome.manifest declarations are missing for SeaMonkey. Because of that,
chrome://personas/skin/
does not get registered for SeaMonkey