manosim / manosim/css-edit-groups
Inconsistent group position after jumping
Open
Nobody has claimed this yet.
- Dominant language
- CoffeeScript
- Stars
- 6
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Right now, when I jump to a group I get pretty different behaviour for the group's position within the editor.
There's three cases for me:
- The group jumps to the top of the editor. IMO this should be the desired behaviour.
- The group jumps to the bottom of the editor. This seems to be the default behaviour but it feels pretty buggy and annoying since I have to scroll all the way up to be able to work within the group.
- The group sits somewhere in the middle. This seems to happen when the target @group statement is already visible before jumping.
Is there any way to make case 1 the default behaviour?
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 jumping to a CSS, LESS, or SASS group in the Atom package and compare cases where the target statement is at the top, bottom, or already visible. Trace the group-jump entry point and make the behavior consistently place the group at the top of the editor; verify each reported case manually.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- coffeescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100