You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the components still fundamentally work in IE8 without the considerations (even if it looks a bit ropey), we can remove them and drop IE8 support. But if they're fundamentally essential for a component to function, we'll need to talk with MOJ services about what level of support they require.
If we do drop support for IE8, then we can stop building/distributing the IE8-specific CSS file. This would need to be a major release.
The text was updated successfully, but these errors were encountered:
Since upgrading to govuk-frontend 4.6, the MOJ frontend package is throwing warnings caused by the use of the govuk-if-ie8 mixing, which has now been deprecated, and will be removed in v5 of govuk-frontend.
See #528 for more details, but as govuk-frontend v5 is removing support for IE8 we will be doing the same with our v2 (which requires govuk-frontend v5).
Following the GOV.UK Design System's lead we should consider removing support for IE8. We have a few components which make special considerations for IE8 that we should assess the validity of and remove if possible.
If the components still fundamentally work in IE8 without the considerations (even if it looks a bit ropey), we can remove them and drop IE8 support. But if they're fundamentally essential for a component to function, we'll need to talk with MOJ services about what level of support they require.
If we do drop support for IE8, then we can stop building/distributing the IE8-specific CSS file. This would need to be a major release.
The text was updated successfully, but these errors were encountered: