In testing
📌
ComponentSourceInterface::submitConfigurationForm and validateConfigurationForm are never called
Active
it was discovered that we could publish content that included a webform block, even if the entity reference field referenced a non-existent block. This was discovered with webform, but could occur on any entity reference that requires that value to reference an entity that exists.
If we publish content with this invalid block field value, then the Page will crash on render.
In standard forms, validation prevents this from happening:
We know that #validation callbacks run on value changes as of 📌 ComponentSourceInterface::submitConfigurationForm and validateConfigurationForm are never called Active , but it seems like (please verify) they do not prevent publishing from occurring. If this isn't the reason, lets be sure to update the issue summary to remove that theory.
Active
1.0
… to be triaged
If the hypothesis in the issue summary is accurate, this is a stable blocker, so tagging it as such.
In fact, since we haven't released the beta yet, we should get this into that as well.
Beta blockers are by definition also stable blockers, but removing the latter tag so as to make it easier to scan a queue of stable blockers that aren't also blockers to beta or RC.