Open Bug 1609159 Opened 4 years ago Updated 2 years ago

Issues for profile rename windows if user/name string is really long

Categories

(Toolkit :: Startup and Profile System, defect, P5)

Unspecified
All
defect

Tracking

()

Tracking Status
firefox-esr68 --- affected
firefox72 --- affected
firefox73 --- affected
firefox74 --- affected

People

(Reporter: cfogel, Unassigned)

References

Details

Attachments

(1 file)

Attached image Screenshot_2.png

Affected versions

  • 72.0.1, 68.3.0esr, 73.0b4, 74.0a1 (2020-01-13);

Affected platforms

  • Windows 10, macOS 10.15, Ubuntu 19.04;

Steps to reproduce

  1. Launch Firefox;
  2. Access about:profiles
  3. Click on the Rename profile for any of the ones listed ( create a new one if only one in use);
  4. Rename the profile with a really long string such as this example;
  5. Click on the Ok button;
  6. Click on the Rename button for that profile again;

Expected result

  • rename window is displayed and buttons are visible;

Actual result

  • see attachment;

Regression range

  • inclined to say it's not a regression since even with 47.0.2 this issue existed;

Additional notes

  • became visible after 1600897 and the Update Fluent.jsm to @fluent/bundle 0.14.1 in bug 1604839;
  • the highest impact is displayed on Windows OS, since the user is unable to get to the Ok/Cancel buttons;
  • the window for the rename on the Profile selector(when starting up Firefox) stretches out of view vertically instead of horizontally;
  • marking as minor since this is really somewhat of an edge-case to begin with.
See Also: → 1600897

(In reply to Cristian Fogel, QA [:cfogel] from comment #0)

Regression range

  • inclined to say it's not a regression since even with 47.0.2 this issue existed;

Additional notes

  • became visible after 1600897 and the Update Fluent.jsm to @fluent/bundle 0.14.1 in bug 1604839;

I'm confused. If this issue was present with 47.0.2 how did it become visible after bug 1600897 was fixed?

Flags: needinfo?(cristian.fogel)

Actually yeah, phrasing was not necessary and causes more confusion.
More or less was somewhat of a reasoning why it got reported "late"; so it would be best to ignore that part.
Sorry for the confusion.

Flags: needinfo?(cristian.fogel)

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

For more information, please visit auto_nag documentation.

Flags: needinfo?(dtownsend)
Flags: needinfo?(dtownsend)
Priority: -- → P5
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.