- From: Dave Cramer <dauwhe@gmail.com>
- Date: Thu, 20 Oct 2016 09:03:57 -0400
- To: Koji Ishii <kojiishi@gmail.com>
- Cc: fantasai <fantasai.lists@inkedblade.net>, Brad Kemper <brad.kemper@gmail.com>, "www-style@w3.org" <www-style@w3.org>
On Wed, Apr 8, 2015 at 7:58 AM, Koji Ishii <kojiishi@gmail.com> wrote: > On Apr 2, 2015, at 11:41, fantasai <fantasai.lists@inkedblade.net> wrote: >> >> I think we probably need to get the browsers to agree on this >> issue and put the required behavior in the spec, so authors know >> what to expect. >> >> Personally I don't think the copied text should be affected by >> the transform: if that's a key part of the text's presentation, >> then it should be done in the source. There's a lot of cases >> where it wouldn't make sense to copy out the style. E.g. putting >> the first word (or phrase) of an article is a stylistic choice >> that shouldn't come out in the plaintext copy. > > I disagree on both the desired behavior and standardizing this behavior. > > I personally prefer What You See Is What You Copy. How it’s written in the source file doesn’t matter much to me when I’m viewing a web site. Especially if we were to introduce regex based text-transform in future, it’s even more confusing. > > And I think plain-textizing belongs to browser UX. If you don’t like a behavior in your favorite browser, filing a bug to the browser makes more sense to me. Per the Working Group call yesterday, here are some browser bugs around this issue: Mozilla: https://bugzilla.mozilla.org/show_bug.cgi?id=35148 Webkit (old): https://bugs.webkit.org/show_bug.cgi?id=3429 Webkit (new): https://bugs.webkit.org/show_bug.cgi?id=43202 There doesn't seem to be consensus, but it's only been sixteen years. Dave
Received on Thursday, 20 October 2016 13:04:28 UTC