Group connection points design flaws
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8.2k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Preflight Checklist
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for a feature request that matches the one I want to file, without success.
Category
UX: Minor design flaw that confuses (new) users/easy fix
Describe the bug
- Newly created groups have 16 generic connection points that may overlap with parent's connection points
- They are not connectable but connection points can be edited (counter-intuitive/confusing!)
As a consequence, a user:
- sees (parent object) connection points on hover
- clicks and edits the group connection points
- finds the edit has no effect, suspects a bug
Solution:
- A new group should probably not be instantiated with generic connection points
- If an object is not connectable and user edits connection points, the program should give some feedback.
Feedback Options:
- Disable editor if connectable is false (maybe too strong)
- Add switch in editor that indicates whether the object is connectable (I think this is the best)
- Set connectable true on instantiation of the group (false is probably a rare use case anyway)
This guides the user to
- understand how to select group vs parent objects
- discover "connectable" property
- edit the intended connection points
To Reproduce
Steps to reproduce the behavior:
- Create two squares, move apart, with overlap
- Group them (Ctrl+G)
- Hover to see any connection points, left click
- Click 'Edit Connection Points...'
-> Editor shows the same connection points as the parent square but from group
draw.io version (In the Help->About menu of the draw.io editor):
- draw.io version 31.1.5
Desktop (please complete the following information):
- OS: Linux (desktop) and online version
- Browser chromium
I tested the problem in incognito/private mode with all browser extensions switched off, write "yes" below:
- no
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in the online or desktop editor using the listed two-square grouping steps, then inspect the group selection and “Edit Connection Points...” entry points. Compare the group’s displayed points with its connectable state and determine which feedback behavior the project accepts. Done means group connection-point editing no longer appears to work without effect or confuse users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- design, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100