Entfernt unnötige Elemente von der Fandom-Website und lässt nur das Wichtige übrig.
< Rückmeldungen auffandom.com - Bloatware entfernen
Actually, the combination of massRemove with body > svg + * results in images being unexpandable. I think to avoid this, you basically need to prevent the event handler callbacks on all the image anchors so they can open as regular hyperlinks. They are extremely bloated with all kinds of event handlers so it would be pretty difficult to do. Probably better to just let the inline image preview system work as normal.
That said, anyone reading this shouldn't take it as a dealbreaker necessarily, as middle click or ctrl+click can still work. Or right click -> context menu -> open link in new tab. That kind of thing still works.
Actually, the combination of
massRemovewithbody > svg + *results in images being unexpandable. I think to avoid this, you basically need to prevent the event handler callbacks on all the image anchors so they can open as regular hyperlinks. They are extremely bloated with all kinds of event handlers so it would be pretty difficult to do. Probably better to just let the inline image preview system work as normal.That said, anyone reading this shouldn't take it as a dealbreaker necessarily, as middle click or ctrl+click can still work. Or right click -> context menu -> open link in new tab. That kind of thing still works.
I am already leaving skin-fandom class alone on the body so i could do the same with whatever class dark reader uses
Good, but I'd add
#mixed-content-footerto removeListSingle - it's a "Fan Feed" at the bottom of the page.Also, removeExcessiveBodyClassNames has a troublesome interaction with Dark Reader. I removed it from the MutationObserver but left the top-level call and it seems to work okay. I can see why you did this, but it does limit the script's utility somewhat, since userscript users are also pretty likely to be Dark Reader users.
Even so, nice work - removing the selection popup alone is much appreciated, that has been driving me crazy on every fandom page. This UX trend really needs to go the way of the dinosaur. Thank you!
I did remove #mixed-content-footer at the start but sometimes important info can be left by people in the comments
Feel free to make a pull request for any of your suggestions as this extension is not my main focus right now.
Good, but I'd add
#mixed-content-footerto removeListSingle - it's a "Fan Feed" at the bottom of the page.Also, removeExcessiveBodyClassNames has a troublesome interaction with Dark Reader. I removed it from the MutationObserver but left the top-level call and it seems to work okay. I can see why you did this, but it does limit the script's utility somewhat, since userscript users are also pretty likely to be Dark Reader users.
Even so, nice work - removing the selection popup alone is much appreciated, that has been driving me crazy on every fandom page. This UX trend really needs to go the way of the dinosaur. Thank you!