Cannot Populate a Colour Picker From an Image

[Myster]

Which component is this issue related to?

Umbraco.AI.Prompt

Which Umbraco AI version are you using? (Please write the exact version, example: 10.1.0)

17.1.0

Bug summary

The elipsis>wand did not appear when scoped to a field with editor: Umbraco.ColorPicker.EyeDropper

tested with: google / gemini-3.1-flash-lite

Specifics

I was going to try:

Analyze the image and choose a dominant, visually crisp color to use
as a background placeholder shown while the image loads.

{{image:umbracoFile}}

Requirements
- For the description field use html to display a swatch
- give the colour in hex format (#RRGGBB)

extra for experts:
I tried to prompt the AI to output HTML in the discription to show the colour visually, which it succeded at however the html was shown as text rather than rendered into colours.

Steps to reproduce

Create a prompt for a field of type - editor: Umbraco.ColorPicker.EyeDropper (or set it to show on every field.)
It does not show on the field I want

Expected result / actual result

I expect the elipsis and wand to show, and the value to be populated.

Dependencies

<PackageReference Include="Umbraco.AI" Version="17.1.0" />
<PackageReference Include="Umbraco.AI.Google" Version="17.0.0" />
<PackageReference Include="Umbraco.AI.OpenAI" Version="17.1.0" />
<PackageReference Include="Umbraco.AI.Prompt" Version="17.0.1" />

[mattbrailsford]

What CMS version are you using?

[Myster]

Umbraco version 17.5.1
Updated to 17.5.3, and didn't spot any difference.

[mattbrailsford]

Thanks for the detailed report — you found a real gap.

The wand-missing bug: the "Insert Prompt" action was gated behind a hard-coded list of "text-based" property editors (Textstring, Textarea, Rich Text, Markdown), so ColorPicker — in either the standard or Eye Dropper form — was never eligible, regardless of how the prompt was scoped. That allowlist predated a CMS feature (17.4.0's property value schemas) that lets us ask any property editor what shape of value it expects, so it's now removed: the wand can target any property editor, and the AI's output is constrained to match that editor's own value shape automatically.

Fixed in #245 (v18) and backported in #246 (v17), verified against both the Eye Dropper editor (plain hex value) and the standard Color Picker ({value, label}).

The HTML-in-description part: that one isn't a bug, so no fix needed there — it's expected behavior. The description field you were targeting is a plain text field, and those never render HTML (only the Rich Text Editor does). No property editor value renders raw markup as anything but literal text, so that approach wouldn't work regardless of AI.Prompt.

Will ship in the next release. Thanks again for taking the time to report this clearly!