Why<abbr>? According tohttps://developer.mozilla.org/en-US/docs/Web/HTML/Element/abbr it should me used for abbreviations and this is not the case here?<div> or<span> instead?

#12267 seems to be a better fix in my opinion.

@xabbuh, you've mixed my today's pull requests.#12267 fixes a problem giving a better solution (well, at least IMHO), while this PR adds some verbosity to the component.
@dunglas, I'm using the same pattern as used in the Events profiler tab: listener class names are wrapped with<abbr/>'s there, too.

@kix but in the events panel, this can be considered as an abbreviation, as the display text is the short class name, and the title is the FQCN. Here, you are mixing the name of the field and the class name of the form type being used, which are 2 different things

and giving the name of the form type would be better than its class name IMO anyway

I'm not sure this is needed. Hovering for 1-2 seconds is much slower than clicking the entry and checking the type on the right, no?

Well, technically, it's not clicking, it's the same<abbr/> there, as of Symfony 2.5.5:

@kix But you can see from your screenshot that the behavior is inconsistent now. Once you hover over thetype name, and then over theform name. Why (from a usability perspective) should hovering over these two different things show the same tooltip?

A bit more consistent now:

Whendata.type is empty, the tip and the type name are not displayed.

Better! What does the rest of you think? @symfony/deciders

👍

Thank you@kix.

@fabpot 👍! Thanks for merging!