ayo/blog
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

update js dom api post

Browse source
This commit is contained in:
Ayo 2019-10-14 06:39:03 +08:00
parent 54d9818bc0
commit e828a70cbe
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
_posts/2019-10-14-forcing-javascript-dom-types.md
View file

@ -31,10 +31,12 @@ before you assign it...
x = document.getElementById('table-id') // -> always returns HTMLELement x = document.getElementById('table-id') // -> always returns HTMLELement
``` ```
If you go straight to doing `var x = document.getElementById('table-id')` the variable will have the generic type `HTMLElement`. If you go straight to doing `var x = document.getElementById('table-id')`, the variable will have the generic type `HTMLElement`... and you don't want that.
Important hint: the string parameter for `document.createElement()` (which is `'table'` in our example above) will determine the type/interface that the variable `x` will use. Important hint: the string parameter for `document.createElement()` (which is `'table'` in our example above) will determine the type/interface that the variable `x` will use.
The `'table'` parameter is the reason why we get an `HTMLTableElement` from `document.createElement()`.
## Uh, okay. But, uhm, why... woud I want to do that? ## Uh, okay. But, uhm, why... woud I want to do that?
Well, this way, the variable `x` will have the type `HTMLTableElement` all the way in your code. Well, this way, the variable `x` will have the type `HTMLTableElement` all the way in your code.