Open Bug 1561232 Opened 5 years ago Updated 2 years ago

The RDM Toolbar buttons are not displayed in the right order on RTL builds

Categories

(DevTools :: Responsive Design Mode, defect, P3)

Product:
DevTools
Component:
Responsive Design Mode
Platform:
Desktop
All
Type:
defect

Tracking

(firefox67 affected, firefox68 affected, firefox69 affected, firefox72 affected, firefox73 affected, firefox74 affected)

Tracking Flags:
Tracking Status
firefox67 --- affected
firefox68 --- affected
firefox69 --- affected
firefox72 --- affected
firefox73 --- affected
firefox74 --- affected

People

(Reporter: rdoghi, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [rdm-reserve])

[Affected versions]:
Nightly 69.0a1

[Affected platforms]:
Platforms: ALL

Prerequisites:
Download and Install a RTL Firefox build.

Steps :

  1. Launch the Firefox browser and reach www.facebook.com
  2. Hit Ctrl + Shift + M in order to start Responsive Design Mode.

Expected Results :
The Toolbar buttons should be displayed from right to left starting with the List of devices and ending with the Touch simulation on the left side.

Actual Results :
RTL builds have the same order for the Toolbar buttons as normal builds.

I'm not sure if it should block the meta-viewport bug since its not really connected to the meta-viewport preference. Please remove it if necessary.

Blocks: rdm-meta-viewport
status-firefox67: --- → affected
status-firefox68: --- → affected
status-firefox69: --- → affected

Good find. You are correct that it's not dependent on meta viewport. Changing the blockers to account for that.

Blocks: rdm-ux
No longer blocks: rdm-meta-viewport
Whiteboard: [rdm-reserve]
Priority: -- → P3

Hi, we also noticed that the Resize Corner is still on the bottom right side.. I think it should be on the bottom left side on RTL builds, I might be wrong on this though. Updating the flags for this issue as well.

status-firefox72: --- → affected
status-firefox73: --- → affected
status-firefox74: --- → affected
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.