w3c / w3c/webdriver

Allow Get Element Text algorithm to be set via a capability

Open
#703 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
718
Forks
228
PR merge metrics
No merged PRs in 30d

Description

At the Lisbon F2F we agreed to use the atom from the Selenium project for Get Element Text as this is what users expect and because there wasn't a stable alternative (the inner text algorithm not being equivalent)

We also agreed it would be desirable to be able to use innerText once it was available in all browsers and stable. This feature should be exposed to the user via a capability. I'd suggest text rendering with the possible values of atom and inner text (with the default being atom to preserve compatibility) would be a reasonable key name and values.

We need to ensure that element retrieval algorithms uses the same algorithm as Get Element Text (which I think they do) when this change happens.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the WebDriver specification sections for the Get Element Text algorithm and element retrieval algorithms referenced by the issue. Define how a text-rendering capability selects the atom or innerText algorithm, preserve atom as the default, and ensure element retrieval uses the same selection; done means the capability and algorithm behavior are specified consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.