-
Notifications
You must be signed in to change notification settings - Fork 30
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.
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
Fix four UI issues (#434) #435
Fix four UI issues (#434) #435
Conversation
I am review now |
allowedBackends={new Set(props.queue.allowed_backends)} | ||
onChange={props.onChangeBackend} | ||
selectedBackend={props.selectedBackend}/> | ||
<Row> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think the col-lg
on line 372 might also be an issue and need to be updated?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not an issue per se, but it's an instance of the direct Bootstrap class usage I've tried to move away from. Actually, this column turned out to be not needed, since it's not part of a larger grid structure (other Row
s or Col
s). Since this was the last instance of direct Bootstrap class usage in the module, I went ahead and removed it and used an Alert
component there. It does have one side effect of setting role="alert"
, which makes it pretty noisy for screenreaders, but we're using Alert
for other usages on the page. I could see setting role={undefined}
for the SMS and management alerts, but they are conditional as well. Going to stick with the out-of-the-box Alert
for now. 27c1109
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Working as expected
This PR aims to resolve #434. See issue for details on the regressions or problems this resolves.