<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - iOS 9 Beta 3 Content Blocker Extension - Enable CSS Display Inline"
href="https://bugs.webkit.org/show_bug.cgi?id=146884#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - iOS 9 Beta 3 Content Blocker Extension - Enable CSS Display Inline"
href="https://bugs.webkit.org/show_bug.cgi?id=146884">bug 146884</a>
from <span class="vcard"><a class="email" href="mailto:benjamin@webkit.org" title="Benjamin Poulain <benjamin@webkit.org>"> <span class="fn">Benjamin Poulain</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=146884#c1">comment #1</a>)
<span class="quote">> > We have access to the selector css-display-none to hide our own elements,
> > but it would be great if we can also have access to css-display-inline
> > and/or css-display-block to un-hide elements.
> I do think this might be useful, but I don't think that this would prevent
> websites from detecting if content has been blocked.</span >
We could also make CSSOM lie about the element. Reporting the display as if the user stylesheet was not installed.
But I don't think that would work either. There are many visible side effects to content blocker, they would just move on to the next one.
Dean, can you give us your example of website that break with your content blocker? If it cannot be shared publicly here, feel free to email it to Alex and myself.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>