In a way they're same, cause they fall under category of selecting node/element from the dom.
But they give different performance under different circumstances , you can check performance here : https://measurethat.net/Benchmarks/Show/1144/1/getelementbyid-vs-queryselector-vs-getelementsbyclassna
getElementbyId() is useful when you target particular id from the DOM, which returns single element
getElementsByClassName() or getElementByTagName() will return list of matched elements according to what is passed as parameter , there for i used [0] in getElementByClassName() , both methods returns list of elements
While querySelector() is useful to peek class/id/tag by prefixing their css notation (i.e) id root can be #root and class active can be .active, we can also pass tag names here but in all case querySelector() returns only first element and not list of elements , if you want list of elements to be selected querySelectorAll() can be useful
Regards.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The captures to show the index and app code for:
In a way they're same, cause they fall under category of selecting node/element from the dom.
getElementbyId()is useful when you target particular id from the DOM, which returns single elementgetElementsByClassName()orgetElementByTagName()will return list of matched elements according to what is passed as parameter , there for i used [0] ingetElementByClassName(), both methods returns list of elementsWhile
querySelector()is useful to peek class/id/tag by prefixing their css notation (i.e) id root can be #root and class active can be .active, we can also pass tag names here but in all casequerySelector()returns only first element and not list of elements , if you want list of elements to be selectedquerySelectorAll()can be usefulRegards.