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
Follow operation should prefer the focused way #8750
Comments
Hi and nice to meet you @mbrzakovic @1ec5 , i would like to try and work on this issue if possible. |
is it still possible to work on this? |
Thanks for your interest! There’s a fix available in #8978; perhaps you could help review it? |
Hello @mbrzakovic @1ec5 , I would like to help work on this issue if possible. Thank you! |
Can I still help on this issue if possible? Thank you! |
Hey!! I want to work on this issue. I'm new here so I'm really excited to start contributing. Please assign it to me. |
Right, GitHub has a feature that suggests issues labeled as
good first issue
|
The “follow” operation added in #8671 stops when encountering a node that’s shared among multiple features. iD already keeps track of the “focused” way for the purpose of reliably navigating back and forth among its vertices using the keyboard. It would be natural to extend this capability to the follow operation, so that the user doesn’t have to think as much about other connecting ways after choosing a way to follow. Invoking the follow operation would focus the way, and subsequent follow operations would choose that way from among the candidate ways.
iD/modules/modes/select.js
Line 150 in 7699034
iD/modules/modes/select.js
Lines 48 to 50 in 7699034
The text was updated successfully, but these errors were encountered: