Well, I don't know if it is the right section to post this comment, but I wanted to congratulate you on how the Pale Moon browser project is going on. I've been using it for a couple of days now and I've been so happy about it that I couldn't help but donate. I encourage everyone to do so, as often as possible, to keep this wonderful browser healthy.
For reasons I won't explain here, I'm still on Mountain Lion 10.8.5 in 2023, using a late 2008 unibody Macbook Pro. Believe it or not, this laptop still performs great (for my needs). But web browsing has always been a nightmare. Pale Moon is the more stable and pleasant browser I've ever used with this configuration. Version 32.0.0 works like a charm, though sometimes I experience weird blank menus on some web pages (including palemoon.org). Exit Firefox ESR, ArticFox and Chromium (that I'll keep as a last resort solution in case some exotic sites behave...).
So once again thank you, and I'll try to support you with the best of my abilities as often as I will be able to.
Bravo !
Moderator: dbsoft
Forum rules
Important note:
The old Mac OS versions of Pale Moon were provided by various people and not official or in any way organized. Please make sure you check the date of topic threads to know if the topic is current or relevant! We are using this board for both old discussions and new development of Pale Moon on Mac.
Any specific bugs you find that don't have their own topic yet: please make a new topic; one bug per topic please to keep things organized.
Important note:
The old Mac OS versions of Pale Moon were provided by various people and not official or in any way organized. Please make sure you check the date of topic threads to know if the topic is current or relevant! We are using this board for both old discussions and new development of Pale Moon on Mac.
Any specific bugs you find that don't have their own topic yet: please make a new topic; one bug per topic please to keep things organized.
Re: Bravo !
Glad it is working well for you! So you have blank menus on palemoon.org using Pale Moon on Mountain Lion? I have not seen that, I test on Lion but not Mountain Lion... Can you take a screenshot of it and post it here?jamalbee wrote: ↑2023-04-02, 06:01For reasons I won't explain here, I'm still on Mountain Lion 10.8.5 in 2023, using a late 2008 unibody Macbook Pro. Believe it or not, this laptop still performs great (for my needs). But web browsing has always been a nightmare. Pale Moon is the more stable and pleasant browser I've ever used with this configuration. Version 32.0.0 works like a charm, though sometimes I experience weird blank menus on some web pages (including palemoon.org). Exit Firefox ESR, ArticFox and Chromium (that I'll keep as a last resort solution in case some exotic sites behave...).
Re: Bravo !
Here it is I hope the picture will display correctly. I also noticed problems with wikipedia. I'll try to post a picture about it.
- Attachments
-
Re: Bravo !
Blank menus are probably not the correct expression. Let's say blank images.
Re: Bravo !
And here is the wikipedia page of Mac Os. It only show titles or chapters on the left part and a blank page, without text or pictures. Clicking on one of the chapters in the left part won't display anything, the page remaining blank.
- Attachments
-
Re: Bravo !
That's a new one!. That looks really strange -- it handles the alpha channel of images but doesn't actually texture them
Can you please include the output of help -> troubleshooting information so we can see what your environment is?
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Bravo !
Ok, I saved the entire troubleshooting page, but I can't send .xhtml files. Which part do you actually need ? Here is the Application basics part
- Attachments
-
Last edited by jamalbee on 2023-04-07, 12:35, edited 1 time in total.
Re: Bravo !
The troubleshooting page has a "copy as text" button on it. that will copy everything as plain text. simply paste that in your post when replying, and kindly use the [ hide ] forum tags when you do 
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Bravo !
Re: Bravo !
"Copy text to clipboard" button didn't work? that is strange.
I'm talking about this:
You can zip up the xhtml and attach that, perhaps.
Since you are on Mac though, it may be something Mac specific -- we do need the entire troubleshooting information to get details.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Bravo !
Moving this to the Mac board.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Bravo !
Re: Bravo !
Yeah it doesn't seem to be happy with your graphics at least.
Since it's already using a fallback with skia graphics, maybe you can try disabling hardware acceleration and see if that works any better for you.
Preferences -> Advanced -> tab "General " -> Uncheck "Use hardware acceleration when available"
Then quit and restart the browser.
If that doesn't help then I'll have to defer to the Mac dev (dbsoft) who may have more ideas.
Since it's already using a fallback with skia graphics, maybe you can try disabling hardware acceleration and see if that works any better for you.
Preferences -> Advanced -> tab "General " -> Uncheck "Use hardware acceleration when available"
Then quit and restart the browser.
If that doesn't help then I'll have to defer to the Mac dev (dbsoft) who may have more ideas.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Bravo !
Thank you very much. Problem solved ! Booting in Safe mode (holding the Shift key) was successful too, but it was but a temporary solution.
Re: Bravo !
It might be a driver issue on that MacOS... I wonder if the Nvidia web drivers support your graphics processor...
Worst case I can put in a driver blocklist entry for your version of MacOS and Nvidia card, so it won't try to accelerate on that OS and driver combo.
-
q160765803
- Apollo supporter
- Posts: 35
- Joined: 2023-04-13, 07:57
Re: Bravo !
Off-topic:
First, sorry for being off-topic here.
Regarding gitea timeout issue, I wonder if you can create another branch with part 1 only and create PR on this new branch instead.
After created PR, you can push remaining changes to new branch.
First, sorry for being off-topic here.
Regarding gitea timeout issue, I wonder if you can create another branch with part 1 only and create PR on this new branch instead.
After created PR, you can push remaining changes to new branch.
Re: Bravo !
q160765803 wrote: ↑2023-04-27, 02:51Off-topic:
First, sorry for being off-topic here.
Regarding gitea timeout issue, I wonder if you can create another branch with part 1 only and create PR on this new branch instead.
After created PR, you can push remaining changes to new branch.
Off-topic:
That is worth a try, good idea.
That is worth a try, good idea.
-
q160765803
- Apollo supporter
- Posts: 35
- Joined: 2023-04-13, 07:57
Re: Bravo !
dbsoft wrote: ↑2023-04-27, 18:05q160765803 wrote: ↑2023-04-27, 02:51Off-topic:
First, sorry for being off-topic here.
Regarding gitea timeout issue, I wonder if you can create another branch with part 1 only and create PR on this new branch instead.
After created PR, you can push remaining changes to new branch.Off-topic:
That is worth a try, good idea.
Off-topic:
By the way, it seems that PR#2215 causes videojs to be broken. For example: https://anime1.me/20118
And sites uses dynamic import still having problem on loading. For example: https://misskey.io/
By the way, it seems that PR#2215 causes videojs to be broken. For example: https://anime1.me/20118
And sites uses dynamic import still having problem on loading. For example: https://misskey.io/
Re: Bravo !
Odd about that video, the only thing I see different is this error: Automatic publicPath is not supported in this browserq160765803 wrote: ↑2023-05-02, 01:42Off-topic:
By the way, it seems that PR#2215 causes videojs to be broken. For example: https://anime1.me/20118
And sites uses dynamic import still having problem on loading. For example: https://misskey.io/
Which doesn't seem like something the Dynamic Import changes should affect.
Might be related to the publicPath error, the other thing doesn't trigger on another computer... If this problem was caused by my changes I'll get it fixed.
Edit: Okay the video problem is fixed and I have a pull request for it.
The other site, the problem appears to be an error with parsing await.... the script does not use await with import() so this problem is completely unrelated to dynamic import. I'll take a look at it later, but since it isn't related at all to the dynamic import changes it will be on the back burner.
Martok determined that this feature is required for that second web site: https://repo.palemoon.org/MoonchildProd ... ssues/2229