From 26a8a052c44a69331e92efdfe8f05531b7705bf5 Mon Sep 17 00:00:00 2001 From: Pavan Shinde Date: Tue, 3 Mar 2026 15:53:58 +0000 Subject: [PATCH] docs: use https for browserhacks link --- site/src/content/docs/getting-started/browsers-devices.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/src/content/docs/getting-started/browsers-devices.mdx b/site/src/content/docs/getting-started/browsers-devices.mdx index 3dd644edf2d4..f67c403ac581 100644 --- a/site/src/content/docs/getting-started/browsers-devices.mdx +++ b/site/src/content/docs/getting-started/browsers-devices.mdx @@ -66,7 +66,7 @@ Page zooming inevitably presents rendering artifacts in some components, both in ## Validators -In order to provide the best possible experience to old and buggy browsers, Bootstrap 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. +In order to provide the best possible experience to old and buggy browsers, Bootstrap uses [CSS browser hacks](https://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.