confluence-content was designed to use only Confluence content (pages and blog posts). But we didn’t enforce it before. We are planning to introduce some smart features in our pickers so we had to do it.
That being said, we take data loss related issues very seriously and decided to introduce a fallback so that it doesn’t break existing macros. A user still won’t be able to add new arbitrary text to a confluence-content field.
