From 2f9d4d8ab251af35800a9f8b5ac86d1183c7d38e Mon Sep 17 00:00:00 2001 From: XhmikosR Date: Tue, 9 Jan 2018 15:34:24 +0200 Subject: [PATCH 1/6] Work around Travis errors by switching to sudo. --- .travis.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.travis.yml b/.travis.yml index 57c810b0a8..bc16945169 100644 --- a/.travis.yml +++ b/.travis.yml @@ -1,5 +1,7 @@ -sudo: false +sudo: required dist: trusty +addons: + chrome: stable language: node_js git: depth: 3 From 13be9aa00b899ff2a93c9da6ee423d5b05d28c92 Mon Sep 17 00:00:00 2001 From: XhmikosR Date: Wed, 10 Jan 2018 09:19:18 +0200 Subject: [PATCH 2/6] Ignore the bogus lang vnu.jar error. --- build/vnu-jar.js | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/build/vnu-jar.js b/build/vnu-jar.js index d1002c0a91..991d5c1c09 100644 --- a/build/vnu-jar.js +++ b/build/vnu-jar.js @@ -39,7 +39,9 @@ childProcess.exec('java -version', (error, stdout, stderr) => { 'The “time” input type is not supported in all browsers.*', // IE11 doesn't recognise
/ give the element an implicit "main" landmark. // Explicit role="main" is redundant for other modern browsers, but still valid. - 'The “main” role is unnecessary for element “main”.' + 'The “main” role is unnecessary for element “main”.', + // For some reason, the validator thinks the dashboard example is written in Danish + 'This document appears to be written in Danish.*' ].join('|') const args = [ From 5c53c8e64713cc9232f4fad1b8b58d4c6ab33c3b Mon Sep 17 00:00:00 2001 From: Vytas Date: Thu, 11 Jan 2018 10:26:32 +0200 Subject: [PATCH 3/6] Fix variable name in display utility class naming (#25261) --- docs/4.0/utilities/display.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/4.0/utilities/display.md b/docs/4.0/utilities/display.md index fd6dbe42be..f48d0a538f 100644 --- a/docs/4.0/utilities/display.md +++ b/docs/4.0/utilities/display.md @@ -19,7 +19,7 @@ As such, the classes are named using the format: * `.d-{value}` for `xs` * `.d-{breakpoint}-{value}` for `sm`, `md`, `lg`, and `xl`. -Where *display* is one of: +Where *value* is one of: * `none` * `inline` From d015ab90998d565611169d8ac3ad238c81651987 Mon Sep 17 00:00:00 2001 From: Christian Oliff Date: Thu, 11 Jan 2018 17:31:03 +0900 Subject: [PATCH 4/6] Update browser compatibility note for `position: sticky` since Edge supports it now (#25229) The latest shipping version of Edge supports position: sticky and I've successfully tested it with Bootstrap 4 and it works as intended. I added IE10 in place of Edge in that note as I assume that IE10 also has the `position: relative` fallback. REF: https://caniuse.com/#search=sticky --- docs/4.0/utilities/position.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/4.0/utilities/position.md b/docs/4.0/utilities/position.md index 9cf952452e..b194886260 100644 --- a/docs/4.0/utilities/position.md +++ b/docs/4.0/utilities/position.md @@ -38,7 +38,7 @@ Position an element at the bottom of the viewport, from edge to edge. Be sure yo Position an element at the top of the viewport, from edge to edge, but only after you scroll past it. The `.sticky-top` utility uses CSS's `position: sticky`, which isn't fully supported in all browsers. -**Microsoft Edge and IE11 will render `position: sticky` as `position: relative`.** As such, we wrap the styles in a `@supports` query, limiting the stickiness to only browsers that properly can render it. +**IE11 and IE10 will render `position: sticky` as `position: relative`.** As such, we wrap the styles in a `@supports` query, limiting the stickiness to only browsers that can render it properly. {% highlight html %}
...
From bea31472ea06ea180cd4a829d5814e0eb4364f38 Mon Sep 17 00:00:00 2001 From: Vytas Date: Thu, 11 Jan 2018 10:36:16 +0200 Subject: [PATCH 5/6] Fix invalid "constraint validation API" URL in docs (#25244) --- docs/4.0/components/forms.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/4.0/components/forms.md b/docs/4.0/components/forms.md index 3830f5a9f1..4735bd9a5c 100644 --- a/docs/4.0/components/forms.md +++ b/docs/4.0/components/forms.md @@ -711,7 +711,7 @@ Here's how form validation works with Bootstrap: - Bootstrap scopes the `:invalid` and `:valid` styles to parent `.was-validated` class, usually applied to the `
`. Otherwise, any required field without a value shows up as invalid on page load. This way, you may choose when to activate them (typically after form submission is attempted). - As a fallback, `.is-invalid` and `.is-valid` classes may be used instead of the pseudo-classes for [server side validation](#server-side). They do not require a `.was-validated` parent class. - Due to constraints in how CSS works, we cannot (at present) apply styles to a `