~dr|z3d
@RN
@T3s|4
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
%acetone
%snex
+FreefallHeavens
+Leopold
+Xeha
+ardu
+bak83_
+hk
+profetikla
+qend-irc2p
+r00tobo
+uop23ip
+weko
Arch
BubbRubb1
Danny
DeltaOreo
FreeB
HowardPlayzOfAdmin
Irc2PGuest19950
Irc2PGuest41581
Irc2PGuest85438
Irc2PGuest95056
Meow
Onn4l7h
Onn4|7h
StormyCloud_
altonen
anontor
boonst
l337
maylay
not_bob_afk
not_human_
poriori_
r00tobo[2]
shiver_
solidx66_
thetia
tr
u5657
zer0bitz
zzz
dr|z3d, you familiar with FOUC problems?
dr|z3d
LOL
dr|z3d
I had to look that acronym up.
dr|z3d
yes, familiar.
dr|z3d
for others that may be curious, and lazy: en.wikipedia.org/wiki/Flash_of_unstyled_content
dr|z3d
what's the issue, zzz?
zzz
yeah I'm consistently seeing it in firefox on proxy error pages
zzz
presumably because the css is from proxy.i2p, or tab isolation, or something
zzz
are you seeing it or have fixed it somehow?
dr|z3d
fixed in +
zzz
a js fix seems like a nonstarter, but I could inline the css on-the-fly I guess
zzz
how?
dr|z3d
*** does a twirl. "magic!" ***
dr|z3d
I hide the body of the document via css and then enable when the css is loaded.
dr|z3d
<body id=proxy_error style=display:none;pointer-events:none>
dr|z3d
then at the end of the document..
dr|z3d
<style>body{display:block!important;pointer-events:auto!important}</style>
dr|z3d
you could alternatively do what you do on zzz.i2p
zzz
ok, the first is in the .ht file and the end has to be added by the error page puker
dr|z3d
correct
zzz
and at the cost of CSP css unsafe-inline
dr|z3d
style-src 'self' 'unsafe-inline' proxy.i2p;
zzz
yup
zzz
hmm
zzz
so 3 choices: js, inline the whole CSS in the head, or what you did
dr|z3d
in case you're not familiar with pointer-events, it prevents elements from being clicked on (and re-enables it at the bottom), so you don't have clickable, invisible elements.
dr|z3d
or #4. use an import statement in the head.
dr|z3d
js is a non-starter.
zzz
have you tried import? not familiar
dr|z3d
I prefer what I'm doing. look at zzz.i2p to familiarize yourself with import.
dr|z3d
when you use import, it's blocking.
dr|z3d
I use import for the console, fwiw, in the css files, not in the head element.
zzz
actually I already have style-src unsafe-inline
zzz
but import sounds like the cleanest way to do it, why did you like the inline style at the bottom better?
dr|z3d
more control over how the page is displayed once the css is loaded, generally speaking.
dr|z3d
in the proxy, it's a straight, hide/show routine, but elsewhere I might add a very quick fade so it's less aggressive.
dr|z3d
also, you're all or nothing with import.
dr|z3d
with my current method, the css can load, the content then has to load, and in the interim, if the css has loaded but the content hasn't, you get the page background displayed, not white.
dr|z3d
I don't like watching the DOM render, though that's unlikely an issue with proxy errors.
zzz
your way might be more appropriate for the console, perhaps dealing with huge pages, but for proxy pages, import sounds like the right solution?
dr|z3d
whatever suits, import will be fine.
zzz
ok thanks this was very helpful. I'll give import a try and report results
dr|z3d
you're welcome.
zzz
have a FOUCed day ))
dr|z3d
FOUC off! :)
dr|z3d
(when you apply the fix)
dr|z3d
zzz: do the snark xml files require the refid update?
zzz
hmm.. checking...
zzz
yes, there's one dup in there, good catch
dr|z3d
*thumbs up*
zzz
and the DTD
dr|z3d
yeah, 9.3
zzz
zzzot also has the issue