[wp-trac] [WordPress Trac] #27404: Widget Customizer: Allow adding inactive widgets to widget areas

[WordPress Trac]

#27404: Widget Customizer: Allow adding inactive widgets to widget areas
-------------------------------------+-----------------------------
 Reporter:  westonruter              |       Owner:
     Type:  feature request          |      Status:  new
 Priority:  normal                   |   Milestone:  4.5
Component:  Widgets                  |     Version:  3.9
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch ux-feedback  |     Focuses:  ui, javascript
-------------------------------------+-----------------------------

Comment (by todd-inmotion):

 Replying to [comment:13 celloexpressions]:
 > I wonder if we should reconsider the term inactive"?
 >
 > "Remove" make sense from a widget area, whereas "deactivate" doesn't
 really. But to make that term match the name of the section that the
 removed widget goes to, maybe we should say "orphaned" or "unplaced" or
 even just "removed" widgets?
 >


 That has been a challenge for us for a while, "inactive but configured" is
 what we say internally, but yeh, probably move to something that more
 intuitive would be great.  See my "Move | Delete" option for above, how
 about that?


 > In terms of grouping all of the inactive widgets together vs. putting
 them under the corresponding new widgets, we should probably user test
 this as it could potentially get very confusing if we're not careful.

 We do have a Customer Experience group that does usability testing for us.
 We do it with 5 testers per test.  It isn't perfect, but it does catch any
 really serious issues.  I don't know if it would tell us which one is
 really "better" but it would tell us if either method is preventing people
 from saving then recovering configured widgets and if we created a
 barrier/problem.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/27404#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform