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

Change the CSS Selectors calculation logic #1765

Open
AlexeyGirin opened this issue Aug 8, 2024 · 0 comments
Open

Change the CSS Selectors calculation logic #1765

AlexeyGirin opened this issue Aug 8, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@AlexeyGirin
Copy link
Contributor

Problem statement/business needs:

Currently, backend get one solid task to calculate all CSS Selectors at once, split it to N smaller tasks (where N - number of workers usually equal number of CPU cores minus two) and returns back to the frontend only after smaller task is done completely
From the user perspective that looks like a huge time happens nothing and than - all (almost) calculated CSS selectors appears at once. Bad user experience.

What we have to archive - we have to return to the frontend every CSS selector right after it is calculated. One by one.
In the same manner as we do it for xPath

Definitions of Done:

  • DoD1
  • DoD2

Dependencies or related tasks:

Comments:

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
Status: QA
Development

No branches or pull requests

2 participants