Open Bug 1593840 Opened 5 years ago Updated 2 years ago

[RTL] In-content HTML page scrollbars are on the incorrect side

Categories

(Core :: Layout: Scrolling and Overflow, defect, P3)

defect

Tracking

()

People

(Reporter: itiel_yn8, Unassigned)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression, rtl, Whiteboard: about:addons)

Attachments

(1 file)

Attached image Screenshot (deleted) —

This was an issue before, but bug 1525175 made it worse by extending the scrollbar to the entire view's height, and now it is more obstructive.

See attached.

Summary: [RTK] about:addons' addons list scrollbar should be on the left side of the view → [RTL] about:addons' addons list scrollbar should be on the left side of the view

So about:preferences manages to do this. It looks like it's from the localedir="rtl" property, but I can't get this to work in about:addons or about:config which are HTML documents. Going to need to dig into it a little more.

Priority: -- → P2
Whiteboard: about:addons

btw bug 1514316 first regressed this.

Regressed by: 1514316

STR

  1. Set Firefox to RTL mode (`intl.l10n.pseudo = "bidi" should work)
  2. Open about:config
  3. Click the "Show All" button
  4. Scroll

Expected Results: The scrollbar is on the left side.
Actual Results: The scrollbar is still on the right side.

This is also happening in the about:addons HTML frame (which should eventually move top-level but about:config is there now).

Bug 1594059 is similar for about:preferences (XUL) where the scrollbar is missing in some cases.

Component: Add-ons Manager → Layout: Scrolling and Overflow
Priority: P2 → --
Product: Toolkit → Core
Summary: [RTL] about:addons' addons list scrollbar should be on the left side of the view → [RTL] In-content HTML page scrollbars are on the incorrect side

The priority flag is not set for this bug.
:dbaron, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(dbaron)

The pref's description and the code that implements it might be helpful here, although I don't see why any of that would lead to an HTML versus XUL difference, unless perhaps it's a parent process versus content process difference. (The two relevant prefs here are layout.scrollbar.side and bidi.direction.) I don't remember what the rules about preferences in the content process are...

The other question is whether the behavior here matches (a) web pages and (b) user interface generally.

Flags: needinfo?(dbaron)
Priority: -- → P3
Has Regression Range: --- → yes
Severity: normal normal → S3 S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: