@computionist @notSorella @bascule The fact you can't see the nested languages in 'view source' is one source of encoding mistakes.
-
-
Replying to @mountain_ghosts
@jcoglan@computionist@notSorella@bascule (A) No exposing server-side code anyway. (B) Nested code in FF is 1 click (per file of course).1 reply 0 retweets 0 likes -
Replying to @eachus
@eachus@computionist@notSorella@bascule I'm not sure what A means, and how exactly do I do B?2 replies 0 retweets 0 likes -
Replying to @mountain_ghosts
@jcoglan@computionist@notSorella@bascule I didn't see the whole conv... I was not sure by "view source" if you only meant client side.1 reply 0 retweets 0 likes -
Replying to @eachus
@eachus@computionist@notSorella@bascule I do, but I want to see all the mashed-together languages present in an HTML doc, as a tree.2 replies 0 retweets 0 likes -
Replying to @mountain_ghosts
@jcoglan@computionist@notSorella@bascule But heck, even just inline would often be an improvement.2 replies 0 retweets 0 likes -
Replying to @eachus
@eachus@computionist@notSorella@bascule Inlining external files would *contribute* to this problem, not fix it.2 replies 0 retweets 0 likes -
Replying to @mountain_ghosts
@jcoglan@eachus@computionist@notSorella yup, inlining is nasty, see e.g. CSP script-nonce4 replies 0 retweets 0 likes -
Replying to @bascule1 reply 0 retweets 0 likes
@jcoglan @eachus @computionist @notSorella https://dvcs.w3.org/hg/content-security-policy/raw-file/tip/csp-specification.dev.html#valid-nonces …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.