Update Core CSS to use double-colon for pseudo elements

We should probably enable https://stylelint.io/user-guide/rules/selector-pseudo-element-colon-nota... to make sure that we remain compliant 😅

Added, and CSS recompiled.

Left review on MR, moving to RTBC

The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".

Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

merged in commits from 10.1.x, setting back to RTBC

This looks great, one nit about the stylelint config but otherwise this is ready to go.

Closed 📌 Update stylelint rule selector-pseudo-element-colon-notation to be consistent with Drupal's CSS standards Closed: duplicate as duplicate and transferred credit.

longwave → credited joelpittet → .

longwave → credited occupant → .

longwave → credited codexmas → .

longwave → credited Mukeysh → .

longwave → credited alexpott → .

longwave → credited harsha012 → .

longwave → credited leahtard → .

Tested this with core's yarn lint:css script.

Added the code below to an Olivero PostCss file:

.test-class:before {
  display: block;
}

.test-class:::after {
  display: none;
}

.test-class::hover {
  text-decoration: underline;
}

The linter returned the below errors:

 29:12  ✖  Expected double colon pseudo-element notation          selector-pseudo-element-colon-notation
 33:12  ✖  Unexpected unknown pseudo-element selector ":::after"  selector-pseudo-element-no-unknown
 37:12  ✖  Unexpected unknown pseudo-element selector "::hover"   selector-pseudo-element-no-unknown

Ran the linter again with the --fix flag and it was able to auto-fix the selector-pseudo-element-colon-notation error while the unknown pseudo element errors remained.

The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".

This does not mean that the patch needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

I rebased the branch 10.1.x
Please review.

bnjmnm → closed merge request !3503

Did an additional regex check, but this is a pretty straightforward find and replace. If somehow something slipped through this doesn't preclude it from getting addressed in a separate issue, but this all looks fine. Committed to 10.1.x.

Automatically closed - issue fixed for 2 weeks with no activity.