W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2019

Re: [csswg-drafts] [css-text] text-transform's design, intent and reality resolution (#3775)

From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
Date: Thu, 04 Apr 2019 18:11:06 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-480005535-1554401465-sysbot+gh@w3.org>
@fantasai I think it's worth acknowledging `innerText` here because it is an existing web API that relies on `text-transform` by reference, and any decisions we make here have downstream implications.

Now, maybe the final conclusion is that `innerText` is a weird thing defined by legacy compat instead of logic, and we shouldn't worry about optimizing for it — if it has to be generated on-demand by its own unique pathway, so be it. But that should be a conscious decision, not a shrugged-off “not my spec, not my problem.”

> must not affect the content of a plain text copy & paste operation

The most recent discussion of `text-transform` and copy & paste is in #627. The following resolution was made [one year ago](https://github.com/w3c/csswg-drafts/issues/627#issuecomment-380425497):

> RESOLVED: normative state that text-transform does not apply to plain text paste.

I couldn't find a relevant Chromium bug. [WebKit bug is here](https://bugs.webkit.org/show_bug.cgi?id=43202), with the last comment being an FYI about the CSS working group resolution.

-- 
GitHub Notification of comment by AmeliaBR
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3775#issuecomment-480005535 using your GitHub account
Received on Thursday, 4 April 2019 18:11:07 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:31:06 UTC