- From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Nov 2023 12:13:55 +0000
- To: public-css-archive@w3.org
@annevk, I see from the minutes action items: > <TabAtkins> ACTION drott to investigate for Chrome > <TabAtkins> ACTION emilio to investigate for Firefox But I have trouble extracting exactly what were supposed to investigate. I dug out the removed heuristic: https://chromium.googlesource.com/chromium/src/+/2b4002d072669ff145b0afc1a47272503e3d7879%5E%21/#:~:text=%2DFontTranscoder%3A%3AConverterType-,FontTranscoder%3A%3AconverterType,-(const%20FontDescription%26%20fontDescription And as much as I understand from this 10 year old change: We did seem to modify an internal buffer, different from what we do for `text-transform`, but did some extra logic for clipboard handling so that we would not copy out modified strings, but original strings. The logic we used was: do this for a list of specified fonts, and if no primary font is specified at all. @annevk - are you curious about anything else? Looking at the code, I am not very comfortable adding something like this back in - especially the part about keeping a modified representation of the source text internally and having to special case clipboard operations. -- GitHub Notification of comment by drott Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6848#issuecomment-1794689105 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 6 November 2023 12:13:57 UTC