httpswitchboard
httpswitchboard copied to clipboard
gorhill
Feature request: Option(s) to hide blocked elements
One thing I notice about httpswitchboard that's very different from AdBlock: Blocked elements are not fully hidden. I see broken images and areas where iframes would be. Sometimes I want to see these things, but most of the time I don't. Could there be option(s) to hide these with CSS display:none, please?
I see an option to change the color of removed iframes, but that doesn't quite cover it.
Well, in case Ken-g6 wasnt clear, this is not very effective: 
That's a video stream with a blocked ad over it. Even if I set "Blocked frames color" to transparent, the box that says the domain of the blocked frame still appears.
EDIT: Ok, (I think) I now see what you meant. Anyways this is a feature request so it's your call. In my opinion it's a good idea to have that option (it could be off by default).
Well, since @gorhill shot me down I've been trying to fix this with user styles/scripts. My efforts with iframes were less than successful, at least so far, but I got broken images to disappear. (All broken images.)
https://gist.github.com/Ken-g6/8d467443b9f62c631bf7
Edit: Seems to have had some effect on other images too, though. Back to the drawing board.
Edit2: And I think I have a better approach there now.
Ok I see the white box, which defeats the purpose of allowing transparent frame. Will look into a fix.
Meanwhile you may want to try this ubiquitous rule in the Your block rules text area: ptcanal.com###above
Looks like this should be proposed for inclusion in ABP EasyList.
@ruimams I move the transparency problem to issue #299, as it is a separate issue from the feature requested here.
And I think I have a better approach there now.
For HTTPSB something will be needed though, since an error not caused by HTTPSB could cause an image to not be loaded, and in such case I doubt hiding the image is a good thing.
I will thin about the best way to implement this properly in HTTPSB, which certainly involves communication between the injected content script and the background page.
@gorhill Great, thanks. I thought it was intentional so you could "See ALL the remote connections, failed or attempted(...)" (quoting README.md) and that was why I was rooting for the hiding of blocked elements.