Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove selector-pseudo-element-colon-notation #36

Merged
merged 1 commit into from
Jun 29, 2023

Conversation

querkmachine
Copy link
Member

@querkmachine querkmachine commented May 2, 2023

The Design System team is in the process of removing support for Internet Explorer 8, 9 and 10 from GOV.UK Frontend, signalling our intent to no longer support these browsers or provide fixes or polyfills specifically for them.

Supporting IE8–10 has not been a requirement for services since June 2018.

We do not expect service teams to continue making accommodations for legacy IE versions now or in future and are encouraging them to begin removing any code specifically for these versions of IE.

As part of this, we should remove selector-pseudo-element-colon-notation to begin enforcing the default standards-compliant double-colon syntax instead.

@colinrotherham
Copy link
Contributor

Think we're happy with this now @querkmachine if you'd like to bring it out of draft

Will probably want it to land before #32 🙌

@kevindew
Copy link
Member

Great, one thing I wonder is are we flipping this rule to be the stylelint default? if so we can just remove the rule rather than edit it

@querkmachine
Copy link
Member Author

@kevindew I think it's now the same as the default, yeah.

I figured switching it explicitly rather than removing might make it more obvious that changing it was a conscious decision (we want folks to update their authored code, not override it again in their local configs) but I can't rightfully say whether anyone would actually notice!

@querkmachine querkmachine marked this pull request as ready for review June 27, 2023 12:55
@kevindew
Copy link
Member

@kevindew I think it's now the same as the default, yeah.

I figured switching it explicitly rather than removing might make it more obvious that changing it was a conscious decision (we want folks to update their authored code, not override it again in their local configs) but I can't rightfully say whether anyone would actually notice!

Yup, that makes sense. Though our project goals are to have only things that differ from community standards so would be more consistent to remove it.

The Design System team is in the process of removing support for Internet Explorer 8, 9 and 10 from GOV.UK Frontend, signalling our intent to no longer support the browser or provide fixes or polyfills specifically for it.

Supporting IE8–10 has not been a requirement for services since June 2018.

Barring legacy projects, we do not expect services to be making accommodations for legacy IE versions now or in future, and encourage those projects to begin removing any code specifically for these versions of IE.

As part of this, we should remove `selector-pseudo-element-colon-notation` to begin enforcing the default standards-compliant double-colon syntax instead.
@querkmachine querkmachine force-pushed the kg-update-pseudo-elements branch from fa2673e to 5b3456c Compare June 27, 2023 13:15
@querkmachine querkmachine changed the title Flip value of selector-pseudo-element-colon-notation Remove selector-pseudo-element-colon-notation Jun 27, 2023
@querkmachine
Copy link
Member Author

@kevindew Fair enough! I've updated the PR to remove it instead.

Copy link
Contributor

@colinrotherham colinrotherham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, thanks @querkmachine

@querkmachine querkmachine merged commit 47677e4 into main Jun 29, 2023
@querkmachine querkmachine deleted the kg-update-pseudo-elements branch June 29, 2023 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants