UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:62.0) Gecko/20100101 Firefox/62.0

Example URL:
https://jsfiddle.net/fj0wr59m/35/

Steps to reproduce the problem:
1. Open https://jsfiddle.net/fj0wr59m/35/ in Chrome on macOS or Android
2. See that the the stroke fails to get rendered on the top rectangle

What is the expected behavior?
The stroke should get rendered on both rectangles.

What went wrong?
It seems that when both `rx` and `ry` attributes of a `<rect>` element are set to exactly half of the value of `stroke-width`, the stroke fails to get rendered. The actual value of `rx`, `ry`, and `stroke-width` does not seem to matter as long as `rx` and `ry` have the same value and `stroke-width` equals two times that value.

In the provided example `rx` and `ry` are set to `10` and `stroke-width` is set to 20. In the example, the rectangle with correctly rendered stroke has a `stroke-width` set to 21, but it looks like any value other than 20 works correctly.

The values of `width` and `height` on the `<svg>` element do matter. It looks like the bug is triggered if any of them has a decimal part which is larger than around 0.016. For example `width="300"` does not trigger the bug, but "width="300.02" does trigger it. The actual value of `width` and `height` does not seem to matter, the bug is always triggered as long as one of them contains a decimal part larger than ~ 0.016.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes Chrome 52 - tested on BrowserStack

Does this work in other browsers? Yes

Chrome version: 69.0.3497.92 (Official Build) (64-bit)  Channel: stable
OS Version: OS X 10.13
Flash Version: Shockwave Flash 28.0 r0

The bug can be reproduced on macOS and Android. I wasn't able to reproduce it on Windows (using BrowserStack). Did not test in Linux.
 

Deleted: Screen Shot 2018-09-13 at 13.14.04.png 26.0 KB

	Screen Shot 2018-09-13 at 13.14.04.png 26.0 KB View Download