Skip to content
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 cmd+down on search result focusing editor #68182

Merged
merged 1 commit into from
Feb 9, 2019

Conversation

roblourens
Copy link
Member

Fix #68018

}

export function getSelectionKeyboardEvent(typeArg: string, preserveFocus?: boolean): SelectionKeyboardEvent {
const e = new KeyboardEvent(typeArg);
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

KeyboardEvent does not like to be subclassed

@mjbvz
Copy link
Collaborator

mjbvz commented Feb 8, 2019

Change looks good to me and seems to work when I built it. @joaomoreno should review as well

@roblourens
Copy link
Member Author

@joaomoreno you can merge it if it's good

@joaomoreno joaomoreno added this to the January Recovery 2019 milestone Feb 8, 2019
Copy link
Member

@joaomoreno joaomoreno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With this change, we are hard-coding the list.select command to never preserve focus... which I'm not entirely sure we should do. Was this true in the latest stable? If so, merge away. Otherwise, I would be careful with it.


For the future, it seems to be list.select is bogus. We should introduce a list.open command which could handle a preserveFocus argument.

@roblourens
Copy link
Member Author

If I am reading this correctly, that was the case with list.select and the other resource navigator too.

@roblourens roblourens merged commit e984653 into release/1.31 Feb 9, 2019
@roblourens roblourens deleted the roblou/fix68018 branch February 11, 2019 23:04
@Spown
Copy link

Spown commented Feb 13, 2019

this is probably causing #68515

@egamma egamma removed this from the January 2019 Recovery milestone Feb 13, 2019
@github-actions github-actions bot locked and limited conversation to collaborators Mar 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants