Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v40.1 on macOS 13.1 BROKEN #128

Open
CalidumCanis opened this issue Mar 2, 2023 · 16 comments
Open

v40.1 on macOS 13.1 BROKEN #128

CalidumCanis opened this issue Mar 2, 2023 · 16 comments
Labels
question Further information is requested

Comments

@CalidumCanis
Copy link

I downloaded and ran v40.1 on macOS 13.1 and the whole window except the title bar is just transparent.

@rmottola
Copy link
Owner

Never tested on such a new system. 40.2 should provide some release if you can build, but no guarantee. On 13.1 you have full Firefox and SeaMonkey...

@rmottola
Copy link
Owner

rmottola commented Jun 5, 2023

how does 42.0 fare, just out of curiosity?
ON 10.11 it works very well, on 10.13 it works too, but windows cannot be moved.

@rmottola
Copy link
Owner

@CalidumCanis please try 43.0 It works fine on 10.11, on 10.13 it works but windows cannot be dragged... test and say :) Several mac fixes were imported in this release.

@rmottola rmottola added the question Further information is requested label Dec 13, 2023
@rmottola
Copy link
Owner

@CalidumCanis any news? otherwise I will probably close the bug, since I cannot reproduce. There were several updates to test too.

@katze26
Copy link

katze26 commented Jun 13, 2024

Hey it's me from another account, on macOS 12.7.4 trying out 44.0 it's opening, but there's this blank popup in the middle of the screen which isn't closing, I can see the "About:" page has loaded behind. This is how it looks:
image

@rmottola
Copy link
Owner

rmottola commented Jun 13, 2024

@katze26 no idea... 12.7.4 is so new... probably nobody ever tested ArcticFox on it... I can't support it without having it. If nobody steps up... It could be an error message which is not readable? could you try opening --jsdebug console on launch?
It could even be a compatibilty of a 10.7 build on 12.x? ever tried opening PaleMoon 27 or Firefox 45 on such recent mac?

@rmottola
Copy link
Owner

rmottola commented Jul 1, 2024

It would be interesting to try a build done on 10.13 instead of older ones, but I cannot attach it to this bug, too big (36MB vs 25MB allowed)

@rmottola
Copy link
Owner

@CalidumCanis, @katze26 would you mind testing v45? please test the classic 10.7 build but also the specific 10.13 build I did and see if there are any differences?

@rmottola
Copy link
Owner

Please let try and let me know, trying to understand if either by miracle it was fixed or building on a newer system helps. More than that I cannot to myself.

@Jazzzny
Copy link

Jazzzny commented Dec 15, 2024

I think this was fixed by UXP in https://repo.palemoon.org/MoonchildProductions/UXP/commit/e73a2fb0fc21de86db411a1a0fd475582455c5ac - would it be possible to cherry pick this? It seems to be a rather simple patch.

@rmottola
Copy link
Owner

@Jazzzny I am little bit sceptic because I see nothing similar in Firefox... not even esr128, I checked all esr versions, they didn't add such a workaround. Unfortunately, I don't have such a recent mac and also we don't know if esr has such behaviour.

@rmottola
Copy link
Owner

@rmottola
Copy link
Owner

@CalidumCanis @Jazzzny are you able to test Firefox ESR versions and see which one did not work and which do? I suppose esr45 will be broken given https://bugzilla.mozilla.org/show_bug.cgi?id=1818939

esr52 ? esr60? esr68? that could help us look for a fix.

@Jazzzny
Copy link

Jazzzny commented Dec 17, 2024

Unfortunately there seems to be another bug that affects Firefox 57-69, where all of these versions crash for me (at least on macOS 15, arm64).

Firefox 56 and 52 ESR launch but have the invisible window issue and Firefox 70 and 78 ESR launch without the issue.

This is a very big gap between versions, maybe the crashing isn't an issue on Intel if anyone would like to test.

@rmottola
Copy link
Owner

@Jazzzny I too fear that testing on ARM chips with emulation might add some compliaction. Best would be to reporduce on Intel and check the version you cannot test. Somebody else can join?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants