Leaderboard
Popular Content
Showing content with the highest reputation on 10/20/2024 in Posts
-
@feodor2 The non-standard JavaScript function document.loadOverlay() is deprecated since Gecko 60 (Firefox 60). Did you completely remove it in Mypal 68? Some of my (important) scripts call up this function which leads to the error message "TypeError: document.loadOverlay is not a function" in the Browser Console. If it has been removed, can it be re-implemented? I ask this as in more recent Firefox versions, these problematic scripts seem to be working again which means the document.loadOverlay() method is there again and works.3 points
-
Hope you can fix this bug. If it was fixed, my self-created custom button would work as I planned without any special workaround to be implemented. I use the VORAPIS V3 script version. Works great here in Mypal 68.3 points
-
@feodor2 Thanks for the links! The history feature of GitHub is great. Thanks to @UCyborg's hint to use this time machine, I started downloading repositories from the Firefox 68 era. With the linked version of xiaxiaofloods's userChromeJS, you can indeed install bootstrapped, legacy extensions in Mypal 68, but unfortunately, none of xiaxiaofloods's extensions I've tested from the linked repository do actually work.3 points
-
That "fact" is not valid here, You again forget, it's not a 360EE topic No.2385382538258. simply because someone wrote it happened in that outdated by several years browser, doesn't mean it will happen with Supermium released a week ago.3 points
-
Right, unfortunately, looks like you still don't know. In fact, it's very consistent. If you took your time to read on-topic posts, you'd see - the our "pack", the pack of on-topic, polite people, like 66cats, for example, already explained in technical terms. https://msfn.org/board/topic/185045-supermium/?do=findComment&comment=1259864 Edit: Is there anything you could contribute to the discussion in technical matters/terms, apart from investigating/claiming "whose" this thread is? Thank you.3 points
-
3 points
-
Win32 doesn't respond here anymore, and you know it. We were trying to raise our voices of wisdom and cool down the local crap posters. But we were labelled as the evil "collective you" by some grandpa. Good deeds don't go unpunished. So either you make a github account and try to ask, or do your own research (as you already stated you don't trust me). In case someone missed why no win32 anymore.link2 points
-
Again I'm not "a folk that simply delete files willy-nilly and check a checkbox", be respectful and reasonable on the forum. Check in chrome / GPU. Vulkan: Disabled2 points
-
1 point
-
The data archive is still offline, only wayback machine is back.1 point
-
This is a YouTube bug, the loading icon animation works even when hidden. It can be fixed if you add it to the uBlock m.youtube.com##.spinner:style(animation: none !important)1 point
-
1 point
-
So don't! But who's fighting whom? I missed. I'm having a polite conversation (I simply pretend you're polite, too). EDIT: I again ask everyone to create a pleasant atmosphere for win32 to appear!1 point
-
There you go! Finally someone noticed! Even on the poorly compressed screenshot it's still visible. On my good monitor, Supermium background looks like it's backlit with LEDs (cheap chinese bluish LEDs).1 point
-
You claimed to have good vision. Example. Compare the word "Brave" to "Supermium". Around "Supermium" we can see ugly, thick, red, blurry areals. The word "Brave" looks much cleaner. https://msfn.org/board/topic/185045-supermium/?do=findComment&comment=12526061 point
-
Yes, you do, there were several reports of different brightness levels in CatsXP (no modifications, just running only on kernel-ex), ported Chrome 115 (mine), default version of Brave and even Ungoogled! Supermium is brighter than all of those above, also has thicker, blurry fonts. I talk about all fonts (including the UI). The winners are Ungoogled and Brave.1 point
-
How then you'd explain it works (like it supposed to) in a normal Chrome 115? Unfortunately, I can't test both of 121 version, because I only have a self-ported v115 at my disposal. But then again, in older tests 115 vs 115, Supermium was also brighter.1 point
-
Is there a requirement of always being rude? Was I ever rude to you? No. I can disagree with you, but I don't roll on you. With such attitude you don't attract normal people to join your monologues.1 point
-
Missed my post again, I wonder if folks these days read before posting. It's rather insulting to assume I didn't try all available drivers before troubling win32. I mean, it's me we are talking about, not a random github fella. "I tried other drivers, all the same." https://msfn.org/board/topic/185045-supermium/?do=findComment&comment=12597241 point
-
Yes, absolutely! I should have emphasized this in my post as well. Don't let them intimidate you into leaving, @feodor2!1 point
-
Tobin must think himself very clever to have found a supposedly actionable fault in you not specifying to his satisfaction the exact steps to get the source code (which is in fact available, let's not forget that). Well, since apparently he's now wanting you to remove all his contributions from your code, you could play his game and ask him to provide an exact list of his personal contributions so that you could remove them. If he can't be expected to determine which Github code corresponds to which release version, then surely you can't be expected to hunt down his contributions either. In fact it may not even be possible for you to do so, because the fact that Tobin has commited certain code doesn't necessarily mean that he's the author of that code (as opposed to just copying something over from Mozilla, for example); and some of the code he's authored has very likely been commited by other people, like Moonchild. So, let him provide the list and prove his original authorship if that's the path he wants to take. IANAL (I am not a lawyer), of course, and I don't think his claims have merit, but why not have him(/them all) work for it instead of just trying to intimidate people. In any case it's very unfortunate that Pale Moon people choose to spend their energy on hounding people for pointless reasons instead of improving the (sadly) increasingly obsolete browser. Mypal and Centaury pose no threat to their IP, they're just hounding you to earn some sort of a "victory" and feel better about themselves in the face of losing the game in the big picture. (As a sidenote, I feel I should give some small credit to athenian200 for at least not behaving like a petulant child - which can't be said about the other two, especially Tobin. ) All that said, and regardless of this MCP attack, @feodor2, it actually wouldn't hurt you to properly tag your Centaury releases (in the Mypal repo) and provide a source archive for each release. It is indeed pretty inconvenient to have to go by just the commit dates. You absolutely don't deserve their attack, but in a way you gave them the means to try it by being a bit lazy.1 point
-
right click on the video and select "full screen". same goes for the "video controls".1 point
-
1 point
-
New NewMoon 27 Build! 32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210821-520d6b706-xpmod.7z 32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210821-520d6b706-xpmod-sse.7z 32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20210821-520d6b706-xpmod-ia32.7z 64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20210821-520d6b706-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1174323 - Disable screenClientXYConst subtest of pointerlock test on OS X. rs=KWierso (2d0db6d1b) - Bug 992096 - Implement Sub Resource Integrity [1/2]. r=baku,r=ckerschb (c30671ac0) - Bug 992096 - Implement Sub Resource Integrity [2/2]. r=ckerschb (0afc64d88) - Bug 1091883 - Added test, this is fixed by a fix to bug 1113438. r=sstamm CLOSED TREE (fd9a64b43) - Bug 1196740 - Consider redirects when looking for SRI-eligibility. r=ckerschb (5c749cdc9) - Bug 1202015 - Better document the SRI strings for translators. r=ckerschb (a7860e0fb) - Bug 1202027 - Make SRI require CORS loads for cross-origin resources. r=ckerschb (ea451323d) - bit of Bug 1202902 - Mass replace toplevel 'let' with 'var' (a6e8a587d) - Bug 1208629 - Properly support data: and blob: URIs with an integrity atribute. r=ckerschb (6b2018fe4) - Bug 1140129 - Don't clear tab title when location changes (r=Mossop) (ca1945ba8) - Bug 1073462: Send synthetic property with Content:LocationChange message. r=felipe (1aa418acf) - bug 1165017 - annotate content process URL on location change. r=mconley (cdca4fa75) - Bug 1157561 - Add webRequest-like API to Firefox (r=Mossop) (546a57822) - Bug 1163861 - Include windowID in all WebRequest notifications (r=Mossop) (c140af560) - Bug 1171248 - Add MatchPattern support to WebRequest module (r=Mossop) (b09a05658) (ebd6e6dc1) - browser: change mozCancelAnimationFrame to cancelAnimationFrame, fix returning from control fullscreen. (f790982a7) - import changes from `dev' branch of rmottola/Arctic-Fox: - Don't upgrade gfx features after device resets. (bug 1183910 part 5, r=mattwoodrow) (e53d0f91f) - Use the same graphics device parameters across processes. (bug 1183910 part 7, r=mattwoodrow) (083ae4f15) - Rename DriverInitCrashDetection to DriverCrashGuard. (bug 1190281 part 2, r=mattwoodrow) (9bd189d09) - Make DriverCrashGuard initialization lazy. (bug 1190281 part 3, r=mattwoodrow) (6821dc386) - Pull D3D11 logic out of DriverCrashGuard. (bug 1190281 part 4, r=mattwoodrow) (e499a0079) - Move telemetry recording into D3D11LayersCrashGuard. (bug 1190281 part 5, r=mattwoodrow) (b50a4c2b4) - Factor prefs out of DriverCrashGuard. (bug 1190281 part 6, r=mattwoodrow) (a3a1166ab) - Bug 1170939 - Close PBontentBridge when receving shut dwon message, r=khuey (5473d07f0) - Allow DriverCrashGuard to be used in content processes. (bug 1190281 part 7, r=mattwoodrow) (c9eaf8315) - Add a crash guard for DXVA2D3D9. (bug 1190281 part 8, r=mattwoodrow) (eceff5212) - Add driver crash guards to WebGL (bug 1190281 part 9, r=jgilbert,mattwoodrow) (c362b60c6) - Fix bogus assert in DriverCrashGuard. (bug 1190281 followup, r=mattwoodrow) (d4a7145bd) - Bug 968923 - part 5b - add nsIDOMWindowUtils::forceUseCounterFlush; r=bz (138d30251) - Bug 968923 - part 5c - add tests for use counters; r=bz (0c4b745e0) - Bug 554186 - Part 1: Unimplement NPN_Status API. r=josh (8759dad40) - Bug 554186 - Part 2: Remove unused nsPluginInstanceOwner::ShowNativeContextMenu(). r=josh (ad2ac0c4d) - Bug 1174913 - anchor and area mochitests. r=bz (ab2c58a34) - Bug 959992. Go back to not treating properties that the named properties object exposes as enumerable. r=peterv (0adeeb910) - Bug 1154974 (Part 1) - Give blobs serial numbers. r=bent (4602ca2cd) - Bug 1154974 (Part 2) - Merge image cache entries for blobs URIs with the same underlying blob. r=baku (3b64b409e) - Bug 1173314 - Make GetMozFullPath and GetMozFullPathInternal const. r=sicking (f8eaabb1e) - Bug 1167389 - Make FileList::mParent a smart pointer, and declare it to the cycle collector. r=ehsan (d1217e547) - Bug 1173390 - Remove the majority of the old directory picker implementation to prepare for the new implementation under bug 1164310. r=baku (750049972) - Bug 1164310, part 1 - Make the code for bypassing mobile security checks more general so that it can be used on non-mobile. r=baku (0486fb5ff) - Bug 1164310, part 2 - Implement an abstraction for a rooted filesystem for non-mobile devices. r=baku (f1d906bd6) - Bug 1164310, part 3 - Allow the DirState of blobs to be set explicitly. r=baku (13d832700) - Bug 1164310, part 4 - Implement the new HTMLInputElement API including the new Promise returning GetFilesAndDirectories. r=baku (d0f93ec19) - Bug 1164310, part 5 - Implement new anonymous content and layout pieces for directory picking via input elements. r=tnikkel (ac5a00781) - Bug 1164310, part 6 - Implement the new Promise returning DataTransfer.getFilesAndDirectories() API. r=baku (375fba953) - Bug 1164310 - Follow-up: Fix build bustage with --disable-accessibility. r=me (da0e6745b) - Bug 1164310, part 7 - Touch CLOBBER since bug 1177844 isn't fixed yet. r=me (5fa829742) - Bug 1185381 - Make FileList clonable - patch 1 - move code into FileList.h/.cpp, r=smaug (b85483178) - Bug 1185381 - Make FileList clonable - patch 2 - rename FILEIMPL_IID to BLOBIMPL_IID, r=smaug (0f920cd05) - Bug 1185360 - PostMessageEvent should not have a different behavior if the main principal subsumes the destination one., r=smaug (070ab034b) - Bug 1185381 - Make FileList clonable - patch 3 - FileListClonedData implementation, r=smaug (f4f082d18) - Bug 1185381 - Make FileList clonable - patch 4 - tests, r=smaug (fb3637313) (520d6b706)1 point
-
yes it does, will have a look on it and try to fix. EDIT: fixed, will be included in next build. https://github.com/roytam1/palemoon27/commit/f790982a7dd54d64b274a7537dd84d1becac119d1 point
-
1 point
-
New Moon 26.5 playground build for Win2000 (32bit only): http://o.rthost.win/gpc/files1.rt/palemoon-26.5.0-20210814.win2000.7z and updated test binary of K-Meleon 74 with Goanna 2.2(newmoon-26.5) that works in Win2000: http://o.rthost.win/gpc/files1.rt/KM74-g22-20210814.win2000.7z Changes since last build: - ported cubeb_winmm.c overflow fix by mixit@MSFN, Thanks! This should fix the famous 23m18s freeze bug for audio/video playback. (a66d2e441) - NSS: update builtin certdata with mozilla (dated May 2021) and bump ckbi version (6e8ae29d9) - ported changes from UXP: - [NSPR] Lock access to PRCallOnceType members in PR_CallOnce* for thread safety. (361743b22) (599d6be8b)1 point