Opened 6 weeks ago
Last modified 3 weeks ago
#41886 assigned enhancement
Code Editor: Auto scroll or click button to go to error.
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | Future Release | Priority: | high |
| Severity: | normal | Version: | |
| Component: | General | Keywords: | ux-feedback needs-patch |
| Focuses: | Cc: |
Description (last modified by westonruter)
It would be good to have an auto scroll to go to error that the code editor notices. (Or a button the user can click.) After fixing one error the user can click the button again to go to the next.
The Update File button should not be disabled.
Originally https://github.com/WordPress/better-code-editing/issues/95
See conversation at https://wordpress.slack.com/archives/C0381N237/p1505425698000437
Change History (14)
This ticket was mentioned in Slack in #core-customize by paaljoachim. View the logs.
6 weeks ago
#2
@westonruter
6 weeks ago
- Milestone changed from Awaiting Review to 4.9
#3
@westonruter
6 weeks ago
- Keywords ux-feedback added
- Owner set to melchoyce
- Status changed from new to assigned
#4
@westonruter
6 weeks ago
- Description modified (diff)
#5
@westonruter
6 weeks ago
- Description modified (diff)
#6
@westonruter
5 weeks ago
- Summary changed from Better Code Editing: Auto scroll or click button to go to error. to Code Editor: Auto scroll or click button to go to error.
#7
@westonruter
5 weeks ago
- Priority changed from normal to high
This ticket was mentioned in Slack in #design by karmatosed. View the logs.
4 weeks ago
This ticket was mentioned in Slack in #core by jeffpaul. View the logs.
3 weeks ago
This ticket was mentioned in Slack in #design by melchoyce. View the logs.
3 weeks ago
#12
@melchoyce
3 weeks ago
- Milestone changed from 4.9 to Future Release
I've been look at this issue, and at this point my two options feel like:
- Add something that looks kind of hacky and crappy that lets you scroll between errors
- Or, create a whole new "find" interface, like the one in browsers/major editors like Google Docs
I think 2 is viable, but not in the time we have. I'd want to spend some time working on it and testing it, so I'd need probably 1-2 weeks. Since we're coming up on the Beta 1 deadline, I think we should punt this and explore making improvements in a future release.
This ticket was mentioned in Slack in #core-customize by melchoyce. View the logs.
3 weeks ago
#14
@westonruter
3 weeks ago
In 41721:
Bumping priority to high for visibility and alignment with 4.9 goals, and given proximity to beta 1 deadline.