User talk:FireFly: Difference between revisions
Content added Content deleted
(→Quine: comment: wow!) |
m (Responded) |
||
Line 4: | Line 4: | ||
Question: '''Why''' doesn't it work in MSIE? -- [[User:Eriksiers|Eriksiers]] 00:32, 28 January 2010 (UTC) |
Question: '''Why''' doesn't it work in MSIE? -- [[User:Eriksiers|Eriksiers]] 00:32, 28 January 2010 (UTC) |
||
: It's probably compiling/interpreting the HTML differently, and likely doesn't allow reassigning elements from being header material to body after it has started interpreting. Given how twisted what that code is (if I had a hat on, I'd take it off in honor of it!) I'm not very surprised that it has issues with IE. –[[User:Dkf|Donal Fellows]] 10:45, 28 January 2010 (UTC) |
: It's probably compiling/interpreting the HTML differently, and likely doesn't allow reassigning elements from being header material to body after it has started interpreting. Given how twisted what that code is (if I had a hat on, I'd take it off in honor of it!) I'm not very surprised that it has issues with IE. –[[User:Dkf|Donal Fellows]] 10:45, 28 January 2010 (UTC) |
||
:: CSS didn't even exist when Internet Explorer was first released, so IIRC the Trident CSS support has always been a bit rusty. The idea is that the head and style elements normally are set to "display: none", but I override it by setting it to display as a block element (which prints out its content). It's probably as [[User:Dkf|Donal Fellows]] suggested, IE probably simply never adds the style element to the (rendered) tree of elements. Also, I think it has troubles with the ::before and ::after pseudo-elements. -- [[User:FireFly|FireFly]] 11:48, 28 January 2010 (UTC) |
Revision as of 11:48, 28 January 2010
Quine
I don't understand how it works, but your HTML + CSS Quine solution is genius.
Question: Why doesn't it work in MSIE? -- Eriksiers 00:32, 28 January 2010 (UTC)
- It's probably compiling/interpreting the HTML differently, and likely doesn't allow reassigning elements from being header material to body after it has started interpreting. Given how twisted what that code is (if I had a hat on, I'd take it off in honor of it!) I'm not very surprised that it has issues with IE. –Donal Fellows 10:45, 28 January 2010 (UTC)
- CSS didn't even exist when Internet Explorer was first released, so IIRC the Trident CSS support has always been a bit rusty. The idea is that the head and style elements normally are set to "display: none", but I override it by setting it to display as a block element (which prints out its content). It's probably as Donal Fellows suggested, IE probably simply never adds the style element to the (rendered) tree of elements. Also, I think it has troubles with the ::before and ::after pseudo-elements. -- FireFly 11:48, 28 January 2010 (UTC)