[wp-trac] [WordPress Trac] #35210: Add notification area to Customizer

[WordPress Trac]

#35210: Add notification area to Customizer
-------------------------------------------------+-------------------------
 Reporter:  westonruter                          |       Owner:
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  4.5
Component:  Customize                            |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  needs-patch ux-feedback ui-feedback  |     Focuses:  ui,
                                                 |  javascript
-------------------------------------------------+-------------------------

Comment (by Kelderic):

 Replying to [comment:21 karmatosed]:
 > @Kelderic I appreciate what you are suggesting, however I think we are
 best to stick to conventions and usability, performance issues with what
 you are suggesting. I'm not convinced a entire section cover is apt for
 notifications. A notification doesn't need the entire section taken
 control of. Those are quite some impact visually. Adding an entire layer
 like that with animation too adds weight I don't think we need performance
 wise for notifications. It's worth noting we should not take away from the
 user experience with regards to that along with keep to conventions.

 I agree that taking up the entire panel might be a bit much, but I think
 we need to remember that in the event of an error occurring with saving,
 then that error message is now the '''primary''' content on the page. It
 should catch the eye and be unable to miss. This isn't as important with a
 success message (probably don't really even need one, not sure), but with
 an error it can be critical.

 Plus we want to respond to the user and prevent further changes while the
 submitting changes are being processed. An overlay does that, but it's
 also very obtrusive, and processing feedback isn't as critical as error
 feedback is.

 (The performance impact of `transform` is relatively minor, as is the
 performance impact of `opacity`, since neither requires a browser
 repaint.)

 What about using the button itself as feedback? Instead of just changing
 color, it could first change to a disabled state, and then change to a
 green or orange state, for success or error, with the error tied then to a
 message.

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