-
Notifications
You must be signed in to change notification settings - Fork 29.5k
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
Notebook: find doesn't search in output #94239
Comments
Putting it in backlog first considering its complexity. |
I should explain its "complexity" in details. It's not totally impossible to implement search in the webview but the catch is how many bugs or limitations it has. Firstly, to archive the best result, we want to let the browser to do the search other than us traverse the tree as we might not able to handle cases like
Also not every browser implements all const resultRanges = [];
if(window.find) {
while(window.find(query)) {
const range = window.getSelection().getRangeAt(0);
resultRanges.push(range);
}
} This algorithm might be good for a lot of cases but not sure how much it can cover (90%, or 50%? It depends on output renderers). The drawback of this approach is the bugs browsers currently have for
IMHO it's a good API to start with but we might need a champion/ambassador for it to convince the browsers that it's a good API to have for web apps. |
Another challenge we have is we are only rendering outputs when it become visible. It means you can't search for things which are not rendered once yet (cell input is good though), even if you know they exist. |
Is there any update on this issue (since it's still open)? 😄 🙏 |
We now support searching cell outputs. |
@rebornix thanks for the update! Do I need to do anything special to enable this? For now, nothing seems to have changed (Insiders version as well) 🤔 |
Testing #93742
label:electron $repo sort desc by reactions
The text was updated successfully, but these errors were encountered: