- From: Sylvain Galineau <sylvaing@microsoft.com>
- Date: Tue, 26 Jun 2012 22:08:24 +0000
- To: Brad Kemper <brad.kemper@gmail.com>
- CC: Christoph Päper <christoph.paeper@crissov.de>, W3Cwww-style mailing list <www-style@w3.org>
[Brad Kemper:] > > > > > > [Christoph Päper:] > >> > >> > >> With 'text-transform' some UAs ignore the code/style distinction already: > >> When you copy text that was case-changed through CSS from a browser > >> into a plain-text environment, it will often be pasted with the > >> casing displayed in the browser instead of the one stored in the > >> source code. I strongly believe this is just as wrong as not copying > "display: none" parts to the clipboard. > > > > I'm not sure why that would be wrong, especially from the point of > > view of an end user. If someone copies/paste something from a web page > > into their email client and the case changes they are imo far more > > likely to be surprised and consider it a bug than to think 'oh thank > > God the browser preserved the state of the markup instead' > > Well the CSS is just supposed to be stylistic. A distinction that is meaningless to 99.9% of end-users. While people are now somewhat used to content looking different when they paste it from a browser into a word processor or a mail client they do not consider these formatting discrepancies as a feature. >If I use Word's "paste special" to paste without formatting, or if I paste >into something else that normally strips styling (such as another form field), >then I'd expect ALL styling to be stripped. Sure, the browser can provide a raw version of the content to the clipboard and the software at the receiving end can expose this format as a choice to the user. Whether that should be supported or the default imo far outside the scope of CSS, however.
Received on Tuesday, 26 June 2012 22:08:56 UTC