Thanks for the reminder, @webwrotter – I probably should have reported back earlier. I’ve actually been talking to ACF devs about this, who have been fantastic at researching and chatting about it. (Mad props to Liam G, especially.)
It turns out that ACF is behaving exactly like native WordPress core blocks do at the moment. While I don’t love how core handles it, I wouldn’t expect ACF to do things any differently.
This issue covers most of it: https://github.com/WordPress/gutenberg/issues/7342
But basically, WP core sees default values to be used at runtime, rather than when the block is inserted. Feel free to voice your opinion for change in the Github issue along with mine and some others
When I use the approach above, it LOOKS like things are working in the editor, but if you publish the page and view it, none of the default colors are applied. I put this document together to help illustrate and explain: https://docs.google.com/document/d/1VJmUCFFGRieIgkJ4Jj0PZiRefCrJQr2EUbBlzaBsPb0/edit
Same issue, but the problem appears to be larger than just not having the “Update” button be clickable. If I mess around in a core widget block, yes I can have the “Update” button be clickable again, but it doesn’t actually SAVE any of my changes in my ACF block (but the changes to the core block are updated).
Gah – of course, after submitting, I see how unclear the title was. It should read: Limit which TAXONOMIES users can filter by…
