Skip to content

Fix EuiStat invalid DOM nesting#2229

Merged
elizabetdev merged 8 commits intoelastic:masterfrom
elizabetdev:stat-invalid-dom
Aug 26, 2019
Merged

Fix EuiStat invalid DOM nesting#2229
elizabetdev merged 8 commits intoelastic:masterfrom
elizabetdev:stat-invalid-dom

Conversation

@elizabetdev
Copy link
Copy Markdown
Contributor

@elizabetdev elizabetdev commented Aug 15, 2019

Fixes #2228

There was an invalid DOM nesting due to a <p> tag nested within another <p> tag. The issue was fixed by replacing the <p> tag with a <span>.

Checklist

  • Checked in dark mode
  • Checked in mobile
  • Checked in IE11 and Firefox
  • Props have proper autodocs
  • Added documentation examples
  • Added or updated jest tests
  • Checked for breaking changes and labeled appropriately
  • Checked for accessibility including keyboard-only and screenreader modes
  • A changelog entry exists and is marked appropriately

@elizabetdev elizabetdev requested a review from snide August 15, 2019 13:24
@snide
Copy link
Copy Markdown
Contributor

snide commented Aug 15, 2019

@miukimiu Don't forget to add a changelog. Look at previous entries. A couple tips.

  • Use the past tense
  • This is a bug fix, so it would go under bug fixes for master

@elizabetdev
Copy link
Copy Markdown
Contributor Author

@snide I just the added a changelog under bug fixes for master. Can you review? 🙂

Copy link
Copy Markdown
Contributor

@snide snide left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small change should get you fixed.

snide added a commit that referenced this pull request Aug 16, 2019
CL entry for the stat stuff shouldn't be in master yet. It's still in a PR over here #2229

@miukimiu Please add this back into the change log file in your branch.
Copy link
Copy Markdown
Contributor

@myasonik myasonik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a small a11y issue that now VO users loose the bounding box of the content that's being read. That's not perfect but I think it's better than what we have today and I don't have any ideas that would keep the bounding box without significant hacks or significant work so I'm comfortable with the current solution for now.

Copy link
Copy Markdown
Contributor

@snide snide left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@elizabetdev elizabetdev merged commit 9d5716d into elastic:master Aug 26, 2019
@elizabetdev elizabetdev deleted the stat-invalid-dom branch August 26, 2019 16:52
thompsongl pushed a commit to thompsongl/eui that referenced this pull request Sep 10, 2019
CL entry for the stat stuff shouldn't be in master yet. It's still in a PR over here elastic#2229

@miukimiu Please add this back into the change log file in your branch.
thompsongl pushed a commit to thompsongl/eui that referenced this pull request Sep 10, 2019
* Fixes stat invalid DOM nesting

* Putting animation back

* Moving display block

* Improving sctructure and accessibility

* ScreenReaderOnly rendered as a single phrase

* Loading reverse

* Changelog and code refactor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

EuiStat has invalid DOM nesting when isLoading is set to true

3 participants