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

Incorporate innerText #465

Closed
Ms2ger opened this issue Jan 4, 2016 · 6 comments
Closed

Incorporate innerText #465

Ms2ger opened this issue Jan 4, 2016 · 6 comments
Assignees
Labels
addition/proposal New features or enhancements compat Standard is not web compatible or proprietary feature needs standardizing

Comments

@Ms2ger
Copy link
Member

Ms2ger commented Jan 4, 2016

From https://rocallahan.github.io/innerText-spec/

@domenic
Copy link
Member

domenic commented Jul 26, 2016

So I guess one of the reasons I wasn't enthusiastic about progressing this was the lack of multi-vendor interest in the approach specced there (of re-using CSS primitives).

However, we should be pragmatic about this. innerText is definitely part of the web and definitely needs a spec. That one is certainly better than nothing, and is in fact pretty good. IMO we should just incorporate it.

In doing so we should probably add some minor guidance to authors on why this is a bad thing to use and that there are better alternatives. We should also give it a dedicated sentence in the acknowledgments (as is done for other things previously developed elsewhere, like custom elements). And we'll need to make sure the non-normative parts of the text are converted into notes.

We should probably define a somewhat-generic algorithm that the innerText getter delegates to, and then we can update the spec that defines Selection to have Selection.prototype.toString() delegate to that algorithm also.

@domenic domenic added the addition/proposal New features or enhancements label Jul 26, 2016
@annevk
Copy link
Member

annevk commented Jul 27, 2016

Are there web-platform-tests?

@Ms2ger
Copy link
Member Author

Ms2ger commented Jul 27, 2016

@zcorpan zcorpan added the compat Standard is not web compatible or proprietary feature needs standardizing label Aug 15, 2016
@zcorpan
Copy link
Member

zcorpan commented Aug 15, 2016

@rocallahan are you interested in upstreaming the innerText spec?

@Ms2ger
Copy link
Member Author

Ms2ger commented Aug 15, 2016

Note that roc is no longer paid to work on the web platform.

@rocallahan
Copy link

I'm interested in something else upstreaming it :-).

zcorpan added a commit that referenced this issue Aug 16, 2016
From https://rocallahan.github.io/innerText-spec/ with no normative
changes except adding [CEReactions] to the IDL.

Fixes #465.
@zcorpan zcorpan self-assigned this Aug 16, 2016
zcorpan added a commit that referenced this issue Aug 17, 2016
From https://rocallahan.github.io/innerText-spec/
with the following normative changes:

* Defined behavior for non-CSS UAs.
* The setter is better defined.
* Added [CEReactions, TreatNullAs=EmptyString]
  to the IDL.

Fixes #465.

Remaining issues: #1679
alice pushed a commit to alice/html that referenced this issue Jan 8, 2019
From https://rocallahan.github.io/innerText-spec/
with the following normative changes:

* Defined behavior for non-CSS UAs.
* The setter is better defined.
* Added [CEReactions, TreatNullAs=EmptyString]
  to the IDL.

Fixes whatwg#465.

Remaining issues: whatwg#1679
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
addition/proposal New features or enhancements compat Standard is not web compatible or proprietary feature needs standardizing
Development

No branches or pull requests

5 participants