From 6a1cccfa0482fe9028078478a9a57f4189ea1352 Mon Sep 17 00:00:00 2001 From: Alfiya <33545574+alfiya-udc@users.noreply.github.com> Date: Tue, 21 May 2019 15:37:42 +0300 Subject: [PATCH 1/2] Some punctuation & sense ? --- 2-ui/3-event-details/4-mouse-drag-and-drop/article.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/2-ui/3-event-details/4-mouse-drag-and-drop/article.md b/2-ui/3-event-details/4-mouse-drag-and-drop/article.md index 2c781c59..a6d54682 100644 --- a/2-ui/3-event-details/4-mouse-drag-and-drop/article.md +++ b/2-ui/3-event-details/4-mouse-drag-and-drop/article.md @@ -4,9 +4,9 @@ Drag'n'Drop is a great interface solution. Taking something, dragging and droppi In the modern HTML standard there's a [section about Drag Events](https://html.spec.whatwg.org/multipage/interaction.html#dnd). -They are interesting, because they allow to solve simple tasks easily, and also allow to handle drag'n'drop of "external" files into the browser. So we can take a file in the OS file-manager and drop it into the browser window. Then JavaScript gains access to its contents. +They are interesting because they allow to solve simple tasks easily, and also allow to handle drag'n'drop of "external" files into the browser. So we can take a file in the OS file-manager and drop it into the browser window. Then JavaScript gains access to its contents. -But native Drag Events also have limitations. For instance, we can limit dragging by a certain area. Also we can't make it "horizontal" or "vertical" only. There are other drag'n'drop tasks that can't be implemented using that API. +But native Drag Events also have limitations. For instance, we can't limit dragging by a certain area. Also we can't make it "horizontal" or "vertical" only. There are other drag'n'drop tasks that can't be implemented using that API. So here we'll see how to implement Drag'n'Drop using mouse events. Not that hard either. From a361825446c49fc1cd61953adec08a3113d4fd3d Mon Sep 17 00:00:00 2001 From: Alfiya <33545574+alfiya-udc@users.noreply.github.com> Date: Wed, 22 May 2019 09:28:20 +0300 Subject: [PATCH 2/2] Grave accent --- 5-network/02-fetch-progress/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/5-network/02-fetch-progress/article.md b/5-network/02-fetch-progress/article.md index b1e4a591..9a2c26b0 100644 --- a/5-network/02-fetch-progress/article.md +++ b/5-network/02-fetch-progress/article.md @@ -3,7 +3,7 @@ `Fetch` allows to track download progress, but not upload progress. -Please note: there's currently no way for fetch to track upload progress. For that purpose, please use [XMLHttpRequest](info:xmlhttprequest). +Please note: there's currently no way for `fetch` to track upload progress. For that purpose, please use [XMLHttpRequest](info:xmlhttprequest). To track download progress, we can use `response.body` property. It's a "readable stream" -- a special object that provides body chunk-by-chunk, as it comes, so we can see how much is available at the moment.