Skip to content
This repository has been archived by the owner on Mar 4, 2020. It is now read-only.

feat(Chat): Add expandable control messages prototype #1765

Merged
merged 12 commits into from
Aug 12, 2019

Conversation

sophieH29
Copy link
Contributor

Based on @mnajdova 's work #1687

Collapsed:
image

Expanded:
image

@codecov
Copy link

codecov bot commented Aug 6, 2019

Codecov Report

Merging #1765 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1765   +/-   ##
=======================================
  Coverage   69.76%   69.76%           
=======================================
  Files         867      867           
  Lines        7353     7353           
  Branches     2135     2158   +23     
=======================================
  Hits         5130     5130           
  Misses       2215     2215           
  Partials        8        8
Impacted Files Coverage Δ
...ccessibility/Behaviors/Chat/chatMessageBehavior.ts 100% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7a1daca...c1d44bf. Read the comment docs.

@@ -20,6 +20,7 @@ const chatMessageBehavior: Accessibility = () => ({
attributes: {
root: {
[IS_FOCUSABLE_ATTRIBUTE]: true,
tabIndex: -1,
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this change for the prototyping or a real fix?

Copy link
Contributor Author

@sophieH29 sophieH29 Aug 9, 2019

Choose a reason for hiding this comment

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

it's additional safety thing. Helps both for prototype and overall behavior. Chat Message should be always focusable, meaning - to have set tabIndex=-1. When component re-renders based on state change, FocusZone won't pick this change up unless you move arrow keys, so the chat message will be rendered without tabIndex - thus not focusable

@vercel vercel bot temporarily deployed to staging August 9, 2019 11:43 Inactive
Sofiya Huts added 2 commits August 9, 2019 15:54
…ble-control-messages' of https://github.com/stardust-ui/react into proto/expandable-control-messages

# Conflicts:
#	CHANGELOG.md
<>
{this.props.icon ? <Icon name="participant-add" /> : null}
<Ref innerRef={this.messageRef}>
<Chat.Message {...this.props.message} className="control-message" />
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's follow the convention for the other stardust component's classNames. It should be something like ui-chat__message_control

Copy link
Contributor

@mnajdova mnajdova left a comment

Choose a reason for hiding this comment

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

See one final comment, looks good otherwise :)

@sophieH29 sophieH29 merged commit 94feb58 into master Aug 12, 2019
@delete-merged-branch delete-merged-branch bot deleted the proto/expandable-control-messages branch August 12, 2019 09:43
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants