Jump to content

VistaLover

Member
  • Posts

    2,095
  • Joined

  • Last visited

  • Days Won

    93
  • Donations

    0.00 USD 
  • Country

    Greece

Everything posted by VistaLover

  1. @UCyborg : Since you appear to be a CSS connoisseur , I have a personal request/favour to ask: When loading a GitLab repository URL (palefill is required in UXP-based browsers), e.g. https://gitlab.com/cleanflash/installer/-/releases/ GL now display a very wide (or, rather, tall) header , which, for me, is an unnecessary waste of (vertical) screen space... Some months prior, it was still possible to revert to a slimmer header by manipulating a cookie (named "logged_out_marketing_header_id"), but that cookie is no longer set/effective ... So I'm hoping you can come up with a userstyle (CSS code) I could use inside Stylus to trim that header's height, ideally as shown below: Thanks in advance!
  2. In NM28, discourse-based boards load the "proper" (full) version when the "User Agent Mode" is set either to "Native" (default): Mozilla/5.0 (Windows NT 6.0; rv:4.8) Goanna/20221125 PaleMoon/28.10.6a1 or "Gecko Compatibility": Mozilla/5.0 (Windows NT 6.0; rv:68.0) Gecko/20100101 Goanna/4.8 PaleMoon/28.10.6a1 "Firefox Compatibility" mode: Mozilla/5.0 (Windows NT 6.0; rv:68.0) Gecko/20100101 Goanna/4.8 Firefox/68.0 PaleMoon/28.10.6a1 exposes a Fx 68.0 slice, which makes "discourse" trigger the "unsupported browser" header and loads the read-only, "dumbed-down" version of boards; as I posted above, "discourse" now expect at minimum Fx 91.0esr to load fully (possibly, some version between 79-90 is the exact minimum version of the release branch, but I didn't bother checking that scenario ...) .
  3. In Serpent 52, firefox-91esr seems to be the minimum FxESR version that is supported by "boards.straightdope.com" (91esr has been now deprecated, the currently supported one is 102esr) : general.useragent.override.straightdope.com;Mozilla/5.0 (Windows NT 6.0; rv:91.0) Gecko/20100101 Firefox/91.0
  4. The WebRTC implementation that ships with St52, despite being spec-compliant, is not up-to-date with the latest, Chromium-specific, iteration most "such" services employ ... Don't count on upstream (MCP) to improve WebRTC in the context of UXP, as they never supported the feature inside Pale Moon... The new maintainer of official Basilisk (i.e. Basilisk-Dev) has plans laid out to improve WebRTC performance inside "his" browser, however I'm not certain how much that effort has progressed and/or whether @roytam1 is tracking/implementing those changes in Serpent 52.9.0 ... EDIT: I may be in error with the above statements in relation to Zoom, because I just found this: https://forum.palemoon.org/viewtopic.php?p=230890#p230890 Thus, more insight is needed in regards to "Zoom-audio" from an actual browser developer...
  5. @luweitest : In about:config, locate network.captive-portal-service.enabled and toggle to "false"; for good measure, also locate captivedetect.canonicalURL and change the value from http://detectportal.palemoon.org/success.txt to an empty string; restart browser to take full effect... FWIW, for me "captive portal detection" isn't considered as nefarious... Please, also read: https://www.palemoon.org/policies/privacy.shtml Also, for: ... read: https://19216801.one/ (i.e. this is an internal LAN IP address, not something external...) I can understand you being inside mainland China makes you extra cautious/suspicious of "background" connections, still I think Pale Moon can be absolved of such wrong doing ...
  6. ... Wow, someone must have jinxed you, Roy! First, infection by Covid19; then, a broken pair of prescription glasses (which cost a hefty sum to replace); and, lastly, the bicycle accident ... I'm sending tons of good luck your way to counter the jinx and heaps of wishes for a speedy, full, recovery! BTW, I'm sorry I'm not that vocal in this thread currently, but RL issues prevail ...
  7. I am on Vista SP2 32-bit (build 6.0.6003) for which, as you might know, there's no Extended Kernel (yet?) , and I can confirm that Notepad++ v8.4.7 [32-bit x86] has become Vista-incompatible, for the reason outlined above by @AstragonQC :
  8. ... That's why the MozillaZine (not related to Mozilla) KB site was created in the first place : http://kb.mozillazine.org/Browser.backspace_action
  9. ... Mentioned previously in this thread: FWIW, this is the XP-compatible version 4 (last official 4 build being v4.0.7.22); version 5 is Chromium 86 based, latest version 6 is Chromium 101 based; v5 & v6 require Win7SP1 and higher... http://dcbrowser.cqttech.com/ (What with Google services being banned in mainland China and DCBrowser targeting only the Chinese, a Google search for "dcbrowser" here did not return that homepage above ...)
  10. The path that works for me is: ftp://ftp.dyu.edu.tw/pub/Hardware/vendor/Diamond/display/fire-gl/fire-gl-1000-pro/b1kp154.exe (206 KiB file...)
  11. ... What version of Chromium is that based on? Also, it appears that its installer can't be unpacked with any of the known extractors ; many people, myself included, won't run directly a Chinese-made setup... Indeed, version 8.0.0.21681 (from May 31st), based on Chromium 79 (way far from latest Chromium 106 ), requires at least Win7: http://www.liebao.cn/index.html
  12. Hi Dave ! 20 days have passed since and we're less than a week away from the time clocks will have to be set one hour back (in your case, from BST to GMT), am I to infer that lack of further communication on this means that the "incorrect-today" issue on your 360EEv13.5 copy has no longer manifested itself? ... Considering you were skeptical about that ,,, Cheers
  13. ... I won't miss it myself, it is/was sending most user data to Chinese servers: https://en.wikipedia.org/wiki/UC_Browser Works here, but only links for the mobile version are to be found in it:
  14. @Slavich : How does your latest post above fit into this thread/topic? This is about force-enabling multiprocess (aka electrolysis=e10s) in Firefox 52 ESR (under Windows XP) and in roytam1's Serpent 52.9.0/55.0.0 forks... Please post any issue(s) you have with New Moon (27 or 28?) in the appropriate thread ...
  15. ... Better first check on Mozilla Firefox 52.9.0, too... If it doesn't detect Silverlight too, then your issue probably has to do with a corrupted (global) Silverlight installation ... If a complete SL-removal-OS reboot-SL-re-installation doesn't fix it, an old Mozilla Support article that may contain useful info is this one ... Edit: If "plugin.scan.plid.all" is set to true (default), then SL should be detected by St52 via the reg-key below: HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@Microsoft.com/NpCtrl,version=1.0 Hope I've helped ...
  16. Can't confirm/WFM ; in a fresh Serpent 52.9.0 profile, latest St52 (2022-10-13) (32-bit), the NPAPI plugin is correctly identified inside "about:addons => Plugins" : When I visit a test SL page (radioactivepages.com), "Click-to-activate" is correctly triggered: ... and after I "Allow Now", the animation (clockwork) plays fine:
  17. https://repo.palemoon.org/MoonchildProductions/UXP/issues/2018
  18. @UCyborg : It's well past midnight here and I had a rough day today (rusty plumbing caused a water leak in one wall of my flat ), so I'll review the linked documentation tomorrow, when, hopefully, I'll be more lucid , but, put in layman's terms, who is right and who is wrong here? Is UXP doing the right thing by taking into account "z-index=-2", resulting in the image being hidden, or is Chromium doing the right thing by ignoring "z-index=-2" and, thus, displaying the "story-image"? Thanks in advance ! From file https://cdn.tunwalai.com/lib/bootstrap5/bootstrap.min.css , L96-L104: .story-image { margin: 0; border-radius: 8px; display: block; height: 292px; min-width: 100%; width: 292px; z-index: -2; }
  19. https://forum.palemoon.org/viewtopic.php?f=70&t=28972 More about "z-index" here ; still, Moonchild didn't say why Chromium displays such an image fine ...
  20. ... or, rather, a "problem with UXP itself" (I can guarantee you the "tunwalai" admins don't think, even for a second, that their site has any "problem" ) ... FWIW, St52 doesn't seem to have an issue fetching the image itself (no network issues), however the CSS script it's being served is not palatable to UXP: Since it's been shown, here in this thread, that the "non-loading-image" issue also manifests itself in the official UXP apps, it had better be reported to: https://forum.palemoon.org/viewforum.php?f=70 https://forum.palemoon.org/viewforum.php?f=61 Why is this, simply, NOT a surprise?
  21. Once again, you're correct ... But I created my cosmetic filter before patching palefill to work on "learn.microsoft.com"; without palefill doing its magic, the site in question would display as below: ... so I used the cosmetic filter: learn.microsoft.com##.has-default-focus.header-holder to also remove what "appeared" to be two "empty" ribbons ; and there it was my wrong assumption ... Thanks for pointing this out ! With palefill patched and enabled, the cosmetic filter above will also remove So a more appropriate cosmetic filter would be: learn.microsoft.com###banner-holder,#unsupported-browser which blocks both the top Microsoft Ignite "info" banner as well as the "unsupported browser" one... Thanks for that, too! Instead of removing the "unsupported browser" banner after its creation, remove the Javascript code that generates it in the first place ("promo" banner still displays, though...); @AstroSkipper, time to update your "learn.microsoft.com" custom filters ("My filters" tab of uBO) !
  22. It wasn't clear to me at first what you were speaking of there , but upon inspecting the userscript's code, I figured out it must be the problem of not being able to access GitHub releases in a UXP-based browser without having palefill/gh-wc-pf extension installed first... And yes, I have already reported this, in this very thread, just ca. 20 days ago: https://msfn.org/board/topic/182647-my-browser-builds-part-3/page/189/#comment-1226368 ... and https://github.com/martok/palefill/issues/47#issuecomment-1257080166 contains a "dirty" workaround ...
  23. Do you want these? https://github.com/roytam1/UXP/commit/a16549ddb717f8c178f1433ade673fb0bb169b63 https://github.com/roytam1/UXP/commit/51bb5d5c8179ff6e5ef0770403e9334bebd898d9
  24. ... As far as I am aware, the default setting in uBO is to have "cosmetic filtering" always enabled ("activated"), both in a global scope: as well as "on a per site" scope: Relevant reading material here ... So I take it, by what you posted, that you had disabled CF yourself sometime in the past... Am I correct in this assumption? Kind regards
×
×
  • Create New...