Skip to content

Markdown fixes on "DOM Attributes in React 16" post #10816

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 25, 2017
Merged

Markdown fixes on "DOM Attributes in React 16" post #10816

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/_posts/2017-09-08-dom-attributes-in-react-16.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ In the past, React used to ignore unknown DOM attributes. If you wrote JSX with

would render an empty div to the DOM with React 15:

````js
```js
// React 15 output:
<div />
```
Expand Down Expand Up @@ -105,7 +105,7 @@ We've made a few other changes to make the behavior more predictable and help en
Below is a detailed list of them.

* **Unknown attributes with string, number, and object values:**

```js
<div mycustomattribute="value" />
<div mycustomattribute={42} />
Expand All @@ -118,7 +118,7 @@ Below is a detailed list of them.
*Note: attributes starting with `on` are not passed through as an exception because this could become a potential security hole.*

* **Known attributes with a different canonical React name:**

```js
<div tabindex="-1" />
<div class="hi" />
Expand Down