Hi Laird,
> What implicit assumptions were there when the specification was
> written? What implicit unspecified contract should Customizer
> Components adhere to? Should they provide their own button bars
> in all cases (i.e. is the "embedding in a panel" case just
> silly)? Or should they /n
Thanks so much for your answers. For the record I agree with you that
Customizers
should not provide their own buttons, but many problems do result from this
(that could easily be solved with a couple of backwards-compatible
specification clarifications).
For example:
- If a Customizer does n
