Re:How to Write CSS That Works in Every Browser, Even the Ol...
by pluma on Friday March 09, 2018 @04:29AM
(#16550654)
Remember when console.log was available when the dev tools were open but would be undefined otherwise, so your code would break unexpectedly but then work fine when you tried to figure out what went wrong?
Re:How to Write CSS That Works in Every Browser, Even the Ol...
by laxd on Friday March 09, 2018 @11:50AM
(#16552989)
Oh gaahd, It's all coming back to me now.
function log(msg) { if (console.log) console.log(msg) }
Re:How to Write CSS That Works in Every Browser, Even the Ol...
by Yaggo on Friday March 09, 2018 @07:05AM
(#16551174)
> safari and older ie versions. 10 for sure.
This is false information about Safari. In fact, Safari was the first browser to implement 100% ES2015 support.
https://developer.apple.com/safari/technology-preview/releas...
Re:How to Write CSS That Works in Every Browser, Even the Ol...
by neonhomer on Thursday March 08, 2018 @07:35PM
(#16548957)
It was terrible when the only thing you could do was alert your variables!
Re:How to Write CSS That Works in Every Browser, Even the Ol...
by geocar on Thursday March 08, 2018 @07:55PM
(#16549064)
Back in the day I used LiveConnect[1] for this and other purposes[2]. I would dump errors to an IRC server so that I could collect the results. I could also respond with code that would be eval'd making development very easy.
[1]: https://developer.mozilla.org/en-US/docs/Archive/Web/LiveCon...
Re:How to Write CSS That Works in Every Browser, Even the Ol...
by tonyarkles on Thursday March 08, 2018 @09:54PM
(#16549512)
> I could also respond with code that would be eval'd making development very easy
In dev only, I hope?! I honestly love the idea as a super fun hack, but the security implications for prod are terrifying.
Re:How to Write CSS That Works in Every Browser, Even the Ol...
by geocar on Friday March 09, 2018 @05:21PM
(#16555528)
Not sure there was much risk: The web application used a private IRC server with name+password registered users. L3 support who /msg'd a user session some JavaScript doesn't seem likely as the messages were all logged, and anyone with fileserver access could just put whatever they want in the <script> tag anyway...
Remember when console.log broke ie? Debugging was fun.