-
Notifications
You must be signed in to change notification settings - Fork 90
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
feat: add to single line map arrowa to navigate between points #798
feat: add to single line map arrowa to navigate between points #798
Conversation
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.
Perfect! Thank you
className={`${checkIfValidStep(rightStep) ? '' : 'disabled'}`} | ||
onClick={() => navigateMarkers(rightStep)} | ||
/> | ||
<LeftOutlined |
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.
we can add a "title" attribute for hover ("prev" / "next")
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.
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.
the title attribute is visible to users, and should help them understand whether right will indicate the previous or the next item of the list.
In RTL website, it's common to see right arrows serving as "next" buttons, while on LTR website it's the opposite, that's why I feel having this title can be significant to the user experience
return ( | ||
<div className="map-footer-buttons"> | ||
<RightOutlined | ||
className={`${checkIfValidStep(rightStep) ? '' : 'disabled'}`} |
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.
just an idea - we can hide the button if it's not relevant for this data point
Description
#776
it's not solution with more zoom (i check with the docs and it look like it's the maximum)
screenshots