From e0ad7e4bd9fd9174b413bb61b95bd4316108f5ae Mon Sep 17 00:00:00 2001 From: Louis-Maxime Piton Date: Thu, 8 Aug 2024 08:09:22 +0200 Subject: [PATCH] docs(getting started): add 'Browsers and devices' page (#2684) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Julien Déramond --- .../0.0/getting-started/browsers-devices.md | 72 ++++++++++++++++++- site/data/sidebar.yml | 1 - 2 files changed, 71 insertions(+), 2 deletions(-) diff --git a/site/content/docs/0.0/getting-started/browsers-devices.md b/site/content/docs/0.0/getting-started/browsers-devices.md index af5b88b788..001a2baec3 100644 --- a/site/content/docs/0.0/getting-started/browsers-devices.md +++ b/site/content/docs/0.0/getting-started/browsers-devices.md @@ -8,4 +8,74 @@ aliases: toc: true --- -{{< callout-soon "page" >}} +## Supported browsers + +OUDS Web supports the **latest, stable releases** of all major browsers and platforms. + +Alternative browsers which use the latest version of WebKit, Blink, or Gecko, whether directly or via the platform's web view API, are not explicitly supported. However, OUDS Web should (in most cases) display and function correctly in these browsers as well. More specific support information is provided below. + +You can find our supported range of browsers and their versions [in our `.browserslistrc file`]({{< param repo >}}/blob/v{{< param current_version >}}-ouds-web/.browserslistrc): + +```text +{{< rf.inline >}} +{{- readFile ".browserslistrc" | chomp | htmlEscape -}} +{{< /rf.inline >}} +``` + +We use [Autoprefixer](https://github.com/postcss/autoprefixer) to handle intended browser support via CSS prefixes, which uses [Browserslist](https://github.com/browserslist/browserslist) to manage these browser versions. Consult their documentation for how to integrate these tools into your projects. + +### Mobile devices + +Generally speaking, OUDS Web supports the latest versions of each major platform's default browsers. Note that proxy browsers (such as Opera Mini, Opera Mobile's Turbo mode, UC Browser Mini, Amazon Silk) are not supported. + +{{< bs-table "table" >}} +| | Chrome | Firefox | Safari | Android Browser & WebView | +| --- | --- | --- | --- | --- | +| **Android** | Supported | Supported | — | v6.0+ | +| **iOS** | Supported | Supported | Supported | — | +{{< /bs-table >}} + +### Desktop browsers + +Similarly, the latest versions of most desktop browsers are supported. + +{{< bs-table "table" >}} +| | Chrome | Firefox | Microsoft Edge | Opera | Safari | +| --- | --- | --- | --- | --- | --- | +| **Mac** | Supported | Supported | Supported | Supported | Supported | +| **Windows** | Supported | Supported | Supported | Supported | — | +{{< /bs-table >}} + +For Firefox, in addition to the latest normal stable release, we also support the latest [Extended Support Release (ESR)](https://www.mozilla.org/en-US/firefox/enterprise/) version of Firefox. + +Unofficially, OUDS Web should look and behave well enough in Chromium and Chrome for Linux, and Firefox for Linux, though they are not officially supported. + +## Internet Explorer + +Internet Explorer is not supported. + + + +## Browser zooming + +Page zooming inevitably presents rendering artifacts in some components, both in OUDS Web and the rest of the web. Depending on the issue, we may be able to fix it (search first and then open an issue if need be). However, we tend to ignore these as they often have no direct solution other than hacky workarounds. + +## Validators + +In order to provide the best possible experience to old and buggy browsers, OUDS Web uses [CSS browser hacks](http://browserhacks.com/) in several places to target special CSS to certain browser versions in order to work around bugs in the browsers themselves. These hacks understandably cause CSS validators to complain that they are invalid. In a couple places, we also use bleeding-edge CSS features that aren't yet fully standardized, but these are used purely for progressive enhancement. + +These validation warnings don't matter in practice since the non-hacky portion of our CSS does fully validate and the hacky portions don't interfere with the proper functioning of the non-hacky portion, hence why we deliberately ignore these particular warnings. + +Our HTML docs likewise have some trivial and inconsequential HTML validation warnings due to our inclusion of a workaround for [a certain Firefox bug](https://bugzilla.mozilla.org/show_bug.cgi?id=654072). diff --git a/site/data/sidebar.yml b/site/data/sidebar.yml index c008fcca9f..a699e187b8 100644 --- a/site/data/sidebar.yml +++ b/site/data/sidebar.yml @@ -11,7 +11,6 @@ - title: Contents draft: true - title: Browsers & devices - draft: true - title: JavaScript draft: true - title: Webpack