[wp-trac] [WordPress Trac] #36164: Customizer selective refresh: improve the error messages style

[WordPress Trac]

#36164: Customizer selective refresh: improve the error messages style
---------------------------------------+--------------------
 Reporter:  afercia                    |       Owner:
     Type:  defect (bug)               |      Status:  new
 Priority:  normal                     |   Milestone:  4.5
Component:  Customize                  |     Version:  trunk
 Severity:  normal                     |  Resolution:
 Keywords:  has-screenshots has-patch  |     Focuses:  ui
---------------------------------------+--------------------

Comment (by melchoyce):

 Replying to [comment:10 westonruter]:
 > @melchoyce That is possible, and the UI for this has been prototyped in
 #34893, but it's too late for 4.5. I suggest we proceed with letting the
 error appear inline within the preview partial for this release (as again,
 it should be an exception—pun intended—rather than the norm). If that is
 not acceptable, then note also that the error message is also written out
 to the JS console via `console.error()`. The user would have to have their
 dev tools open to see it, however.

 What happens when a user sees this? Can they dismiss the message, or do
 they have to reload the customizer to get rid of the error? Will there be
 any copy that tells them how to fix it or what's wrong? Is there any way
 to say whether it's a theme or a plugin that caused the error?

 It seems super alarming that we're dropping code errors into someone's
 site preview. If I saw that without context, I would think that I broke my
 website and would probably panic. I expect to sometimes encounter errors
 in WordPress, but I don't expect to see those errors displayed on my site
 — even if it is just a preview. We should prioritize #34893 in 4.6.

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