Hi Mr JonRBloom,
As per this thread and perhaps other posts related to the issue, the problem one would consider quite simple is not new.
https://forums.autodesk.com/t5/fusion-360-api-and-scripts/jointorigin-isvisible/td-p/9306477
I don't know how you are familiar with API and its development (or changes) over the years.
Let's look at this particular trivial case of visibility of an icon marking visibility of browser members (including jointOrigin).
If you study API documentation, you will find that this property can be set or/and get using two properties isVisible and isLightBulbOn. On top, there are also (added not long time ago group properties like for example isJointsFolderLightBulbOn.
It seems that during the software development life, there were two competing parties in not necessarily well-synchronized teams.
One party I would call Visi_Cratic and other GE_Cratic (short for LightBulbOn_Cratic).
There was also the vicious battle about the colour of the respective icon.
isVisible parameter is sometime settable & gettable and, on other occasions, only gettable. It is hard to devise the pattern here (perhaps the research of the phenomena could lead to a high degree in Methods Of Software Development Department at Esteemed University)
isLightBulbOn seems to be set/get/able.
So about your concern: 'If it is still working today, I would be wary of relying on this.'
I agree I can't predict the outcome when I pick my nose. Predicting what will happen when F360 digs into the problem is much, much harder, perhaps impossible.
Regards
MichaelT
PS.
As jointOrigin.isVisible = True/False seems to work now, it is still not documented. (checked couple days ago)
MichaelT