That was my first thought as well. When I learned the PopupMenu won’t keep the PopupMenu::Options, I refactored to use only the targetComponent to limit the information exposed.
TBH. later I learned, that the MenuWindow stores a copy of the PopupMenu::Options, but I decided against changing it back to limit the exposed information and maybe future Components might use the same approach, which are not a PopupMenu.
But that is totally up for discussion.
Yes, that is possible. But if you look, I switched more than 10 times the findColour to use the targetComponent if available, so DRY justifies a second method IMHO.
I could have settled for a default argument, but that would impose a runtime cost on all other occasions, and only a few LookAndFeelMethods actually need to deflect to a targetComponent (so far only PopupMenu).