bug#43218: EWW handles default answer incorrectly when changing a select

[Lars Ingebrigtsen]

Drew Adams <drew.adams@oracle.com> writes:

>> But I guess I still wonder why `completing-read' strips the text
>> properties from the completions?  If it's historical reasons, why
>> not allow minibuffer-allow-text-properties to override that?
>
> `completing-read' is likely older than text properties
> on strings.  (It was coded only in C for a long time.)
>
> As I said, `minibuffer-allow-text-properties' only has
> an effect on text that is in the minibuffer.  When you
> complete against candidates, the result may or may not
> ever get put into the minibuffer, and it has no text
> properties.

Right.  What I'm wondering is whether we could make the text properties
in the candidates survive the completion process is that variable is
non-nil.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no