Skip to content

Commit 3c24a25

Browse files
authored
Merge pull request #291 from trimble-oss/coliff-patch-1
Clean up browser support and mobile modal sections
2 parents e2c7550 + 4a02e26 commit 3c24a25

1 file changed

Lines changed: 1 addition & 19 deletions

File tree

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

Lines changed: 1 addition & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -50,31 +50,13 @@ For Firefox, in addition to the latest normal stable release, we also support th
5050

5151
Unofficially, Modus Bootstrap should look and behave well enough in Chromium and Chrome for Linux, and Firefox for Linux, though they are not officially supported.
5252

53-
## Internet Explorer
54-
55-
Internet Explorer is not supported.
56-
57-
## Modals and dropdowns on mobile
58-
59-
### Overflow and scrolling
60-
61-
Support for `overflow: hidden;` on the `<body>` element is quite limited in iOS and Android. To that end, when you scroll past the top or bottom of a modal in either of those devices' browsers, the `<body>` content will begin to scroll. See [Chrome bug #175502](https://bugs.chromium.org/p/chromium/issues/detail?id=175502) (fixed in Chrome v40) and [WebKit bug #153852](https://bugs.webkit.org/show_bug.cgi?id=153852).
62-
63-
### iOS text fields and scrolling
64-
65-
As of iOS 9.2, while a modal is open, if the initial touch of a scroll gesture is within the boundary of a textual `<input>` or a `<textarea>`, the `<body>` content underneath the modal will be scrolled instead of the modal itself. See [WebKit bug #153856](https://bugs.webkit.org/show_bug.cgi?id=153856).
66-
67-
### Navbar Dropdowns
68-
69-
The `.dropdown-backdrop` element isn't used on iOS in the nav because of the complexity of z-indexing. Thus, to close dropdowns in navbars, you must directly click the dropdown element (or [any other element which will fire a click event in iOS](https://developer.mozilla.org/en-US/docs/Web/API/Element/click_event#Safari_Mobile)).
70-
7153
## Browser zooming
7254

7355
Page zooming inevitably presents rendering artifacts in some components, both in Bootstrap 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.
7456

7557
## Validators
7658

77-
In order to provide the best possible experience to old and buggy browsers, Modus 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.
59+
In order to provide the best possible experience to old and buggy browsers, Modus 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.
7860

7961
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.
8062

0 commit comments

Comments
 (0)