- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Fri, 30 Oct 2020 15:04:01 +0000
- To: public-css-archive@w3.org
Not sure how `innerText` demonstrates the difference between "text" and "string", since there's no `innerString`. Also note that `innerText` was never the output of a rigorous consensus-driven process, but a Microsoft extension that was later standardized to pave the cowpaths. Do note that in spreadsheets, it's a [`text()` function that converts to a string](https://support.google.com/docs/answer/3094139?hl=en). I don't think adding string concatenation on a case by case basis is a good idea at all. It makes each individual property more complicated, it makes the language less consistent (which properties support concatenation and which don't?) and adds overhead to learning each property, since each property does concatenation differently (lack of internal consistency). Also it would mean that authors need to wait for the full standards lifecycle (proposal + draft + implementation + test) for **every single concatenation use case** that we did not foresee early on. Also note that `font-family` doesn't support concatenation. If you have a variable with `"Times"` and another one with `" New Roman"`, you cannot turn them into a single font family by just placing them next to each other. The only property that currently supports actual concatenation is `content`. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/542#issuecomment-719606386 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 30 October 2020 15:04:03 UTC