As discussed in #18061, the new LinkControl component can be considered as a composite component of URLInput, plus labeling behaviors associated with similar *Control input control components. In this model, URLInput should be considered a very barebones component whose sole responsibility should be to render an input field and associated URL autocompletion results from which to pick a value.
Currently, URLInput is enhanced to support "custom" rendering behavior of suggestions, which is leveraged by LinkControl to customize the appearance of its suggestions. These should be migrated to URLInput and considered to be the new default appearance of URL suggestions. The motivation for this is to assure consistency of link suggestions for all use of URLInput (UX), and avoid the maintenance cost associated with maintaining multiple implementations of search result appearances (DevX).
Previously: https://github.com/WordPress/gutenberg/issues/18061#issuecomment-580480464
As discussed in #18061, the new
LinkControl
component can be considered as a composite component ofURLInput
, plus labeling behaviors associated with similar*Control
input control components. In this model,URLInput
should be considered a very barebones component whose sole responsibility should be to render an input field and associated URL autocompletion results from which to pick a value.Currently,
URLInput
is enhanced to support "custom" rendering behavior of suggestions, which is leveraged byLinkControl
to customize the appearance of its suggestions. These should be migrated toURLInput
and considered to be the new default appearance of URL suggestions. The motivation for this is to assure consistency of link suggestions for all use ofURLInput
(UX), and avoid the maintenance cost associated with maintaining multiple implementations of search result appearances (DevX).