Mainly this issue refers to the Mime Mail support introduced by #698494: HTML Email Template Functionality (MIME mail support). In order to support upcoming Mime Mail features like #882528: Template suggestions based on mailkey or #319384: Add $mailkey to body tag as CSS class, we should use a more descriptive mailkey like e.g. "webform-$nid". With this functionality the messages would be able to have their own .css and .tpl files and could be styled based on the $mailkey. Furthermore perhaps a unique identifier could be set on the settings page and could be used for $mailkey and even $delta for the block functionality in #248157: Allow any Webform to be displayed as a block?

Comments

quicksketch’s picture

quicksketch
he/him
commented

See #837594: Give a machine name to webform and use it for theming, exports, features, form IDs, etc. for discussion on user-specified unique identifiers.

quicksketch’s picture

quicksketch
he/him
commented
Status: Active » Closed (won't fix)

At this point I don't think this change is likely to happen. In Webform you already have per-node template suggestions for e-mails (webform-mail-[nid].tpl.php). I imagine that MIME Mail templates per mail key may be useful for distinguishing completely separate e-mails that might not have templates at all, but in the case of Webform the trade-off probably isn't as great as in other use-cases. At this point I'd be more concerned about all the existing mechanisms we'd break with such a change.