Feature/EuiMark

[mridulgogia]

Summary

#2085
Added EuiMark component

Checklist

• Check against all themes for compatibility in both light and dark modes
• 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

[kibanamachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[myasonik]

jenkins test this

[kibanamachine]

Preview documentation changes for this PR: https://eui.elastic.co/pr_3060/

[thompsongl]

From previously open PRs:

We'll want to add the following for accessibility, also:
https://github.com/thompsongl/eui/blob/euimark/src/components/mark/_mark.scss#L19-L37

[snide]

From previously open PRs:

We'll want to add the following for accessibility, also:
https://github.com/thompsongl/eui/blob/euimark/src/components/mark/_mark.scss#L19-L37

I'd suggest doing something similar to this using EuiScreenReaderOnly before and after the mark, rather than using CSS before/after. That was we can make sure the text gets i18n treatment.

[cchaos]

Lets get this PR in for @mridulgogia and then we can do a follow up for a11y and style.

Jenkins, test this

[kibanamachine]

Preview documentation changes for this PR: https://eui.elastic.co/pr_3060/