Синхронізація з оригінальною англійською версією javascript.info #523
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
to make `alerts` work
Update article.md
Noticed that the word implementing was spelt incorrectly within the section for pointercancel events, thus I decided to correct it for reading comprehension reasons.
Fixed typo
According to MDN, the precedence of unary plus, unary negation, exponentiation, multiplication, division, addition, and subtraction is 1 lower than it is in the document
Line 265 and 266: Use 'fruits' instead of the 'arr' variable.
This is almost the minimal number of changes that I would make. I would still recommend changing "play" in the first line to "work".
Looks like the right line for a comment is the line 306 instead of 308.
Depends on https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Operator_Precedence#Table, precedence of `??` and `||` should be 3 instead of 4
Edit precedence of `??` and `||`
Fix typo in pointercancel section
feat: improve type conversion for string with whitespace
Update the operator precedence table
small format change
Update article.md
Co-authored-by: Bogdan Bacoșcă <bogdanbacosca@protonmail.com>
Since the button is causing mobile screen users to have a horizontal scroll, I've fixed it giving it a max-height. This removes the horizontal scroll that the button was causing on the entire page for mobile readers.
correct statement grammar by adding missing word 'to'
fix: add missing word 'to' - Pointer events
Update button to fix horizontal scroll on mobile
Fix "JavaScript specials" links
Fix the article.md Resolves #3307
grammar & legibility (to check)
Added a missing word
#3345 Fixed Grammar
|
|
Collaborator
Author
|
@all-contributors add @georgyna for translation |
Contributor
|
@stas-dolgachov @georgyna already contributed before to translation |
ltlaitoff
reviewed
Sep 21, 2023
| Це дуже зручно, оскільки `finally` не призначений для обробки результату промісу. Так що він буде пропускати його через себе далі. | ||
| 3. Обробник `finally` також не повинен нічого повертати. Якщо все ж таки він щось повертає, це значення ігнорується. | ||
| Єдиним винятком із цього правила є випадки, коли обробник `finally` видає помилку. Бл потім ця помилка переходить до наступного обробника замість будь-якого попереднього результату проміса. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
56 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.