So remove its entry from the Wall.
Refs #20012, #20024
Refs http://trac.webkit.org/changeset/202324

[ci skip]

Add Wall of Browser Bugs entries for #12832

So remove its entry from the Wall of Browser Bugs
Refs #15832

[skip sauce]
[skip validator]

Update Wall of Browser Bugs accordingly.
Refs #19670

[ci skip]

See https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/7787318/
Refs #19670

[skip sauce]

Refs https://developer.mozilla.org/en-US/docs/Web/CSS/:dir
[skip sauce]

See https://bugzil.la/1278000
Refs #19670

[skip sauce]

See https://bugzilla.mozilla.org/show_bug.cgi?id=1277782
Refs #19839

[skip sauce]

See https://webkit.org/b/158342
Refs #17695.

[skip sauce]

Refs https://webkit.org/b/158340
Closes #20012

[skip sauce]

Refs https://crbug.com/597642
Closes #19810

[skip sauce]

Refs https://webkit.org/b/158276
Closes #19927

[skip sauce]

Remove its entry from the Wall of Browser Bugs
Refs #16372

[skip sauce]

Remove its entry from the Wall of Browser Bugs.

[skip sauce]

Update the Wall of Browser Bugs entry accordingly.

[skip sauce]

Remove its entry from the Wall of Browser Bugs.
Refs #16180

[skip sauce]

These bugs are factors in our decisions regarding which unit to use in our media queries.
Refs #17403
[skip sauce]

Refs #12536
[ci skip]

Due to the lack of this feature in browsers,
we currently have to implement an annoying setTimeout-based workaround,
which adds an extra layer of complication and probably slightly impacts performance:
https://github.com/twbs/bootstrap/blob/e391fcb953cc959ddd88fb676b68f49eef85ef06/js/src/util.js#L63-L77

[ci skip]

* https://connect.microsoft.com/IE/feedback/details/2445370 => https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/6793560/
* https://connect.microsoft.com/IE/feedback/details/2256049 => https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/7165383/
[skip sauce]

Refs #12078
[skip sauce]

Refs #16180, #16262
[skip sauce]

Refs https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/5381673/
[skip sauce]

[skip sauce]

Refs https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/
[skip sauce]

Refs https://bugzilla.mozilla.org/show_bug.cgi?id=1259972
Closes #19626
[ci skip]

https://crbug.com/595210

Closes #17338
[skip sauce]

Sounds like IE11 isn't getting non-critical fixes anymore, so there's no point in mentioning it (just like there's no point in mentioning IE10).
Help us, Edge-Wan Kenobi! You're our only hope.
[ci skip]

http://bugzil.la/1139853 was resolved as a duplicate of http://bugzil.la/924068
Refs #15990
[ci skip]

Refs https://bugzilla.mozilla.org/show_bug.cgi?id=1217012
Refs #19393
[ci skip]

https://bugzilla.mozilla.org/show_bug.cgi?id=1253468
Closes #19390
[skip sauce]

http://bugzil.la/1060131 has been fixed by http://bugzil.la/823483 which should land in Firefox 46.
Refs #14320
[ci skip]

http://bugzil.la/975632 has been fixed by http://bugzil.la/823483 which should land in Firefox 46.
Refs #10690
[ci skip]

Wasn't able to reproduce in iOS 9.2.
So remove its entry from the Wall of Browser Bugs.
Refs #14708
[skip sauce]

Refs https://github.com/twbs/bootstrap/issues/14839#issuecomment-60940738
[skip sauce]

Refs http://getbootstrap.com/getting-started/#overflow-and-scrolling
Refs #14839
[skip sauce]

https://connect.microsoft.com/IE/feedback/details/2274240/edge-edge-renders-an-svg-img-with-max-width-100-too-small
is fixed as of Edge 25.10586.0.0 (or possibly earlier).
Confirmed in https://github.com/twbs/bootstrap/issues/16915#issuecomment-175210482
Reverts #19010

[skip sauce]

https://connect.microsoft.com/IE/feedback/details/2274240/edge-edge-renders-an-svg-img-with-max-width-100-too-small
[skip sauce]