0x1b.pw##IMG:first-child
But I imagine you could work around this by adding a null IMG element before the ad. Also, I'm pretty sure this would break any non-toy page.
[1]: https://addons.mozilla.org/en-US/firefox/addon/elemhidehelpe...
11–20 of 46 posts
0x1b.pw##IMG:first-child
But I imagine you could work around this by adding a null IMG element before the ad. Also, I'm pretty sure this would break any non-toy page.
[1]: https://addons.mozilla.org/en-US/firefox/addon/elemhidehelpe...
ermm? Just right click the image, adblock -> remove this image. Of course reloading the page will bring it back due to way it's done, I guess that's supposed be the challenging part.
For tracking, security, and analytics reasons, ad providers almost always originate ads from a separate domain than the content provider's.
With the element hiding extension[1] installed: 0x1b.pw##IMG:first-child But I imagine you could work around this by adding a null IMG element before the ad. Also, I'm pretty sure this would break any non-toy page. [1]: https://addons.mozilla.org/en-US/firefox/addon/elemhidehelpe...
This is a pointless challenge, because it has none of the characteristics of an actual ad. For tracking, security, and analytics reasons, ad providers almost always originate ads from a separate domain than the content provider's.
With the element hiding extension[1] installed: 0x1b.pw##IMG:first-child But I imagine you could work around this by adding a null IMG element before the ad. Also, I'm pretty sure this would break any non-toy page. [1]: https://addons.mozilla.org/en-US/firefox/addon/elemhidehelpe...
Updated, not the cleanest way to do it but indeed adding a dummy image as the first child should stop it.
// First clear the interval assigned to window
var highestTimeoutId = setTimeout(";");
for (var i = 0 ; i