-
Notifications
You must be signed in to change notification settings - Fork 6
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
Fix the css selector #15
Comments
I think we should just update the lexbor sources in nokolexbor. In lexbor:
|
@lexborisov The reason I didn't update lexbor is that the new versions were not as performant as the current one. I just did the benchmark again.
Raw data:Lexbor at b2c0a61
Lexbor at 9677d13
The newer version shows a small improvement in parsing but a big downgrade in selecting (at_css and css). Actually, the downgrade was introduced since this commit lexbor/lexbor@9677d13. I think CSS parsing is slowing down the whole selecting process. Is there something I can do to recover the performance? |
Hi @zyc9012 Okay, I'll take a look at it. It's weird that the parser slowed down, it didn't seem to change anything there. |
The
~
selector is not working as expected.I'm trying to extract only the blocks that appear before the
.more-news
element. This works in the browser but doesn't behave as expected in my code.Environment
Additional context
The text was updated successfully, but these errors were encountered: