WordPress.org

Make WordPress Core

Changes between Initial Version and Version 2 of Ticket #30951


Ignore:
Timestamp:
01/08/2015 06:40:24 PM (7 years ago)
Author:
westonruter
Comment:

Please file a separate ticket for the other issue you reported, which I've removed from the description. It is surely a different issue, probably something specific with the color picker control.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #30951

    • Property Keywords has-patch added
  • Ticket #30951 – Description

    initial v2  
    33After I upgraded to v4.1, I found out, that now the customizer is capable to refresh the values if I change it from javascript and I don't have to reload the customizer page.
    44
    5 '''But, it has some small issues:'''
    6 1. if I set empty for color in one subtemplate and I changed from a subtemplate which had this color set, then the color value is empty, but the color box, beside the input is colored.
    7 `api.instance('background_color').set('');` <- I mean that for empty
     5'''But, it has some small issues, including:'''
    86
    9 2. radio buttons don't get checked correctly. I can say, they are not checked at all, after changed one subtemplate to another.
     7radio buttons don't get checked correctly. I can say, they are not checked at all, after changed one subtemplate to another.
    108
    11 I try to explain the second one (2):
     9I try to explain:
    1210
    1311I added new setting:
     
    7270
    7371It is only visually incorrect, because if I click on the save button, the data is saved correctly.
    74 But, it will be visually correct, only if I reload the customizer page. The same happens with case 1 (color)
     72But, it will be visually correct, only if I reload the customizer page.