LogFAQs > #892565512

LurkerFAQs, Active DB, DB1, Database 2 ( 09.16.2017-02.21.2018 ), DB3, DB4, DB5, DB6, DB7, DB8, DB9, DB10, DB11, DB12, Clear

Topic List	Page List: 1
Topic	Which browser do you use?
Dikitain 12/20/17 11:39:23 AM #28:	kind9 posted... Questionmarktarius posted... kind9 posted... The developers of those extensions have the responsibility to keep up to date. Give it time and your extensions, if they are worth a damn, will be updated. The backend has been gutted so badly that the needed APIs don't exist for such things as UI tweaks, cookie manipulation, and download management, all of which worked reasonably well in FF56. Gutted, as in removed completely? Are you sure the API hasn't just changed? If they actually removed those things then that's pretty fucking stupid on Mozilla's part. The new one uses a WebExtensions SDK (the same thing used for plugin support in Chrome and Opera), whereas the old one used an Add-Ons SDK. It gets kind of complicated to explain, but basically anything that would change core functionality of the browser is not allowed in WebExtensions (but was allowed in Add-Ons). In one sense, it is sort of fixing a security loophole. However, it also greatly limits what you can do with plugins. --- I am a senior software engineer. If you see me post here, I am tired of writing TPS reports. <cite>Dikitain posted [p:892565512] in Which brow... [t:76114910]...</cite> <quote><cite>kind9 posted...</cite> <quote><cite>Questionmarktarius posted...</cite> <quote><cite>kind9 posted...</cite> <quote>The developers of those extensions have the responsibility to keep up to date. Give it time and your extensions, if they are worth a damn, will be updated.</quote> The backend has been gutted so badly that the needed APIs don't exist for such things as UI tweaks, cookie manipulation, and download management, all of which worked reasonably well in FF56.</quote> Gutted, as in removed completely? Are you sure the API hasn't just changed? If they actually removed those things then that's pretty fucking stupid on Mozilla's part.</quote> The new one uses a WebExtensions SDK (the same thing used for plugin support in Chrome and Opera), whereas the old one used an Add-Ons SDK. It gets kind of complicated to explain, but basically anything that would change core functionality of the browser is not allowed in WebExtensions (but was allowed in Add-Ons). In one sense, it is sort of fixing a security loophole. However, it also greatly limits what you can do with plugins. --- I am a senior software engineer. If you see me post here, I am tired of writing TPS reports.</quote> ... Copied to Clipboard!
Topic List	Page List: 1