Layout Builder shouldn't use the default value to determine whether a field has a value or not

Hello! Thank you for raising a very detailed issue.

Could you please confirm that the steps to reproduce in the IS are with a fresh install of Drupal 11? If not can they be updated with the steps to reproduce starting with a fresh install of D11?

I'm asking because I've tried to this and I've been unable to replicate this. The steps I've followed are below:

• Fresh install of a standard D11 site
• Enabled LB
• Added Layout builder to articles
• Added a text field to articles with a default value of "Default text"
• Created a new article and removed the default value from the field
• Went to LB for the article and added the fieldblock for the new field.
• I'm not able to see the label as described in the IS

Thanks!

Yes, this is replicable on a clean installation using Simplytest. And sorry I mispoke, the behaviour more apparent when the "Display title" option is ticked on the block.

Relevant links available here (username: admin, password: admin):

• Text field with "default value"
• Layout Builder with the new "Text with default value" field and a Title set
• Sample content with the bug

Updated the patch to fix all related test failures:

• LayoutBuilderDefaultValuesTest: Adjusted alt text and file name checks to correctly match fields with storage/instance defaults. Updated string field checks for default value handling.
• FieldBlockTest: Fixed access check logic when a field is empty but has a default value. Access should be allowed in that case.
• BlockFilterTest: Adjusted block filter assertions to handle variations in block counts when filtering by text like "ad" or "adm".

Seems more like a feature request and disruptive one for existing sites