-
Notifications
You must be signed in to change notification settings - Fork 351
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: Open unlimited polygon does not restrict crossing sides. #1896
Conversation
GeraldRequired Reviewers
Don't want to be involved in this pull request? Comment |
npm Snapshot: PublishedGood news!! We've packaged up the latest commit from this PR (ceb9775) and published it to npm. You Example: yarn add @khanacademy/perseus@PR1896 If you are working in Khan Academy's webapp, you can run: ./dev/tools/bump_perseus_version.sh -t PR1896 |
Size Change: +175 B (+0.01%) Total Size: 1.29 MB
ℹ️ View Unchanged
|
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.
Neat! A couple of non-blocking suggestions, but overall looks good to me.
packages/perseus/src/widgets/interactive-graphs/reducer/interactive-graph-reducer.ts
Outdated
Show resolved
Hide resolved
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.
What happens when closing the polygon is what causes the sides to cross? Can you then untangle the points using the keyboard, or are they stuck?
I think we might need some logic like "if the polygon's sides currently cross, don't reject a move that results in the sides still crossing."
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 changes to this file seem unrelated to the rest of the PR. Are they supposed to be included?
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.
Discussed with Cat in Slack. It sounds like Caitlyn is aware of the "lines crossing" behavior and is okay with it for now. LGTM!
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @khanacademy/[email protected] ### Patch Changes - [#1896](#1896) [`56fd44806`](56fd448) Thanks [@catandthemachines](https://github.com/catandthemachines)! - Fixing intersecting polygon sides issues for unlimited sided polygon. - [#1894](#1894) [`01edfb8be`](01edfb8) Thanks [@nishasy](https://github.com/nishasy)! - [SR] Add comment about making translation tickets - [#1875](#1875) [`28cae9d2a`](28cae9d) Thanks [@nishasy](https://github.com/nishasy)! - [Locked Labels] Count lone unescaped \\$ as regular dollar signs in TeX ## @khanacademy/[email protected] ### Patch Changes - [#1874](#1874) [`42d25c2d2`](42d25c2) Thanks [@nishasy](https://github.com/nishasy)! - [Locked Figure Aria] Fix \\$ edge cases for spoken math aria labels - [#1912](#1912) [`44e78a95d`](44e78a9) Thanks [@nishasy](https://github.com/nishasy)! - [Interactive Graph Editor] Stop cursor jumps in number input fields - [#1875](#1875) [`28cae9d2a`](28cae9d) Thanks [@nishasy](https://github.com/nishasy)! - [Locked Labels] Count lone unescaped \\$ as regular dollar signs in TeX - Updated dependencies \[[`56fd44806`](56fd448), [`01edfb8be`](01edfb8), [`28cae9d2a`](28cae9d)]: - @khanacademy/[email protected]
## Summary: For keyboard users if they're drawing a polygon and it places a point at 0,0. There are cases where it could cross the sides of the polygon they are actively creating and cause the polygon to break. Mouse uses can get around this a bit. But it's not idea. This fix checks whether the polygon type allows intersecting sides and disables the rejection logic. This PR also includes improvements to: - Screen readers announcing instructions to enable graph (was not reading out before). - Disabled buttons are not tabbable now. Issue: LEMS-2618 ## Test plan: Go to /?path=/story/perseus-widgets-interactive-graph--unlimited-polygon-with-mafs in Storybook. Use your keyboard to add points. Move a few points in a way that a new point would cause the sides to intersect. Add a new point and make sure you can still move points on the polygon. Author: catandthemachines Reviewers: catandthemachines, nishasy, benchristel, anakaren-rojas Required Reviewers: Approved By: nishasy, benchristel Checks: ✅ Lint, Typecheck, Format, and Test (ubuntu-latest, 20.x), ✅ Publish npm snapshot (ubuntu-latest, 20.x), ✅ Cypress (ubuntu-latest, 20.x), ✅ Check builds for changes in size (ubuntu-latest, 20.x), ✅ Check for .changeset entries for all changed files (ubuntu-latest, 20.x), ✅ Publish Storybook to Chromatic (ubuntu-latest, 20.x), ✅ gerald Pull Request URL: #1896
Summary:
For keyboard users if they're drawing a polygon and it places a point at 0,0. There are cases where it could cross the sides of the polygon they are actively creating and cause the polygon to break. Mouse uses can get around this a bit. But it's not idea. This fix checks whether the polygon type allows intersecting sides and disables the rejection logic.
This PR also includes improvements to:
Issue: LEMS-2618
Test plan:
Go to /?path=/story/perseus-widgets-interactive-graph--unlimited-polygon-with-mafs in Storybook.
Use your keyboard to add points.
Move a few points in a way that a new point would cause the sides to intersect.
Add a new point and make sure you can still move points on the polygon.