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

Improve scroll to text WPT coverage. #20105

Merged
merged 1 commit into from Nov 8, 2019

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Nov 6, 2019

Adds many tests to the scroll to text WPT suite:

  • Setting window.location.fragmentDirective has no effect
  • All combinations of optional parameters in text directive
  • Matching TextMatchChars and PercentEncodedChars (in particular the
    syntactical characters '&', ‘,’ and ‘-’) including non-ASCII
  • Multiple matches in the page
  • Cross-whitespace/node matching (i.e. context terms and match terms
    can be separated by whitespace and node boundaries)

Also added a readable description to each test case.

Note all tests pass in Chrome except for non-ASCII character matching.

Change-Id: I2a692049ba81bef5412e7b73909fbcdc710eb0da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1900648
Commit-Queue: Nick Burris <nburris@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#713057}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

Adds many tests to the scroll to text WPT suite:
- Setting window.location.fragmentDirective has no effect
- All combinations of optional parameters in text directive
- Matching TextMatchChars and PercentEncodedChars (in particular the
  syntactical characters '&', ‘,’ and ‘-’) including non-ASCII
- Multiple matches in the page
- Cross-whitespace/node matching (i.e. context terms and match terms
  can be separated by whitespace and node boundaries)

Also added a readable description to each test case.

Note all tests pass in Chrome except for non-ASCII character matching.

Change-Id: I2a692049ba81bef5412e7b73909fbcdc710eb0da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1900648
Commit-Queue: Nick Burris <nburris@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#713057}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants