Closed Bug 1316727 Opened 8 years ago Closed 1 year ago

Creating containers without a name can get confusing

Categories

(Core :: DOM: Security, defect, P5)

defect

Tracking

()

VERIFIED FIXED
111 Branch
Tracking Status
firefox57 --- wontfix
firefox111 --- fixed
firefox112 --- verified

People

(Reporter: pdehaan, Assigned: sdk)

References

(Blocks 1 open bug)

Details

(Whiteboard: [userContextId][domsecurity-backlog])

Attachments

(1 file)

Go to about:preferences#containers in Nightly

1. Add a new container and set a space as the container name.
2. Click "Done".
3. Select "File" > "New Container Tab" from the main menu


### Actual results:
There is an empty option in the menu where the unnamed container is.

### Expected results:
Maybe not allow unnamed containers, and we do a trim() on the container name before allowing the user to create a new container.
Similarly, I have three nameless containers, separated only by icon+colors, but the File > New Container Tab menu doesn't display the icons, so I just have 3 empty slots.
(In reply to Peter deHaan [:pdehaan] from comment #1)
> Similarly, I have three nameless containers, separated only by icon+colors,
> but the File > New Container Tab menu doesn't display the icons, so I just
> have 3 empty slots.

If you're using macOS, the missing icons are because of bug#1316919. If you're not using macOS, could you please let me know which OS you're seeing the missing icons under? We might have another regression somewhere :/

I agree that we shouldn't give users the ability to create "empty" containers with nothing but spaces. It's definitely not good UX.
Priority: -- → P5
We can probably use a similar approach to what we are doing in testpilot: Container<number> if the name is not set.
Severity: normal → S3
Assignee: nobody → contact
Attachment #9309759 - Attachment description: WIP: Bug 1316727 - Creating containers without a name can get confusing → Bug 1316727 - Creating containers without a name can get confusing r?mconley
Attachment #9309759 - Attachment description: Bug 1316727 - Creating containers without a name can get confusing r?mconley → Bug 1316727 - Ensure we cannot create a containers with no name r?mconley
Pushed by mconley@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4e5bd1922ed2
Ensure we cannot create a containers with no name r=mconley
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
QA Whiteboard: [qa-111b-p2]

Reproducible on a 2023-01-15 Nightly build on Ubuntu 22.
Verified as fixed on Nightly 112.0a1(build ID: 20230301225323) on Ubuntu 22, Windows 11, macOS 12.

Status: RESOLVED → VERIFIED
QA Whiteboard: [qa-111b-p2]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: