Without using document.getElementById
Historic window object still retains features pertaining to the start of the Browsers era

Search for a command to run...
Historic window object still retains features pertaining to the start of the Browsers era

No comments yet. Be the first to comment.
Clean your email list even before sending it to a mass emailing solution like AutoSend to avoid a high bounce rate

Try using an alternative to openclaw, which they claim is cheaper to use

Using types (and interfaces) to define a blueprint of a variable

Using GraphQL as an alternative to REST API for Hashnode

making makemigrations work in Django when migrations is not pushed to git

A few weeks ago I was surprised at at the fact that something that seemed impossible was / is still possible.
I didn't realize that this was even possible in my 20+ years of web development. I even had a debate with my colleague about not using it that way but we weren't in sync.
Apparently - if you set in your HTML <input type="text" id="first_name" /> , you don't need to do document.getElementById('first_name').value - instead, you can directly call first_name.value !!!
https://codepen.io/anjanesh/pen/GRLJZrj
Apparently, this is still valid and is also in the HTML spec.
the value of the id content attribute for all HTML elements that have a non-empty id content attribute and are in a document tree with window's associated Document as their root.