1165746 - In css writing-mode:vertical-rl, "Find" does not always scroll the highlight into the visible area of the browser window.

Status: NEW

(Toolkit :: Find Toolbar, defect, P5)

Description

[Alice0775 White]

Attachment: 芥川龍之介 羅生門.html

If found word is in the right of the viewport
"Find" does not scroll the highlight into the visible area of the browser window.

Steps To Reproduce
1. Enable writing mode (and ruby)
  user_pref("layout.css.vertical-text.enabled", true);
  user_pref("layout.css.ruby.enabled", true);
2. Open attached
3. Scroll to left end
3. Open FindBar (Ctrl+F)
4. Input 羅生門 to Find field
   --- BUG, Page scrolled but not enough, so the highlight not visible
5. Try Find Previous (Shift+F3) several times
   --- BUG, Page scrolled but not enough, so the highlight not visible

Actual results:
If found word is in the right of the viewport
"Find" does not scroll the highlight into the visible area of the browser window.

Expected Results:
The page should be scrolled the highlight into the visible area.
And also, scroll to center as much as possible if the highlight was not visible.

Comment 1

[Gérard Talbot]

We most likely need to create a test with scrollIntoView() and with different code scenarios...

Comment 2

[張俊芝(ZHANG Junzhi)]

This might be caused by bug 1453303. Because the showing of the find toolbar will reflow the whole content, but the find toolbar still scrolls according to old positions.

Comment 3

[Alice0775 White]

(In reply to 張俊芝(ZHANG Junzhi) from comment #2)

This might be caused by bug 1453303. Because the showing of the find toolbar
will reflow the whole content, but the find toolbar still scrolls according
to old positions.

Not related.

In vertical writing mode, scrolling into view does not seem to take into account the boundary rectangle of the selection. Only the baseline of the selection seems to have been considered.

Comment 4

[Gérard Talbot]

Alice0775 White, I believe this bug is related to bug 1263810.

Comment 5

[Alice0775 White]

(In reply to Gérard Talbot from comment #4)

Alice0775 White, I believe this bug is related to bug 1263810.

I do not think so.
Those all testcases in bug 1263810 seems OK(getting reasonable results) for me.