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

editor should not be dimmed when navigating search results #190102

Open
meganrogge opened this issue Aug 9, 2023 · 8 comments
Open

editor should not be dimmed when navigating search results #190102

meganrogge opened this issue Aug 9, 2023 · 8 comments
Assignees
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues feature-request Request for new features or functionality
Milestone

Comments

@meganrogge
Copy link
Contributor

editor.mov
@Tyriar
Copy link
Member

Tyriar commented Aug 9, 2023

@andreamah is there any class or something other CSS class we could use to disable this opacity rule for the editor when a search is active?

rules.add(`.monaco-workbench .editor-instance:not(:focus-within) .monaco-editor { ${filterRule} }`);

@Tyriar Tyriar added the under-discussion Issue is under discussion for relevance, priority, approach label Aug 10, 2023
@andreamah
Copy link
Contributor

editor.mov

this is loading for me as a 1-second video. could you re-attach the video? I'm not sure where that opacity rule is referenced in search.

@Tyriar
Copy link
Member

Tyriar commented Aug 10, 2023

@andreamah it's not referenced in search, it's a small workbench contrib that currently depends on terminal and editor. We also want to include search in the rule to ensure the editor with the active match also shows up, even when it's not focused.

@andreamah
Copy link
Contributor

What are the repro steps to seeing the dimmed editor when viewing search results? I don't think I see it.

@meganrogge
Copy link
Contributor Author

set accessibility.unfocusedViewOpacity and open the search panel, search for something and click through the results

@andreamah
Copy link
Contributor

Ah, I see it now. Can we check for context keys? If hasSearchResult & searchViewletFocus, then don't dim the editor?

@Tyriar
Copy link
Member

Tyriar commented Aug 11, 2023

We could use IContextKeyChangeEvent.onDidChangeContext but that would involve setting up a listener and replacing the CSS. That's an option, but it would be preferable if there's something like .has-search-results. If that doesn't exist that's fine, we can go the event route.

@andreamah
Copy link
Contributor

Sorry for the late reply on this. I don't think there's anything like .has-search-results since search uses the context key to make changes to the view. We could probably have to do a IContextKeyChangeEvent.onDidChangeContext for hasSearchResult

@Tyriar Tyriar added this to the September 2023 milestone Aug 31, 2023
@Tyriar Tyriar added feature-request Request for new features or functionality accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues and removed under-discussion Issue is under discussion for relevance, priority, approach labels Aug 31, 2023
@Tyriar Tyriar modified the milestones: September 2023, Backlog Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

3 participants