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

XPath selector #21

Open
fcollonval opened this issue May 10, 2021 · 2 comments
Open

XPath selector #21

fcollonval opened this issue May 10, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@fcollonval
Copy link
Member

  • xpath. The css selectors fall down on finding some lab things. I'd love
    if selectors starting with / were interpreted as xpath selectors, seems
    like a light transform.

These last three kinda quack like "middleware," which could be registered
by plugins and opted into in a tour definition in the settings/command
API... As these would not be part of the official types, they'd need a new
place in the schema, e.g. "extras" or "transformers," e.g. {"markdown":
true, "xpath": true, "commands": true} at the simplest, though they might
need configuration...

Originally posted by @bollwyvl in #17 (comment)

@fcollonval fcollonval added the enhancement New feature or request label May 10, 2021
@fcollonval
Copy link
Member Author

@bollwyvl
Copy link
Contributor

Thanks for adding this. Also, a quick thing most browsers implement (but is not a safe API to rely on):

$x(`//some/long/xpath[with=quotes()`)

Anyhow... this might be a non-starter, as the target cannot be a callback... and there's little guarantee that e.g. the Run button element would exist before opening a notebook. Might have to cool this one and go upstream on this one...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants