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)
Core
DOM: Security
Tracking
()
VERIFIED
FIXED
111 Branch
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.
Reporter | ||
Comment 1•8 years ago
|
||
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.
Comment 2•8 years ago
|
||
(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.
Updated•7 years ago
|
Priority: -- → P5
Comment 3•7 years ago
|
||
We can probably use a similar approach to what we are doing in testpilot: Container<number> if the name is not set.
Comment 4•7 years ago
|
||
Bulk change per https://bugzilla.mozilla.org/show_bug.cgi?id=1401020
status-firefox57:
--- → fix-optional
Updated•2 years ago
|
Severity: normal → S3
Assignee | ||
Updated•1 year ago
|
Assignee: nobody → contact
Assignee | ||
Comment 5•1 year ago
|
||
Updated•1 year ago
|
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
Updated•1 year ago
|
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
Comment 7•1 year ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox111:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
Updated•1 year ago
|
QA Whiteboard: [qa-111b-p2]
Comment 8•1 year ago
|
||
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.
Updated•1 year ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•