That’s the same as saying “I can copy this image, and my OCR app can convert it to text, so therefore Keyboard Maestro should be able to read the text too”. Not as obvious, but it is the same principle.
Keyboard Maestro can read either the plain text (in a whole bunch of encoding flavors), or the styled text (in a bunch of flavors). HTML is neither plain text nor styled text as far as Keyboard Maestro is concerned (because it’s not supported as styled text by NSAttributedString) - this is exactly why the clipboard has multiple flavors. Since Chrome actually knows how to render HTML, it should probably put styled text on the clipboard as well.
In this case, if Chrome copies the HTML, and no other styled text information, then you’ll need some sort of processing to convert the HTML into styled text.
You should be able to use the Clipboard condition and the “conforms to” check to see if there is RTF and/or HTML on the clipboard (although that wont tell you if there is something else that NSAttributedStrings can read as rich text).
It seems, for example to evaluate ‘public.html’ with a Chrome clipboard to true, but com.apple.webarchive with a Safari clipboard to false.
( but I may be missing something there – haven’t yet found a symbol for which it will return true in the presence of Safari’s «class weba» clipboard content, which can be hex-unpacked to a WebArchive plist containing a key for HTML)