Siiigh.... OOPS-2:
Now struggled an hour trying to figure out why a
webpage was completely empty and all the usual workarounds didn't help a thing (especially when forgetting to toggle adblock off too!) - until finally noticing this in their html source code:
<body class="vollbild cookie-hint">
www.medizinfuchs.de/wirkstoffsuche/Chloroquin.html
Oh great, I did suspect those universal rules for ALL web pages are probably too strict, but something like
that is an additional challenge.... As next workaround may try to set ALL "html, body" to visibility:visible and display:block etc. But will not help of course if servers wrap their whole page into some inner elements, in "div" etc.
But next time will
remember sooner to just toggle adblock off :cool:
Now testing those experimental rules, which must be placed BELOW the cookie-killer rules.
And which will of course have other side-effects too...
html[id], html[class], html body[id], html body[class] {
display: block !important;
visibility: visible !important;
position: relative !important;
height: auto !important;
max-height: none !important;
width: auto !important;
max-width: none !important;
overflow: auto !important;
}
@JohnHell:
Yep, that's another possibility. But then it's not working when viewing a locally saved web page again. There are pro's and con's for every method. A trap could also be to forget this global URL-condition when adding site-specific URL rules, accidentally nesting -moz-document conditions, which didn't work at all when I tried last time. Of course, if someone is diligent and takes care to keep universal rules and site-specific rules separate, all works fine :-)
Edited 1 time(s). Last edit at 03/08/2020 06:53PM by siria.