bug#6757: 24.0.50; Search field in Customize

[Chong Yidong]

> 1. There is no doc for this new feature,
>
> 2. Click mouse-1 in the search field, then type, say, `.*fer'.
>    *IF* you could guess (without any doc) that `Search' runs
>    `customize-apropos', they you would expect that the regexp you
>    entered, `.*fer' would be passed to `customize-apropos'.
> 
>    But no; it is not.  The entire Search field is prepopulated with
>    spaces!
>
> 3. Also, in a virgin Search field (nothing typed), click Search.
>    Because of the current behavior of counting the leading
>    whitespace but not the trailing whitespace, the search string
>    used is "" (no leading whitespace because no non-whitespace
>    char to lead).

All these appear to be fixed.  Closing the bug.