Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


roytam1

My build of New Moon (temp. name) a.k.a. Pale Moon fork targetting XP

Recommended Posts

1 hour ago, Mcinwwl said:

webgl

How do you enable WebGL compatibility? I only see gecko & firefox

Share this post


Link to post
Share on other sites

52 minutes ago, Mathwiz said:

How do you enable WebGL compatibility? I only see gecko & firefox

webgl.webgl2-compat-mode=true

Share this post


Link to post
Share on other sites

Hi guys,

Does Google Maps work fine for you? For me it opens fine but after a second or two, the map´s screen goes black and

can´t show any part of the map. The zoom tool is there though. What´s wrong? How can I fix this?

Thanks.

Cheers.

Share this post


Link to post
Share on other sites

Don't know why they don't work for you, but I can confirm they work fine on my end.

Edited by Tamris
  • Like 1

Share this post


Link to post
Share on other sites

Well, I just tried the 3 mods available of the latest version of the browser, 27.9, and the problem is there on 3 mods.

Tested with clean installs, no old settings.

This problem doesn´t occur with Google Chrome, with the old latest working version on XP.

So, what could be the problem? Here I attach a screenshot so you can see.

Google Maps Black Screen.jpg

Share this post


Link to post
Share on other sites
12 minutes ago, curiosil said:

Well, I just tried the 3 mods available of the latest version of the browser, 27.9, and the problem is there on 3 mods.

Tested with clean installs, no old settings.

This problem doesn´t occur with Google Chrome, with the old latest working version on XP.

So, what could be the problem? Here I attach a screenshot so you can see.

Google Maps Black Screen.jpg

your webgl seems to be broken

  • Like 1

Share this post


Link to post
Share on other sites

can also confirm that google maps works fine for me on all 3 browsers.

maybe try make sure hardware acceleration is enable.  And update your gfx card drivers if that doesn't work.  Check this page idk if it is relevant or not.

https://www.sitepoint.com/firefox-enable-webgl-blacklisted-graphics-card/

Try updating your video drivers 1st. if that doesn't work check try these.

To enable WebGL, set webgl.force-enabled to true.

To enable Layers Acceleration, set layers.acceleration.force-enabled to true

To enable Direct2D in Windows Vista/7, set gfx.direct2d.force-enabled to true

Edited by Destro
  • Like 1

Share this post


Link to post
Share on other sites

curiosil said:


Does Google Maps work fine for you? For me it opens fine but after a second or two, the map´s screen goes black and can´t show any part of the map. The zoom tool is there though.



Just a side note, in my old browser and on OSM that happens when the scripts switch to a higher encryption, which it can't support yet. First looks fine, then BANG - server kills the tiles. Maybe check current TLS1.2 settings? "security" prefs in aboutconfig. Hm, and remember some pref about security hardening...
Another thought: Fake the useragent. Some major sites today just kick out XP-users (if UA contains "Windows NT5.x")
Or perhaps the browser already has a hardcoded fake UA for the tile server...
  • Like 1

Share this post


Link to post
Share on other sites

 

Thanks for your replies, but the solutions given could still be viable knowing that, as I said, this problem doesn´t occur with Chrome?

If the problem were hardware acceleration or the graphics card drivers, it should happen also with Chrome, right?

I don´t know about WebGL, but will try the modifications mentioned for about:config.

Edited by curiosil
Update

Share this post


Link to post
Share on other sites

 

But, if this WebGL is broken, where is it broken? If clean installations of new browsers have the same problem, the problem

doesn´t seem to be within the 'about:config' configuration of the browser, does it?

Share this post


Link to post
Share on other sites

JFYI:

Why You Shouldn’t Use Firefox Forks Like Waterfox, Pale Moon, or Basilisk

https://www.howtogeek.com/335712/update-why-you-shouldnt-use-waterfox-pale-moon-or-basilisk/

Brought to you by this guy:

https://www.howtogeek.com/author/chrishoffman/

Quote

Chris is Editor in Chief of How-To Geek. He's always tracking the latest Windows 10 news, tapping at his iPhone, and playing with all kinds of technology.

jaclaz

Share this post


Link to post
Share on other sites

curiosil said:


Thanks for your replies, but the solutions given could still be viable knowing that, as I said, this problem doesn´t occur with Chrome?
If the problem were hardware acceleration or the graphics card drivers, it should happen also with Chrome, right?
But, if this WebGL is broken, where is it broken? If clean installations of new browsers have the same problem, the problem doesn´t seem to be within the 'about:config' configuration of the browser, does it?


No it often means nothing if something works in one browser and in another not, as so many people seem to assume. Sometimes yes, but very often not. Not everything depends from the system only, browsers can also bring some own capabilities too.
Especially that encryption/SSL/TLS stuff is contained completely independent inside all Firefoxes and the forks, as I've been told here. Unlike other browsers which fully depend on system capabilities. That's the reason why Firefox forks can still be updated to use TLS1.2 on systems even older as Win98, and other browsers are stuck with what the old system can do.

Yet lots of things which work fine can still fail if they simply aren't enabled in the settings.
Settings are an incredible jungle in FF/gecko, there are over 3000 prefs, and some most important ones not even showing up in aboutconfig, and many cross-influencing each other.
Clean installations also are no guarantee that everything is fully enabled out-of-box, as so many people assume. For example some of roytam's browsers for very old systems, like FF2, are now equipped with TLS1.2, yet out-of-box still have the ancient default setting of max TLS 1.0. Or stuff like hardware-acceleration, those settings are infamous to be helpful on one system yet disastrous on another, so intentionally not always enabled by default.

At any rate, if the map first shows up fine and then vanishes again, the browser CAN do it, and it really doesn't matter what Chrome or the system can. The solution or the workaround to persuade the server to send the tiles must be somewhere in the settings....

Share this post


Link to post
Share on other sites
3 hours ago, jaclaz said:

JFYI:

Why You Shouldn’t Use Firefox Forks Like Waterfox, Pale Moon, or Basilisk

https://www.howtogeek.com/335712/update-why-you-shouldnt-use-waterfox-pale-moon-or-basilisk/

Brought to you by this guy:

https://www.howtogeek.com/author/chrishoffman/

jaclaz

already discussed: https://forum.palemoon.org/viewtopic.php?f=3&t=19262&p=142312&hilit=howtogeek#p142312

  • Like 1
  • Upvote 2

Share this post


Link to post
Share on other sites

New build of basilisk/UXP for XP!

Test binary:
Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190202-a31b9e067-xpmod.7z
Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190202-a31b9e067-xpmod.7z

diff: https://o.rths.cf/basilisk/UXP-xp-gitdiff-20181110.7z

PM28XP build:
Win32 https://o.rths.cf/palemoon/palemoon-28.4.0a1.win32-git-20190202-a31b9e067-xpmod.7z
Win64 https://o.rths.cf/palemoon/palemoon-28.4.0a1.win64-git-20190202-a31b9e067-xpmod.7z

Official repo changes since my last build:
- Only use white audio indicator when using a lightweight theme (46958a2aa)
- Only use white audio indicator when using a lightweight theme [pinned tabs] (b39e0b131)
- Merge pull request #945 from FranklinDM/audioindicator-lwtheme-fix (2d43b6eee)
- Add nullcheck for addons (pre-installed webextensions return null) (d6a2deb0c)
- Remove remote add-on debugging control. (2e581f48e)
- Always treat composition time offsets as signed (bed24fdb7)
- [BASILISK] Align browser glue with TychoAM for enableable add-ons. (2cbbc5de4)
- [PALEMOON] Remove some dead code from browser glue (plugin update service) (e82fdef9c)
- Reduce number of allocations in AutoStopwatch (3476c1d60)
- Revert "Reduce number of allocations in AutoStopwatch" (abcaa560f)
- Reduce number of allocations in AutoStopwatch (b55d41c24)
- Merge pull request #948 from trav90/media-work (7f992d50e)
- [TychoAM] Fix GMP* so that EME works in Basilisk (a606410ba)
- [AM] Remove spurious warning for staged cleanup. (efac6cc1c)
- Remove telemetry leftovers from JS engine. (493c956d8)
- Revert "Fix bookmarks backup logic." (dcc5d6a78)
- Only state the stop notification for JSDownloads in nsWebBrowserPersist::EndDownload (aa28523a5)
- Merge pull request #952 from adeshkp/remove-telemetry-js (fecab2c54)
- Merge pull request #954 from MoonchildProductions/TychoEME-work (6edfc0a20)
- Set incremental GC slice to 20 ms duration (278eda6a0)
- Update HSTS preload list (a31b9e067)

My changes since my last build:
- update nss to git rev 4aea92b574d2d674ee75838d46ea95b113e8fecb with nss339-vc2013.diff applied
- update Twemoji font to v11.3 based build.
- update libaom to rev 0ec86ac7ae1e32a7e70410fa4972a655ec3670a4 (without moz.build and aom_ports/aom_once.h)

  • Like 4

Share this post


Link to post
Share on other sites

New build of BOC/UXP for XP!

Test binary:
MailNews Win32 https://o.rths.cf/boc-uxp/mailnews.win32-20190202-733833f-uxp-a31b9e067-xpmod.7z
Browser-only Suite Win32 (removed due to request)

source patch (excluding UXP): (removed due to request)

Official repo changes since my last build:
- [PLATFORM] Update commit pointer (e5e04a0)
- [NAVIGATOR] Reconfiguration (886d0f7)
- [NAVIGATOR] Take select search plugins and fonts directly from Pale Moon (f4f6373)
- [NAVIGATOR] Remove Weave (03589cc)
- Issue #46 Remove Safe Browsing - Part 2: Navigator (9a18586)
- [NAVIGATOR] Fix Fonts (09aad28)
- [NAVIGATOR] Fix installer makefile (1d3c9f5)
- [MAIL] Fix main moz.build for fonts (b377bb9)
- [NAVIGATOR] Remove Doorhangers (5e10e68)
- [MAIL] Fix accidental convars edit (a05468f)
- [NAVIGATOR] Remove Migration (fab0217)
- [NAVIGATOR] Reorganize the menus (ab39ff4)
- [NAVIGATOR] Fix search service issues (3841ce1)
- [NAVIGATOR] Add Cookie Manager (75f1256)
- [NAVIGATOR] Delicious delicacies (8a50ddf)
- [PLATFORM] Update commit pointer (3447d95)
- [NAVIGATOR] Replace the unused Permissions Manager with a superior one and actually use it (53177cb)
- [NAVIGATOR] Fix subscribing to feeds via live bookmark (7b180bb)
- [NAVIGATOR] Offline Data Permissions Manager should show block not allow (76a7eea)
- [PLATFORM] Update commit pointer (f4d9db9)
- [NAVIGATOR] Make the Add-ons Manager as a Window preserve it's metrics and position (eaf32bb)
- [PLATFORM] Update commit pointer (ffcd4b4)
- [INSPECTOR] Add Navigator Support (733833f)

For UXP changes please see above.

Edited by roytam1

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...