- From: Sarah Higley via GitHub <noreply@w3.org>
- Date: Tue, 03 Jun 2025 23:15:24 +0000
- To: public-css-archive@w3.org
smhigley has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-overflow-5]: making specific scroll markers disabled == This isn't currently happening for understandable reasons, but I wanted to open an issue to get browser implenetors' feedback on the feasibility of auto-translating strings given the current format of: ```css content: 'string-not-to-be-translated' / 'string that should be translated'; ``` There's a bit of history of screen-reader-only content getting left out of localization efforts both in browsers and by authors (e.g. `aria-label` taking quite a while to be included in translation), and this seems like it has a high potential to follow that trend so I wanted to make sure this is raised early. Essentially, for browser folks, I'm curious if: - This format with `content` + `/` can feasibly be included in strings to be translated - Would this interfere with efforts to include CSS `content` in general in translations - Could this be implemented before CSS overflow becomes a stable/released feature Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12268 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 3 June 2025 23:15:25 UTC