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

Fragmention must define what “plain text content” means #6

Open
tantek opened this issue Jan 22, 2020 · 0 comments
Open

Fragmention must define what “plain text content” means #6

tantek opened this issue Jan 22, 2020 · 0 comments

Comments

@tantek
Copy link
Member

@tantek tantek commented Jan 22, 2020

The Fragmention processing model says to “Search through the plain text content” and hyperlinks the phrase “plain text content” to the HTML definition of a text node. That link is insufficient for precise (interoperable) implementation. Examples of questions that need to be answered explicitly by normative text in the spec:

Does it just mean to concatenate all the text nodes, including CDATA?

Does that include the text of inline script elements?

Does it instead include the text of noscript elements?

Does that include the text of inline style elements?

As already proposed in issue #4, does that include alt text from images?

The specification should at least answer these questions, preferably with examples demonstrating why the specific answers were chosen, and add tests for them accordingly.

(Originally published at: https://tantek.com/2020/022/b2/fragmention-define-plain-text-content)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.