Open Bug 1355170 Opened 4 years ago Updated 1 year ago

the 'rank' field label is incorrectly visible in view mode again

Categories

(bugzilla.mozilla.org :: User Interface, defect, P3)

Production
defect

Tracking

()

People

(Reporter: MattN, Unassigned)

References

(Depends on 1 open bug)

Details

It looks like bug 1262474 has regressed as I'm seeing the label again in view mode.

+++ This bug was initially created as a clone of Bug #1262474 +++

if you're a member of a group that can set the rank field, but there isn't a value set, the label of the rank field is incorrectly visible in view mode.

the rank label should only be visible in view mode when a rank value has been set.
I want to think about that a minute. 

I think it's okay to show the rank field if it's not been set to socialize that the field exists.

Resolving as WORKSFORME, but willing to reconsider.

I think we should also rethink who has access to that field, but that's another bug.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
I disagree for many reasons:
1) Nothing relevant has changed since bug 1262474 was fixed AFAIK.
2) We hide other non-essential fields in view mode when they're unset as this is no different.
3) It looks bad with a label floating in the middle of nowhere since the default value is an empty string. There needs to at least be "---" or some other visual clue that the field is unset rather than looking like a UI glitch.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Can you point me at an example bug where this is the case? Nothing should have changed this, so I imagine it's a simple fix.
Assignee: nobody → dylan
Flags: needinfo?(MattN+bmo)
(In reply to Emma Humphries ☕️ (she/her) [:emceeaich] (UTC-8) +needinfo me from comment #1)
> I want to think about that a minute. 
> 
> I think it's okay to show the rank field if it's not been set to socialize
> that the field exists.
> 
> Resolving as WORKSFORME, but willing to reconsider.
> 
This isn't a good WORKSFORME because we don't know *why* this changed. It's fine if we later make this as a conscious decision, but if things change unintentionally, we have to investigate why.
Looks like this regressed in bug 1283012
Depends on: 1283012
Looks like we have: <div class="field inline edit-show" id="field-cf_rank" style="display:none">..
and the display: none is ignored because of a display: table-cell !important set for all .inline elements.

Not using !important for .inline causes a number of problems... I guess adding !important to the style="" element may work.
If we're using !important in our style definitions, that that's a definite code smell we ought to address. Agree with reopening this.

Will take a look after dropping tables from the modal UI.

Assignee: dylan → kohei.yoshino
Depends on: 1350424
Status: REOPENED → NEW
Assignee: kohei.yoshino → nobody
Component: User Interface: Modal → User Interface
You need to log in before you can comment on or make changes to this bug.