Follow
#DailyBloggingChallenge (13/25)
One of my favorite things to do is exploit the DOM (ethical concerns aside).
Lots learn early on if some pesky web component is blocking your view, just delete it in the developer’s tools.
This is usually the spark into what other configurations are possible.
As a #WebDeveloper by trade we are constantly in the developer’s tools trying to understand why certain elements are behaving the way they are - visually or in action. Though we have access to the code base, so it’s easier to understand.
The fun begins when you only have access to the website!
- For one time edits basic DOM manipulations will suffice.
- For simple tasks the console will suffice.
- If you started editing the CSS, you can save your changes and load them next time you visit.
- If you don’t care about #fingerprinting, you can use extensions like #GreaseMonkey or #Stylus.
In the realm of heavy duty modifications, there are a couple of options:
- Write your own #browser extension.
- Write your own library and run it through the console. This permits to offline development in your preferred coding language and you can bundle it either through #webpack or #wasm.
- Host your code on #npmjs, use a CDN bundler, and then preload it via an extension like GreaseMonkey.
- There is also the option to preload your script into the browser’s config, though with each update one has to do this anew, not questioning the potential #security flaws.
Through these possibilities one will learn a lot about vanilla #WebDevelopment and #VanillaJS.
