"errors_level":

$builder->add('field', 'type', array(
    // show errors on the field
    'errors_level' => 'field',
    // show errors on the form
    'errors_level' => 'form',
));

"inline_errors":

$builder->add('field', 'type', array(
    // show errors on the field
    'inline_errors' => true,
    // show errors on the form
    'inline_errors' => false,
));

field vs form is weird IMO, as everything is a Form in Symfony. It should be root to talk about the root form to be consistent

Which leads me to an alternative proposal:

$builder->add('field', 'type', array(
    // show errors on the field
    'display_errors' => 'self',
    // show errors on the parent form
    'display_errors' => 'parent',
    // show errors on the root form
    'display_errors' => 'root',
));

display_errors makes me think about the PHP setting, and so I would except to set either true or false. It is more a matter of "level" IMHO.

maybe error_location or error_position ?

@stof what's the difference between your two proposals?

sorry, edited it to actually give the 2 proposal I thought about

what about display_errors_on or just errors_on with self, parent and root as options as proposed by @bschussek ?

Alternatively, error_location sounds clear enough for me, as well.

So when you would want to show errors two levels higher in hierarchy, you would set error_location of the field to parent and in the parent form you set the option to parent as well. Right?

I think the new option with parent|self|root makes more sense than the old error_bubbling because it is more user-centric whereas error_bubbling was just technical.

+1 for second Bernhard proposition #9994 (comment)
And errors_scope as other possible alternative

This would be a great change! I like error_scope too fwiw.

👍 for the parent|self|root

+1 for errors_scope or display_errors_scope with possible values self | parent | root.

@webmozart Have there been any updates on this?

👍 for error_location with self | parent | root

@webmozart status bump? Is this issue still relevant or stale?

If the value would be an array, you could choose multiple error locations:

error_location => ['self','parent']

See #36729

Thank you for this issue.
There has not been a lot of activity here for a while. Has this been resolved?

Let's close this old issue as nobody cared enough to implement this feature.