[wp-trac] [WordPress Trac] #26061: Customizer settings with non-scalar values incorrectly trigger as changed

WordPress Trac noreply at wordpress.org
Sun Dec 1 06:27:07 UTC 2013


#26061: Customizer settings with non-scalar values incorrectly trigger as changed
------------------------------+------------------
 Reporter:  westonruter       |       Owner:
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  3.8
Component:  Appearance        |     Version:  3.4
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |
------------------------------+------------------

Comment (by westonruter):

 @ocean90: here is a quick and dirty demo plugin:
 https://gist.github.com/westonruter/7729203

 You'll notice that if you hit the Update button in the control, that that
 the preview reloads and the customizer's state changes to unsaved, even
 though none of the setting's properties were changed.

 As for not enqueueing all of Underscore.js for this one function
 <http://underscorejs.org/docs/underscore.html#section-84>, we could copy
 it out and include it in `customize-base.js`, maybe as `api.Value.isEqual(
 to )`

--
Ticket URL: <http://core.trac.wordpress.org/ticket/26061#comment:5>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list