-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Completion broken in read-only editors #325
Labels
closed-not-planned
Closed as we don't intend to take action on the reported issue
type-enhancement
A request for a change that isn't a bug
Milestone
Comments
Removed Type-Defect label. |
Set owner to @stevemessick. |
This comment was originally written by [email protected] Added Editor-Usability label. |
Added NotPlanned label. |
stevemessick
added
Type-Enhancement
closed-not-planned
Closed as we don't intend to take action on the reported issue
labels
Apr 20, 2013
kevmoo
added
type-enhancement
A request for a change that isn't a bug
and removed
type-enhancement
labels
Mar 1, 2016
nex3
pushed a commit
that referenced
this issue
Aug 31, 2016
support running the dev_compiler package directly
This was referenced Oct 29, 2020
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
closed-not-planned
Closed as we don't intend to take action on the reported issue
type-enhancement
A request for a change that isn't a bug
Before the editor on a core library class became read-only it was possible to invoke code completion to see what other methods and types were available at any given site. That's no longer possible. It's important for those who want to learn the APIs.
Read-only editors should not ignore keyboard input. They should disallow modification but still respond to keyboard input. (I'm not entirely sure what the problem is because F3 still works for Open Declaration.)
The text was updated successfully, but these errors were encountered: