From bc92283021a5b5d0c23ebfa5cdee6bcf422e330b Mon Sep 17 00:00:00 2001 From: Maksumi Murakami Date: Thu, 13 Aug 2020 17:39:47 -0500 Subject: [PATCH 1/2] Update article.md Changes proposes for the [issue 2049](https://github.com/javascript-tutorial/en.javascript.info/issues/2049) --- 2-ui/1-document/11-coordinates/article.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/2-ui/1-document/11-coordinates/article.md b/2-ui/1-document/11-coordinates/article.md index fb55edf57a..489be2de45 100644 --- a/2-ui/1-document/11-coordinates/article.md +++ b/2-ui/1-document/11-coordinates/article.md @@ -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. ``` -```warn header="Internet Explorer and Edge: no support for `x/y`" -Internet Explorer and Edge don't support `x/y` properties for historical reasons. +```warn header="Internet Explorer: no support for `x/y`" +Internet Explorer don'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()`. ``` From 6615df4d5878fd404e6543b0056a078e8e6facfe Mon Sep 17 00:00:00 2001 From: Maksumi Murakami Date: Thu, 13 Aug 2020 18:22:27 -0500 Subject: [PATCH 2/2] Update article.md --- 2-ui/1-document/11-coordinates/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2-ui/1-document/11-coordinates/article.md b/2-ui/1-document/11-coordinates/article.md index 489be2de45..4775ff0eb5 100644 --- a/2-ui/1-document/11-coordinates/article.md +++ b/2-ui/1-document/11-coordinates/article.md @@ -89,7 +89,7 @@ In practice though, `elem.getBoundingClientRect()` always returns positive width ``` ```warn header="Internet Explorer: no support for `x/y`" -Internet Explorer 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()`. ``` pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy