jeena/en.javascript.info
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Merge pull request #2063 from maksumi/patch-3

Browse source 
Update article.md
This commit is contained in:
Ilya Kantor 2020-08-14 08:42:13 +03:00 • committed by GitHub
commit 665b8ebbba
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
2-ui/1-document/11-coordinates/article.md
View file

@ -88,8 +88,8 @@ As you can see, `left/top` do not equal `x/y` in such case.
In practice though, `elem.getBoundingClientRect()` always returns positive width/height, here we mention negative `width/height` only for you to understand why these seemingly duplicate properties are not actually duplicates. In practice though, `elem.getBoundingClientRect()` always returns positive width/height, here we mention negative `width/height` only for you to understand why these seemingly duplicate properties are not actually duplicates.
``` ```
```warn header="Internet Explorer and Edge: no support for `x/y`" ```warn header="Internet Explorer: no support for `x/y`"
Internet Explorer and Edge don't support `x/y` properties for historical reasons. Internet Explorer doesn't support `x/y` properties for historical reasons.
So we can either make a polyfill (add getters in `DomRect.prototype`) or just use `top/left`, as they are always the same as `x/y` for positive `width/height`, in particular in the result of `elem.getBoundingClientRect()`. So we can either make a polyfill (add getters in `DomRect.prototype`) or just use `top/left`, as they are always the same as `x/y` for positive `width/height`, in particular in the result of `elem.getBoundingClientRect()`.
``` ```