Leaderboard

I'm just plain frustrated to see yet another user of Serpent 52 UNDER WINDOWS XP post and seek help in the official Pale Moon (& Basilisk) forums: https://forum.palemoon.org/viewtopic.php?f=61&t=26414 Such actions only undermine further this project in the eyes of "upstream" and often lead to additional "counter" measures from their side... By pure luck, the OP was replied to by Moonchild, who used more moderate/civilised language... I don't want to even fathom the verbal abuse the OP would've been subject to, had he been "welcome" in the official forums by a certain M.A.T. developer... But in the above case, XP users who don't want to get informed themselves about the software (browser) they're using on that OS is only one part of the problem; OP is still unsure where to seek support for his predicament, trying Roytam1's GitHub repo for a start (only to be discouraged by GitHub's user-agent sniffing and the fact UXP browsers no longer support Chrome/Edge-targeting GitHub without installing a third party extension first... ). @roytam1, please make the header/banner in your blog's page more verbose; I personally know that comments there are indeed enabled, but that fact isn't at all apparent if you arrive there, much like the OP did (from God knows where...), by simply loading: https://rtfreesoft.blogspot.com/search/label/serpent (you'd have to scroll all the way down (END) and then click on the blue "no comments" link in the bottom to reveal the comments input form; a redirection to https://rtfreesoft.blogspot.com/2021/03/weekly-browser-binaries-20210313.html#comment-form takes place); or you can always include links in that blogspot banner to this thread or to the other forum(s) you provide support for your XP forks... We, as a community of users of your splendid offerings, just can't afford anymore to further aggravate Moonchild and Co. ... Thanks for reading, best wishes !

"Upstream" have just removed the years-long ability of official Pale Moon to accept Firefox-targeting "legacy" extensions: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/1748 UXP master branch https://repo.palemoon.org/MoonchildProductions/UXP/commit/3aa334d https://repo.palemoon.org/MoonchildProductions/UXP/commit/3064ad3 Pale Moon master branch https://repo.palemoon.org/MoonchildProductions/Pale-Moon/commit/86e5b48 https://repo.palemoon.org/MoonchildProductions/Pale-Moon/commit/bb6dab5 These changes haven't made it yet to the respective (UXP+PM) release branches, but I guess it's only a matter of time now... I think that route, which was already on the horizon for some time now, has been expedited considerably after the spat with (and following divorce from) ex-associate JustOff and his insistence on keeping Fx legacy extensions compatible with PM (via, among other things, CAA and MTT) ... 1. I sincerely hope/wish the above isn't even considered for inclusion by @roytam1, he's currently building NM28 with the --enable-phoenix-extensions mozconfig flag and they've axed it now... 2. MyPal follows closely the release branch and build configuration of official, release channel, Pale Moon, I'll be waiting with bated breath to see whether @feodor2 merges this in... 3. The code changes also touch platform (UXP) files, I hope Basilisk (and, thus, Serpent 52) aren't being harmfully affected by them, as St52 shares the same GUID with Firefox (and is natively able to load Fx extensions) ...

did some changes in both github settings and in blog settings, hope these help.

test with RT-Firefox2.... Sigh, there may be a filepicker for attaching (after editing), but uploading still doesn't work. No chance :( Had struggled yesterday with older KM1.6 (FF3.5) already, no luck either with uploading. But haven't tried with KMG74 yet... And strongly suspect that UPLOADING may need javascript, BUT the filepicker only shows up inside a noscript-tag... Can unhide that by css, editor and filepicker, despite JS allowed, but just being visible doesn't necessarily mean it starts working. Still potential for more tests... Edit: back on K-Meleon now... But am relieved that Firefox2 (engine = Retrozilla) at least still allows to READ the forum, and login, post, logout etc.! Although looking awful of course, everything is stapled vertically, e.g. just the 3 (huge) Like/Upvote buttons below every posting take up more than a whole screen height! But for frequent visitors this can be fixed later with some custom css, the only prob is for clueless users to find it... But as long as they can read, they have a chance to find And in Firefox2 often the usual brute-force workaround is required, toggle all Page Styles OFF, to get access to the menus, incl. the logout-link. Am still busy fiddling with my css tweaks, will post more in awhile. A few I have already posted here: https://msfn.org/board/forum/23-site-amp-forum-issues/ But don't hold your breath for devs to fix such ancient browsers. Even medium-age browsers are out of luck long since: https://msfn.org/board/topic/182248-what-i-think-about-the-new-forum-software-and-revamped-ui/ There have been heavy complaints even for popular NewMoon27 (KM76) on XP, and guess younger versions too. And am afraid, the control bar (button row in Editor area) is killed completely by semi-modern javascript, requiring Firefox31? Have seen JS attaches a file named "promise.js" to the editor, and inside it mentions something about ES6Promise - and it loads messageChannel?! IIRC that feature started working in KM76 (FF38), but why such an intrusive function just for adding a few text snippets around selected text? Grmpf... Regarding Layout / CSS-styles: The whole forum now seems to depend heavily on over 100 CSS-Variables! Very handy feature I admit, have missed it dearly since forever, but sadly the browsers added it far too late to engines. No wonder KM1.6 has lost just about ALL styling after this ips-update Still busy researching this feature... KM74(FF24) can't handle it either yet, only starts in FF31 (KM75) acc web. Yet anyway, in KM74 the page looks a whole lot better, this version definitely gets somehow almost normal styling - except by default it shows black text on darkgray background! The curse of having brandnew functions, but only in most basic version yet. And a few other minor glitches I can fix myself. Note KM74/FF24: howto get rid of dark background: set in user css body{background-image: none !important} https://msfn.org/board/topic/182251-old-browsers-ips-forum-layout-bugs-self-help-tweaks-css/ Oh well, CSS can all be worked-around, but the real KILLER prob is javascript. Especially the editor buttons, sigh, that's the worst bug, and afraid unfixable in older browsers . The editor now wants lot of too modern javascript, IMO completely unnecessary, but that stuff is decided by the invision devs. In KM I can happily use a macro that creates a context menu, to set selected to bold or underlined etc., but in FF no clue. Other people can surely find their own workarounds, using external tools with macros, or perhaps addons, whatever. .

I dislike the the new UI because I dislike the rounded nature of the new UI, the broken older browser compatibility, hidden edit button, and most of all, the trimmed email notifications. Even on mobile, I prefer the desktop UI over the new bottom control iOS copy UI. New Email Notifications (I use a dark theme): https://i.imgur.com/pRV4oo5.png Old Email Notifications: https://i.imgur.com/MYUJgbb.png I don't like it, and the biggest issue to me isn't even with the site itself, it's with the emails being cut off. Edit: Also, certain parts of the forum are much slower with the new UI and software.