Then you do the ol' "View Source" and now that technique is in your toolkit. In fact you'd prob head right over to your geocities site and try it out right away.
Then you do the ol' "View Source" and now that technique is in your toolkit. In fact you'd prob head right over to your geocities site and try it out right away.
I really think the web community lost something with the transition to compiled uglified js and css…. Sure google will show you to some code if you manage to put what you are looking for into words but that isn’t always easy. Pitty that there is no standardised solution to publish the source along with the Minimized script nowadays.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/So...
Can’t tell if you’re sarcastic or not, assuming not all comment readers will be aware either way.
For JS it's a different story of course but it was never that easy to begin with since the code that affects an element can be anywhere.
<html> <script src="obfuscated.javscript-pack.chunk-12384123.chunkittychunk-packweb.der.huhwhat?{this?:this-v3.2123-notcompatiblewithv3.2122}.js"> <div id="modern-web-app-goez-here"></div> </html>
Good luck with that!
Sure there's source map files, but most of the time you'll fine those aren't distributed together with the minified bundles.
That you'll be able to actually read the code is another completely different story.
getEventListeners($0)
getEventListeners is a Chrome console/devtools only function and $0 is a console placeholder variable for the currently selected element.It's definitely not the nicest way to find things and you often end up running into the minified/uglified madness when delving deeper, but sometimes it helps do the trick.