Support for token_or

I suspect you can use a different token like [webform_submission:user:email] to work around this issue.

I need to pre-populate a hidden field with the email address if the user is logged in, or a web parameter if not.
I think the use of token_or is better than the creation of a new token.
[current-user:email|current-page:query:url_param]

@jmaties thanks for a great idea, and introducing the token_or module for me.
The provided use case is quite common, and site-builders would love this feature.
As a developer I prefer creating new custom token, instead of putting logic to tokens. Because it is much easy to debug.

But I am afraid, introducing this feature will create more negative consequences for webform users in the future.

I would put these changes to token_or module, or create separate module to provide this integration.

You are right @znikiru :)
I have created a submodule of token_or ✨ Support for webform Needs work

@jmaties Thank you for creating and managing the webform support for the token_or.module.