Skip to content

feat: Update supported browser versions

Lukas 'ai-pi' Eipert requested to merge leipert-update-browser-versions into next-major

What does this MR do?

feat: Change supported browsers for pre-compiled version

This changes our supported browsers from IE11 to:

  • Minimum Chrome / Edge 84
  • Minimum Firefox 68
  • Minimum Safari 13.1

This aligns our pre-compiled version of GitLab UI with the GitLab project.

BREAKING CHANGE: Pre-compiled version of GitLab UI dropped older browser support. If you need to use GitLab UI with older browsers, consume the source of GitLab UI directly.


feat: Remove resize-observer-polyfill

We are now targeting browsers that are all support the ResizeObserver API. Therefore we can remove the resize-observer-polyfill.

BREAKING CHANGE: If you target browsers that do not support ResizeObserver, you need to polyfill it yourself.

Does this MR meet the acceptance criteria?

Conformity

  • Code review guidelines.
  • GitLab UI's contributing guidlines.
  • If it changes a Pajamas-compliant component's look & feel, the MR has been reviewed by a UX designer.
  • If it changes GitLab UI's documentation guidelines, the MR has been reviewed by a Technical Writer.
  • If the MR changes a component's API, integration MR(s) have been opened in the following projects to ensure that the @gitlab/ui package can be upgraded quickly after the changes are released:
  • Added the ~"component:*" label(s) if applicable.

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • Security reports checked/validated by a reviewer from the AppSec team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

  • All actions and functionality can be done with a keyboard.
  • Links, buttons, and controls have a visible focus state.
  • All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
  • Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
  • Color combinations have sufficient contrast.
Edited by Lukas 'ai-pi' Eipert

Merge request reports