![]() That sort of thing is probably typical of Firefox. It may have disappeared at any point between Firefox versions 109 & 111.0.1. In any case, that unifiedExtensions preference no longer exists in about:config. ![]() We've had a couple of updates, since then, including 111.0.1 which just came out. ![]() At the time I made my comment, I was running Firefox 109.0. I was struck by a comment I made above about unifiedExtensions in about:config. I just recommended another user find this thread & read it. Imagine another such period of pain is in our future. ![]() Michel had to change theĪrchitecture of VDH & he had to invent the CoApp. TheĪdvent of Firefox Quantum 50+ releases back did exactly that. Having the rug yanked out from under out feet. When it comes to the future being different, I suppose we are always under threat of I'm glad you figured out a way around your problem. Preference is set to true, & extension behavior on my system is still "old." But onceĪgain, this is quite likely due to my system being Windows 7. More, including all the x.x & x.x.x updates. So I have accumulated who knows, maybe 100 updates or I indeed have simplyĪdded updates to Firefox for I can't count how many releases. Interesting what you say about unifiedExtensions.enabled, Sarge. Learning when you migrate to a new release. They are in new places, thus maximizing the learning curve while minimizing the actual Sure, all the various features are there, but Without improving from release to release. This is another example of how things change This doesn't lookĪnything at all like what Jérôme posted. But as you can see, it is completely different in Windows 7. ![]()
0 Comments
Leave a Reply. |