2

Whilst not finalised, the latest piece of CSS documentation to be written about Specificity in CSS uses the letters "A", "B" and "c" to refer to its different levels. To conform with this, when writing the Calculating Selector Specificty example, I too used a lowercase c alongside a capital A and B.

Since Documentation came out of closed Beta a couple users have edited this example to make the c uppercase, which I've so far reverted twice (and then once more after missing an instance of C right at the top).

I can totally understand why someone would want to change this, but I wrote it like this in the first place for a good reason - as I'm sure did the updated documentation (most likely to avoid confusion between HTML's <a> and <b> elements). I wish I had some way of letting future editors know why it's been written like this so that they'd perhaps think twice before making the change.

I'm not going to bother changing it back again as it's such a small and insignificant thing, but I'm sure there will be a lot of Documentation cases where editors modify things unnecessarily - especially when trying to make things look prettier.

I don't know how something like this could be implemented. Possibly using Wikipedia-like citations after specific blocks of content?

closed as off-topic by pnuts, Stephen Rauch, Michael Gaskill, Stephen Kennedy, peterh Sep 9 '18 at 0:08

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "The problem described here can no longer be reproduced. Changes to the system or to the circumstances affecting the asker have rendered it obsolete. If you encounter a similar problem, please post a new question." – pnuts, Stephen Rauch, Michael Gaskill, Stephen Kennedy, peterh
If this question can be reworded to fit the rules in the help center, please edit the question.
{"cc_re__cc_re__cc_by_sa_3_0": ["-item\"><a href=\"https://twitter.com/stackoverflow\" class=\"-link js-gps-track\" data-gps-track=\"footer.click({ location: 2, link: 32 })\">Twitter</a></li>\r\n                    <li class=\"-item\"><a href=\"https://linkedin.com/company/stack-overflow\" class=\"-link js-gps-track\" data-gps-track=\"footer.click({ location: 2, link: 33 })\">LinkedIn</a></li>\r\n                </ul>\r\n\r\n                <p class=\"mt-auto mb24\">\r\nsite design / logo &#169; 2019 Stack Exchange Inc; user contributions licensed under <a href=\"https://creativecommons.org/licenses/by-sa/3.0/\" class=\"js-gps-track\" data-gps-track=\"footer.click({ location: 2, link: 34 })\" rel=\"license\">cc by-sa 3.0</a>\r\n                            with <a href=\"https://stackoverflow.blog/2009/06/25/attribution-required/\"  class=\"js-gps-track\" data-gps-track=\"footer.click({ location: 2, link:35 })\" rel=\"license\">attribution required</a>.\r\n                    <span id=\"svnrev\">rev&nbsp;2019.8.23.34694</span>\r\n                </p>\r\n            </div>\r\n        </div>\r\n\r\n            </footer>\r\n            <script>StackExchange.ready(function () { StackExchange.responsiveness.addSwitcher(); })</scri"], "copyright__copyright__copyright": ["eterh Sep 9 '18 at 0:08\n\nThis question appears to be off-topic. The users who voted to close gave this specific reason:\n\n  \u2022 \"The problem described here can no longer be reproduced. Changes to the system or to the circumstances affecting the asker have rendered it obsolete. If you encounter a similar problem, please post a new question.\" \u2013 pnuts, Stephen Rauch, Michael Gaskill, Stephen Kennedy, peterh\nIf this question can be reworded to fit the rules in the help center, please edit the question."]}