-
Notifications
You must be signed in to change notification settings - Fork 320
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 IE8–10 related Sass and CSS build tasks #3559
Conversation
07853ef
to
18192c0
Compare
This is brilliant work @querkmachine I've found a few more bits to remove that fall between the gaps of not-strictly-CSS:
|
Suppose there's always the bits we did incorrectly (ish) on purpose like Tagging @kevindew as he's been looking at Stylelint v15 breaking changes recently |
@colinrotherham Thanks for looking! For most of them, as you mention, I purposefully left them alone for not being strictly CSS related. The Good catch on pseudo-elements though, I would include updating those as part of this work! |
Yup, the argument for keeping the single colon was to not actively break compatibility with old IE by using a syntax they don't understand. There was, of course, always going to be a point that other stuff broken in those browers or usage sufficiently insignificant that we could drop it. Maybe we've hit that point? I imagine it's within the scope of your team to decide that. To make the switch, what I'd suggest doing is opening a draft PR to propose changing the rule in stylelint-config-gds and then changing the rule in this repo's |
986f11f
to
54c9691
Compare
* https://github.com/alphagov/stylelint-config-gds/pull/36 | ||
* https://stylelint.io/user-guide/rules/list/selector-pseudo-element-colon-notation/ | ||
*/ | ||
'selector-pseudo-element-colon-notation': 'double' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is brilliant. Thanks for the PR too:
@@ -22,6 +22,14 @@ Instead we recommend checking for the disabled attribute using [`$button.hasAttr | |||
|
|||
This change was introduced in [pull request #2830: Set the boolean disabled attribute consistently in the button component](https://github.com/alphagov/govuk-frontend/pull/2830). | |||
|
|||
#### Remove Internet Explorer 8 stylesheets, settings and mixins |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@querkmachine I liked your suggestion on Slack
Would you mind if we removed this CHANGELOG entry in favour of a (future) combined entry for all the IE8, IE9 and IE10 things we've taken out?
Probably can't say we've stopped supporting IE8 until we've removed the internal documentation too
e106835
to
63932b1
Compare
63932b1
to
21a995b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅ All looks good, approving
I've rebased this into the new src
packages/govuk-frontend/src
directory layout so hold off merging for now until we get main
as the new base (once #3491 merges)
Removes uses of the `govuk-if-ie8` and `govuk-not-ie8` mixins from Sass, removing IE8 specific code in the process, whilst maintaing any non-IE8 code. This commit does not remove the mixins themselves.
Clean up some other code which wasn't specifically scoped to IE8, but where the code structure had been altered to accommodate IE8.
…syntax. We can change from single colons to double colons, as single colons were only needed for IE8 support. Includes a temporary override of the GDS Stylelint configuration to not raise complaints about the use of double colons.
21a995b
to
d736de5
Compare
Ah you've accidentally merged into the other PR @querkmachine Did you want to revert until we're ready for I don't mind, but it might mean this PR needs opening again |
@colinrotherham Ah crap, sorry, the hold on merging totally slipped my mind. |
A big one, probably easier to go through it one commit at a time.
Because trimming out Internet Explorer 8–10 support (especially IE8) is such a big chunk of work, I've chosen to only focus on the Sass/CSS elements here. Any JavaScript-related pieces haven't been touched, nor have any aspects related to compatibility mode.
Resolves #3461 and resolves #2622 — except for documentation changes.
Changes
govuk-if-ie8
mixin and any code within them.govuk-not-ie8
mixin, maintaining any code within them.:before
) to the standards compliant double colon (::before
). Single colons were only needed for IE8 support.selector-pseudo-element-colon-notation
stylelint-config-gds#36Notes
This PR doesn't: