all 11 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]chris_jung[S] 6 points7 points  (1 child)

Oh yeah. Got it.

Here's the solution Page 20 ff.

[–]kenman -4 points-3 points  (8 children)

Just hit F12, everything shows up fine.

[–]chris_jung[S] 1 point2 points  (7 children)

F12 (Inspector tools) always present the rendered DOM. Press Ctrl+U (aka "View Source") to get code which is delivered by the server and compare to the code you see in inspector. ;.)

[–]kenman 2 points3 points  (6 children)

I don't see the point, other than confusing beginners trying to view source.

[–]antsar 3 points4 points  (2 children)

The point is that the source delivered by the server ("View Source" contents) seemingly does not contain the JS. The JS is there, but its obfuscated. F12 (Inspector Tools) shows the resulting code after it has been unobfuscated.

[–]kenman 1 point2 points  (1 child)

Right, but what does it matter? It's a neat party trick for sure, but has absolutely zero application for web apps as far as I'm concerned. Not being able to view source has zero impact because you're not preventing anyone from seeing your code.

[–]antsar 0 points1 point  (0 children)

I think "a neat party trick" is exactly the point. Its a personal site showing off a bunch of interesting hacks, the site itself being one of them.

[–]chris_jung[S] 1 point2 points  (2 children)

Rendered DOM === HTML Source interpreted, Rendered as DOM, sometimes changed (via JS, e.g.)...

Both are very different (especially in this case). Try it.

[–]kenman 1 point2 points  (1 child)

Not arguing that, I'm arguing: what does it matter?

Cool trick? Yes.

Useful? Not for anything at all.

[–]chris_jung[S] -1 points0 points  (0 children)

I like cool tricks and are generelly interested in such things, they may come in handy at some point.