The LinkImage plugin should be on for all editor builds because of inline images #9482
Labels
package:image
package:link
resolution:expired
This issue was closed due to lack of feedback.
squad:core
Issue to be handled by the Core team.
type:task
This issue reports a chore (non-production change) and other types of "todos".
Because linking inline images is now possible (see #8871), it would make no sense if integrations that have inline images enabled (this will be default in all builds) would not allow creating this kind of content:
but
instead only because the
imageInline
in the model does not support thelinkHref
attribute. That would make no sense at all.OTOH, ATM
LinkImage
is an optional plugin and enabling it in all builds would be a huge breaking change because that would suddenly make block images linkable, which in turn may be unexpected (in a negative sense) for some integrations.Going even further, these integrations may want linking inline images possible (because they are inline, this is very natural) but they may not want linked block images.
I guess, just like the
Image
plugin, we'll need to splitLinkImage
intoLinkImage
(as a glue) andLinkBlockImage
andLinkInlineImage
to at least make it configurable and then we can figure out which of these should be enabled in builds.The text was updated successfully, but these errors were encountered: