The OP doesn’t seem to be referencing the API change of GetMouseFocus to GetMouseFoci, but rather something about using /click for macros using ActionButton1, etc.
Though, since it was also stated that:
this is possibly rather unhelpful information for troubleshooting assistance.
What Gnàrr is referencing also appears to be unrelated to any /click functionality which is the topic of this thread. But is related to the API change…
Would of course work if using the updated API call to GetMouseFoci instead, i.e.
/script print(GetMouseFoci()[1]:GetName())
With regards to /click, I’m unfamiliar with it, but a quick test shows that you can make a macro like /click ActionButton1 to click whatever is bound to your Action Bar button1, etc. and that that seems to work with some things like Cooking, or a mount, etc. but not with running another script (macro).
As an example (I don’t know why you might want to do this, but I was trying to think of a situation where you might), you could do something like having Fishing bound to ActionButton1 and a mount to ActionButton2. You will cast fishing if you have no mouseover, and cast your mount if you have a mouseover target:
/click [target=mouseover,exists] ActionButton1; ActionButton2
This won’t work if instead of dragging fishing from my spellbook to my action bar, I make a macro and put it there instead:
/cast Fishing
It does appear that the change to /click is noted for 11.0.2 in whatever Wiki this is that is documenting them: https://warcraft.wiki.gg/wiki/Patch_11.0.2/API_changes
“All macros (real and macrotext-based) can no longer chain macros. One macro cannot /click a button that would execute another macro”
