Minutes Telecon 2016-10-19
- Most of the call was dedicated to discussing how to and if we should define the effect of text-transform on copy/paste (CSS Text Issue #108)
- As a general principle there was a desire to have copy/paste match what users are seeing when they copy, however several people believed that the actual use cases in this case overrode the principle.
- There were four main use cases that the group uncovered:
- Turning a heading into all caps
- Turning a first line into all caps
- Turning acronyms into small case when they’re all caps in the source
- A ruby use case around ruby where in Japanese “しゃ” reads “sha”, and “しや” reads “shiya”. If that’s your ruby, there can be a text-transform to turn one into the other, because at small sizes it is hard to tell apart and smaller letters are hard to read. But out of context, you don’t want to change the pronunciation.
- Though mostly in the above use cases preserving the text-transform would be the worse user experience, there are times where you would expect preservation
- Consistency between inner text, paste to plain text, and range to string was another thing to be considered in the decision.
- In a straw poll the group was about evenly split between copied plain text ignoring text-transform or leaving it up to UA for UX decision.
- Group members will look through browser bugs to try and determine user expectations.
- There was also a desire to conduct a through user survey, though no one was tasked with creating one.
- Resolved: White space property is applied to plain text paste output.
- Resolved: Don’t define interaction between hanging punctuation and kerning and leave it up to UA to decide how to adjust.
- fantasai will write up her proposal to address hanging-punctuation scrollable overflow for review as there wasn’t time on the call.
Full Minutes
« Previous article
Next article »