Jump to content

Recommended Posts

Another forum site which does not render correctly is
www.hörspieltalk.de

In the threads, several navigation elements are missing or not displayed correctly. For example:
https://www.hörspieltalk.de/forum/thread/16483-asterix-universal-music/
is 11 pages long, and all page navigation elements are missing. Also the empty grey squares on the right are supposed to contain action buttons such as "share" and "react".

I also cannot login on the site with my credentials. The error message I always get is "The validity of your request could not be verified, because the XSRF token was invalid. Please submit the form again." The only way to login is using another browser, then copying the cookies.sqlite file into the Mypal profile folder.

(The rendering and login problems may be unrelated to each other.)

Link to comment
Share on other sites


While Fedor2 has not released the SSE version of the browser, I think we have the opportunity to influence what it will be like.

What would you all like to see in SSE? For example, how should videos be played or pdf documents opened on very slow computers?

Link to comment
Share on other sites

On 11/19/2023 at 9:42 AM, AstroSkipper said:


@feodor2 Ok! I tried myself. I removed the code marked with - and added the code marked with +, both simply manually. Works great! The Custom Buttons extension seems to be fully functional, and extensions which couldn't be installed before due to the message "Installation aborted because the add-on appears to be corrupt" can now be installed without any warnings. Is that what the code change is supposed to achieve? :dubbio:In any case, I will test this new code more deeply the next days, but first of all, a big thanks! :thumbup

<OT>

If my memory serves me, it was you that had Covid here, if not, I apologize. If so, do you STILL have lingering symptoms? I tested positive last April after becoming mysteriously ill and went around for the way for 3 weeks Until I was hospitalized but I was not intabated just sent home with PaxLovid - were you are also put on that medication? Sorry for all the questions and if I bother you by prying feel free to tell me but I'm trying to figure out long I should expect to feel ill like my short-term memory is shot and my emotions are 'all over the place'. Hands shaky and it takes me a million times to edit my posting to make some kind of sense and I have VERY low energy.

Take good care anyways and I do hope you are well and recovered 100%..

~Salvatore

EDIT:

Oh I just recalled @UCyborg also had Covid are you recovered to 100%?

<OT>

Edited by XPerceniol
Link to comment
Share on other sites

4 hours ago, grey_rat said:

Software webgl angle for MyPal 68

Hi @grey_rat!  Can you give details on how to do this? I read and downloaded the stackoverflow files, but the instructions there are for chrome.

Also, you may be interested in this. It used to work long ago, but probably is more related to sp52.

https://bugzilla.mozilla.org/show_bug.cgi?id=1297182

Link to comment
Share on other sites

Cool. I will try and see.

As per XP can't do gpu processing, people keep saying things like that, the way it's said you can't run chrome 54+ in xp, you can't run firefox 52+, etc. etc. A combination of successful oligopolistic PR campaigns, and a Tobin like mix of laziness and pretended savvy. Not to include you in that group (I have great respect for what feodor  you and others are doing, and enjoying the product of your efforts, thanks).

But it could be done, limitedly between FF4 and FF51. Outside browsers, it could be done to watch videos/music using (at least) an experimental MPC-HC build at https://forum.doom9.org/showthread.php?t=161047 least) combined with lavcodecs rendering on Nvidia Cubid, and madhctrl. Nvidiaprofileinspector (another thing that now goes as "can't be run in XP") also helped. GPU processing was also used by statistical packages that require it to run large monte carlo simulations. Just sayin.

 

Edited by dmiranda
Link to comment
Share on other sites

ON another note, setting user_pref("permissions.default.shortcuts", 2); , where 0 is default 1=allow 2=block prevents page overriding of FF shorcuts, but breaks delete and backspace. The immediate solution is setting this to 0. This dev claims he has a solution that allows you to prevent page overriding of FF shortcuts, while keeping delete and backspace functional.

https://superuser.com/questions/1510447/delete-button-del-button-is-broken-in-firefox-when-sites-are-blocked-from-over

 


 

Link to comment
Share on other sites

@feodor2 The website https://www.camp-firefox.de/ works no longer correctly in Mypal 68 for a few days. Especially the site search function https://www.camp-firefox.de/suche/ is broken. Here is the output of the Web Console:

SyntaxError: private fields are not currently supported WebComponent.min.js:58:1408
ReferenceError: WoltLabLanguage is not defined de.preload.js:2:1
SyntaxError: private fields are not currently supported WoltLabSuite.Core.tiny.min.js:1:33256
ReferenceError: requirejs is not defined suche:49:1
ReferenceError: define is not defined WoltLabSuite.Forum.tiny.min.js:1:1
ReferenceError: require is not defined suche:531:2
ReferenceError: define is not defined suche:561:2
ReferenceError: define is not defined suche:566:2
ReferenceError: require is not defined suche:607:3
ReferenceError: require is not defined suche:612:2
jQuery.Deferred exception: SECURITY_TOKEN is not defined init@https://www.camp-firefox.de/js/WCF.Combined.tiny.min.js?v=1701002591:19:8603
i@https://www.camp-firefox.de/js/WCF.Combined.tiny.min.js?v=1701002591:16:191
init@https://www.camp-firefox.de/js/WCF.Combined.tiny.min.js?v=1701002591:43:226
@https://www.camp-firefox.de/suche/:577:38
f@https://www.camp-firefox.de/js/WCF.Combined.tiny.min.js?v=1701002591:4:38929
o/</p<@https://www.camp-firefox.de/js/WCF.Combined.tiny.min.js?v=1701002591:4:39232
 undefined WCF.Combined.tiny.min.js:4:40512
jQuery.Deferred exception: require is not defined addObject@https://www.camp-firefox.de/js/WCF.Combined.tiny.min.js?v=1701002591:19:13911
@https://www.camp-firefox.de/suche/:592:17
f@https://www.camp-firefox.de/js/WCF.Combined.tiny.min.js?v=1701002591:4:38929
o/</p<@https://www.camp-firefox.de/js/WCF.Combined.tiny.min.js?v=1701002591:4:39232
 undefined WCF.Combined.tiny.min.js:4:40512
ReferenceError: SECURITY_TOKEN is not defined WCF.Combined.tiny.min.js:19:8603
ReferenceError: require is not defined WCF.Combined.tiny.min.js:19:13911
This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see https://developer.mozilla.org/docs/Mozilla/Performance/ScrollLinkedEffects for further details and to join the discussion on related tools and features! suche

There is a lot not defined. Have a look above! The admins of this websites must have recently performed changes. :realmad: In New Moon 28 and Serpent 52, the site search surprisingly works. :thumbup

Link to comment
Share on other sites

18 minutes ago, UCyborg said:

Private class fields are supported since Chrome 74/Firefox 90/Pale Moon 32.2.0.

Yes, they probably updated their CMS, in this case WoltLab Suite Core.

Thanks for the information! Then the chances are quite good that after @feodor2's switch to JS Engine 91, some things will work again.

Link to comment
Share on other sites

Like we all (I guess) knew, by going the chrome way, FF not only abandoned a vibrant addons community, but included a bunch of telemetry, to better serve us, laf. Three things to reduce/mitigate this behavior:

1- In your profile folder include an empty, extension-less file called "Datareporting". This prevents the creation of the folder.

2- We all have seen those pesky mojeek and brave search items popping in every now and then. You can delete them, but they comeback every nor and then, and are listed as extensions in about:support.  Download the attached related file.  Open extensions.json (from your profile) using notepad+++ (pspad freezes for some reason opening it). Copy and search for Look the code in brave, mojeek.txt file, and find the equivalent in extensions.json (they will have changes in ui, as per your installation, so copy and paste over won't do the trick). Once you found the code, delete it manually. Once you selected in this json (make sure they correspond perfectly, or modify as required. DELETE THOSE ITEMS FROM extensions.json. Brave and mojeek, bye bye.

3- Activate these (many hidden, some probably useless, but hey) items in user.js -or one by one using about:config. See included attachment.

 

telemetry items for user.js brave, mojeek.txt

Edited by dmiranda
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...