Skip to content

Change the CSS Selectors calculation logic #1765

Open
@AlexeyGirin

Description

@AlexeyGirin

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:

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

Status

QA

Relationships

None yet

Development

No branches or pull requests

Issue actions