Bug 1625674 Comment 4 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

There are two problems here. One is a Firefox bug, and one is a test bug.

(1) [Firefox bug] All elements here are expected to show 2 scrollbars, but some of them are only showing one scrollbar. This is due to bug 1042151.

(2) [Test bug] The test is assuming the scrollbars are always on the same side of the element. But in Firefox, we place the scrollbars on the writing-mode-specific "end" side of the element, I think.  Here's are some testcases showing that, with a scrollbar on the left side in Firefox:

```
data:text/html,<div style="background:yellow;direction:rtl;overflow:scroll;width:100px;height:100px"><div style="width:999px;height:9999px">

data:text/html,<div style="background:yellow;writing-mode:vertical-rl;overflow:scroll;width:100px;height:100px"><div style="width:999px;height:9999px">
```
(It looks like Safari agrees with Firefox on this, too, which is presumably why Safari "fails" this test as noted in comment 0 here.)

tonikitoo, would you mind filing a github issue or doing whatever's needed to get (2) addressed?
There are two problems here. One is a Firefox bug, and one is a test bug.

(1) [Firefox bug] All elements here are expected to show 2 scrollbars, but some of them are only showing one scrollbar. This is due to bug 1042151.

(2) [Test bug] The test is assuming the scrollbars are always on the same side of the element. But in Firefox, we place the scrollbars on the writing-mode-specific "end" side of the element, I think.  Here's are some testcases showing that, with a scrollbar on the left side in Firefox:

```
data:text/html,<div style="background:yellow;direction:rtl;overflow:scroll;width:100px;height:100px"><div style="width:999px;height:9999px">

data:text/html,<div style="background:yellow;writing-mode:vertical-rl;overflow:scroll;width:100px;height:100px"><div style="width:999px;height:9999px">
```
~(It looks like Safari agrees with Firefox on this, too, which is presumably why Safari "fails" this test as noted in comment 0 here.)~
[EDIT: This was apparently sort of wrong. I tested the last few versions of Safari, in April 2021 -- 14, 13.1, 12.1, 11.1 -- and they don't agree with Firefox **on the second testcase here**.]

tonikitoo, would you mind filing a github issue or doing whatever's needed to get (2) addressed?

Back to Bug 1625674 Comment 4