feodor2

I I already have such extensions, and i know what to do when i poke the extension. While it is bad thing to remove META-INF folder without good reason only to make it unsigned, you may get it broken, not all though.

Sure its necessary sometime. Here that was not necessary, also right after i asked not to do this. So whats wrong if i ask not to spam with pictures?

@athlonxpuser Yes, i do not like pictures in such realm, what is possible to elaborate with few words not needed a bunch of fullscreen pictures, This is distracts confuses and a waste of space - so consider spam. Please dont be lazy type words

@a8s after checked fullscreen Not at all never used this. @seven4ever This is about media center? Do you have sp3 there? And for x64 is already written look on the github @AstroSkipper I asked to stop spaming with pictures but you are keep doing this, what do you expect then? And not even care to provide the link for your insigned addon, so why i to care, fix it on your own. , Okey, this is not the feature itself, you still get warning about unsigned addon. But config.js stuff is really not needed and breaks addons operational integrity indeed.

@a8s Actually this is not seen and not obvious, now i do reproduce the error. Hey i confused with tab_mix_plus so tab_manager_plus installs good via drag&drop too, so we get back to the point of this is error does not reproduce. Meanwhile you can install the addon from the mozilla site without error there. Did you try this?

Pictures are unnecessary at all, i understand that here is easy to put the picture, but i consider this is a spam. So everybody please post the picture only when explicitly asked. @a8s I took clean 13.5 and tried to reproduce the error, but failed. May be you have network problem and actually get corrupt file. Do right click on the blue button ans select "save link as" to save the addon file, then try install from file. Also what happens when you enable the addon after import from an older 3b profile?

Yes. After i publish the new version, and then sse version, supposed next year i begin to move javascript to 91 version, i think this whats is very important. You may to proove me otherwise

Yea https://github.com/Feodor2/Mypal68/issues/53 I think this is so unimportant still no take a time for fix.

The new version is ready, but i want to amend adoons case. I have taken the new version and 13.3 and installed these addons I don't know how to use rss-html, never use this stuff, http-indicator alwasys shows the grey icon don't know is this right. sixindicator shows nothing this only one may be don't works at all Other addons seems works good, by the way i find tab-manager-plus-for-firefox good for me and shall use it further. And this all on both versions no differnce, someone else please check too.

Yes. After the next release i shall begin to make sse version, if all will be good it will be complete before the year end.

New version has bug that breaks ublock and other extensions, sorry i deleted it. The update will be next week.

Check the new version where this may be not needed.

@grey_rat just stop, it is no any need to repeat already learnt.

It is counted both either layers.enable-tiles or layers.enable-tiles-if-skia-pomtp you will get BSOD too then, so no point to check. Meanwhile to narrow the thing i suggest to check another thing: Look about:support Off Main Thread Painting Worker Count if it > 1 then set layers.omtp.paint-workers 1 while layers.omtp.enabled - true and layers.enable-tiles-if-skia-pomtp - true

Let summing-up for today BSOD may be happen not only upon shutdown, layers.omtp.enabled affects both cases. @MWF picture of the notepad is useless, pictures of the crash also useless at all, only drwastson log will be useful. I asked put all files list, not picture but text Next you delete these files, set two webgl things and open about:support - these actions certainly cause crash upon shutdown, but i want to know it is only crash or bsod also. And will be the filelist the same or not, that's why delete files and look what second time.

Yes, or layers.omtp.enabled false, but this affects some things too, look the one good example

BSOD happaned upon shutdown, bug with OMTP. @MFW seems you told get bsod even when browsing, who else also gets? This maybe different case at all While i had last bsod long ago before, never on newer versions past 68.13. However i begin working on x64 version, but before i shall do the small update release because of sites dumperlopers lunacy about queueMicrotask, they push it everywhere possible, too many sites now broken.

The BSOD problem may be resolved, check the new version.

I was really going to apply 1429838 but missed, i consider this not important either, though i can do upload the fix if you really want The fix about extension view hes been uploaded on github 286 I continue to research the OMTP No, until complete its depedns on, so far be happy if it works for the dicord without error

@MWF @mina7601 nothing to do about, whos to know what it wants now, i shall check on 91 later. Also what about other xp browsers?

@curiosil ask here should not to make new forum https://github.com/Feodor2/Mypal/wiki/Portable#advanced-stuff Also new version is coming, where fixed moving portables to different places

This is not about win7, also i think the hazard is very exaggerated, i searched and could not found any infected webp. Iet i check if you already have found one please do zip it with password and put the link. Be not afraid i update libwebp with the fix.

@Anbima Most likely the next week, new version is almost ready. But it will be no changes regarding languages since 16.13, so you not need to wait.

Where to look actual how scary the CVE thing, for do i bother to updootes? The page on the mozillas is "access denied"

@tinman2000 The site loads and i can see it, but after some time the error shows. Console shows "A client-side exception has occurred, see here for more info: https://nextjs.org/docs/messages/client-side-exception-occurred" This is funny when i open that link i get the same error, not funny to think about how stupid modern developers, to break the whole site if some minor thing fails. You may write about this everywhere - let nextjhs make software for plane control whatever. I think the error itself will be fixed when will update engine to 91. @Jody Thornton How was it works before, remember what was changed and set it back, what about "always open in private browsing mode"? No such addon on the mozilla site, why do you want it? Why it messes with cookies? As for dom.indexedDB.enabled this do nothing, on mypal68 it is always enabled. Anyway suppose you have some backup, the regular new tab things are in the places.sqlite