Closed Bug 1060795 Opened 10 years ago Closed 7 years ago

WebIDE menu incorrectly shows name and icon of the current app

Categories

(DevTools Graveyard :: WebIDE, enhancement)

34 Branch
x86
macOS
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: ac, Unassigned)

References

Details

The WebIDE user interface shows a menu at the top left of the User interface which allows a user to switch between 'projects' or open new applications (though not close for some reason). 

When a user switches to work on an App, that top-left menu (let's call it the "project menu") changes to have the logo and name of the current app. This is cute but semantically WRONG---none of the entries have anything to do with the current app. The project menu is entirely related to WebIDE and its functions.

The project menu should have its own name and, if an icon, the webide icon.

The feedback of the current project, including its name and icon, should be placed away from this project menu.
Severity: normal → enhancement
Can confirm the behavior.

I feel it's semantically okay because it's meant to toggle between recent projects. I liken it to the "accounts" dropdown in Gmail and other Google apps.

There is no "close" option because closing the WebIDE window closes the project.
Yeah, I believe this is just a UX design choice.  The current approach and the suggestion in comment 0 are both possible approaches, but neither one strikes me as obviously better than the other.

The runtime menu on the right makes the same design choice: the button shows the current runtime, and the menu shows all the available runtimes.  It also has some actions to act on the current runtime.

I'll leave this open for now in case others are similarly confused by the current UX.
We don't plan to alter the WebIDE interface at this stage, since it's planned for removal (bug 1314811).
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: Firefox → DevTools
Product: DevTools → DevTools Graveyard
You need to log in before you can comment on or make changes to this bug.