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

Revert "fix: Incorrect parsing of functional pseudo class css selector (#169)" #182

Merged
merged 4 commits into from
Apr 19, 2024

Conversation

billyvg
Copy link
Member

@billyvg billyvg commented Apr 19, 2024

This reverts commit 810b39f.

Reverting this in favor of rrweb-io#1401 and rrweb-io#1440 which is better than whatever it is I wrote. I kept our tests just to ensure the fix is compatible with our previous patch.

billyvg and others added 4 commits April 19, 2024 13:56
* Fix known issues

* Run format

* Fix linting errors

* Add comment in code for source of match logic

* Add changeset
* better splitting of selectors - overlapping with rrweb-io#1401 
* Add test from example at PostHog/posthog#21427
* ignore brackets inside selector strings
* Add another test as noticed that it's possible to escape strings
* Ensure we are ignoring commas within strings

Co-authored-by: Eoghan Murray <eoghan@getthere.ie>
@billyvg billyvg marked this pull request as ready for review April 19, 2024 18:25
@billyvg billyvg requested a review from a team April 19, 2024 18:25
@billyvg billyvg merged commit de6cd2b into sentry-v2 Apr 19, 2024
14 checks passed
@billyvg billyvg deleted the revert-810b39f6fa62d17f2389467121ddd11ae6aa1033 branch April 19, 2024 19:25
billyvg added a commit that referenced this pull request Jun 5, 2024
…or (#169)" (#182)

This reverts commit de6cd2b, reversing
changes made to 9e07245.
billyvg added a commit that referenced this pull request Jun 5, 2024
billyvg added a commit that referenced this pull request Jun 7, 2024
This reverts #182 (i.e. we are
going back to #169) as we had
some performance regressions with the CSS changes.

I tested these against the replays that had crashed with the upstream
changes and they seem to work ok.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants