Remove "Wall of browser bugs" page. (#29297)

While important in the past, it has become obsolete, so removing it seems the best solution.

site/content/docs/4.3/browser-bugs.md

@@ -1,50 +0,0 @@
----
-layout: docs
-title: Wall of browser bugs
-group: browser-bugs
-aliases: "/browser-bugs/"
----
-
-Bootstrap currently works around several outstanding browser bugs in major browsers to deliver the best cross-browser experience possible. Some bugs, like those listed below, cannot be solved by us.
-
-We publicly list browser bugs that are impacting us here, in the hopes of expediting the process of fixing them. For information on Bootstrap's browser compatibility, [see our browser compatibility docs]({{< docsref "/getting-started/browsers-devices#supported-browsers" >}}).
-
-See also:
-
-* [Chromium issue 536263: [meta] Issues affecting Bootstrap](https://bugs.chromium.org/p/chromium/issues/detail?id=536263)
-* [Mozilla bug 1230801: Fix the issues that affect Bootstrap](https://bugzilla.mozilla.org/show_bug.cgi?id=1230801)
-* [WebKit bug 159753: [meta] Issues affecting Bootstrap](https://bugs.webkit.org/show_bug.cgi?id=159753)
-
-
-{{< bug.inline >}}
-{{- $type := .Get "type" | default "bug" -}}
-{{- $data := .Get "data" | default "browser-bugs" -}}
-<table class="bd-browser-bugs table table-bordered table-hover">
-  <thead>
-    <tr>
-      <th>Browser(s)</th>
-      <th>Summary of {{ $type }}</th>
-      <th>Upstream issue(s)</th>
-      <th>Bootstrap issue(s)</th>
-    </tr>
-  </thead>
-  <tbody>
-    {{- range (index $.Site.Data $data) }}
-    <tr>
-      <td>{{ .browser | chomp }}</td>
-      <td>{{ .summary | markdownify }}</td>
-      <td>{{ partial "bugify" .upstream_bug }}</td>
-      <td>{{ partial "bugify" .origin }}</td>
-    </tr>
-    {{- end }}
-  </tbody>
-</table>
- {{< /bug.inline >}}
-
-# Most wanted features
-
-There are several features specified in Web standards which would allow us to make Bootstrap more robust, elegant, or performant, but aren't yet implemented in certain browsers, thus preventing us from taking advantage of them.
-
-We publicly list these "most wanted" feature requests here, in the hopes of expediting the process of getting them implemented.
-
-{{< bug.inline data="browser-features" type="feature" />}}

site/content/docs/4.3/getting-started/browsers-devices.md

@@ -105,8 +105,6 @@ For Firefox, in addition to the latest normal stable release, we also support th
 
 Unofficially, Bootstrap should look and behave well enough in Chromium and Chrome for Linux, Firefox for Linux, and Internet Explorer 9, though they are not officially supported.
 
-For a list of some of the browser bugs that Bootstrap has to grapple with, see our [Wall of browser bugs]({{< docsref "/browser-bugs" >}}).
-
 ## Internet Explorer
 
 Internet Explorer 11 is supported; IE10 and down is not. Please be aware that some CSS3 properties and HTML5 elements are not fully supported in IE10, or require prefixed properties for full functionality. Visit [Can I use...](https://caniuse.com/) for details on browser support of CSS3 and HTML5 features. **If you require IE8-9 support, use Bootstrap 3.**

site/content/docs/4.3/migration.md

@@ -135,4 +135,8 @@ Badges were overhauled to better differentiate themselves from buttons and to be
 - **Todo:** Drop `.text-hide` as it's an antiquated method for hiding text that shouldn't be used anymore
 - **Todo:** Split utilities into property-value utility classes and helpers
 
+## Docs
+
+-  Removed "Wall of browser bugs" page because it has become obsolete
+
 ## Build tools