Problem/Motivation
#2698057: Add support for <nolink> and <none> to the LinkWidget UI added support for using and as LinkWidget UI input, but postponed the support for due cache side complexity.
Proposed resolution
Add support for .
Remaining tasks
- Validate if support is really needed, and what the best way to handle cache and/or editor expectations
- Work in a patch, if needed
- Review/Discuss/Commit
User interface changes
The widget description may be affected by introducing a paragraph about <current> option.
API changes
No
Data model changes
No