- From: Alex Rosario via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Mar 2020 04:13:51 +0000
- To: public-css-archive@w3.org
1. I acknowledge the snark was wrong and I apologize. 2. The code on SO did not have the original typo of the first post of this issue, which was simply the result of typing the given escaped example by hand and a typo was never the actual problem, hence my original disappointment at the delivery of the reply focusing more on it than at pointing out that JavaScript would need double-escaping. I acknowledge that the SO code did not show the actual JavaScript I was attempting, but I did say that I had attempted to `CSS.escape` the query to run with the selector. The example given by Oriol did work, yes, that was never in dispute, and refactoring my code to account for that allowed it to work. Given that the use case of a backslash in an attribute is indeed not common, the documentation (at least on MDN at the time) was lacking in that respect and would benefit from an update saying that double-escaping (or `String.raw` tagging an already escaped template literal) the query is potentially necessary if in JavaScript. While I regret how I presented my text, I am glad I asked the question here and I do thank y'all for providing not just the answer to it specifically but the CSSWG in general for promoting the continuous useful progression of CSS. -- GitHub Notification of comment by apollolux Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4820#issuecomment-594316954 using your GitHub account
Received on Wednesday, 4 March 2020 04:13:53 UTC