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

correct typo

Browse source
This commit is contained in:
Ayo 2019-10-14 06:34:30 +08:00
parent 3768c99afd
commit 54d9818bc0
1 changed files with 2 additions and 2 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,9 +31,9 @@ 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 `document.getElementById` 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`.
Important hint: the string parameter for `createElement` (`'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.
## Uh, okay. But, uhm, why... woud I want to do that? ## Uh, okay. But, uhm, why... woud I want to do that?