If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Should be able to collapse the Title/TOC/Rendering-max-age area after opening it

NEW
Unassigned

Status

Mozilla Developer Network
General
--
enhancement
3 years ago
a year ago

People

(Reporter: sheppy, Unassigned)

Tracking

Details

(Whiteboard: [specification][type:change])

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
What feature should be changed? Please provide the URL of the feature if possible.
==================================================================================
In order to edit the title, TOC depth, rendering max age, and translation source, you have to click a link to expand the title into the editing area for these fields.

There is no way to close it again when you're done, which is unbalanced and counterintuitive.

What problems would this solve?
===============================
Being able to close this would feel more "normal" and would let the user put that information away once done using it, or if they expanded these items by mistake.

Who would use this?
===================
Various users.

What would users see?
=====================
A link "Hide these options" or something like that, which would restore the original state (but preserving anything edited). Ideally there'd be some kind of little indicator that changes were made within.

What would users do? What would happen as a result?
===================================================
Click link. Get rid of scary scary options.

Is there anything else we should know?
======================================
Created attachment 8485051 [details]
Screen Shot 2014-09-05 at 10.42.34 AM.png

Attaching a screenshot so others understand. 

The attached image shows that when you open the editing interface to edit the title, etc. of an article, you have no way to collapse the editing interface again.
Severity: normal → enhancement
Mentor: shobson@mozilla.com
Mentor: shobson@mozilla.com
You need to log in before you can comment on or make changes to this bug.