4 ms·
I can't guarantee its safety, but I glanced at his JS, and it seems harmless. (later edit: I probably should have posted this during the day to give someone a
by brfox 18y ago
I can't guarantee its safety, but I glanced at his JS, and it seems harmless.
(later edit: I probably should have posted this during the day to give someone a chance to fix it so no one new actually exploits this... should I delete it?)
- thaumaturgy 18y agoPretty clever too. Click on the logo & letters on the bottom and you can throw them around.
- deleted 18y ago[deleted]
- LogicHoleFlaw 18y agohttp://pastebin.com/f1c2d17cf http://pastebin.com/f1c2d17cf That's a pretty-printed and syntax highlighted view of the JavaScript in question. Edit: slightly cleaned up the formatting. Also! Line 75 confuses me (and jsLint) a bit. What's that up to?
- gojomo 18y agoThat's an HTML-escaped less-than. (I assume pastebin inserted the space between the '&' than the 'lt;'. This is line 75's unescaped: for (e = 0; e < sup.length; e++) {
- LogicHoleFlaw 18y agoAha, indeed. I cleaned up the errant html escapes, resulting in the following pastebin: http://pastebin.com/f1343e50a http://pastebin.com/f1343e50a That gets the jsLint errors down to complaints about assignments in loop conditions. So no biggie.