SecureHeaders in general since the ZA patch have had all kinds of issues. My own addons that work in both classic vanilla and retail have several issues since this latest tbc patch. First it was with SecureAuraHeaderTemplate, which got some fixes, but still can show moments of really strange bugs with some buffs not disappearing. Oddly this mainly happens while leveling.
The more puzzling one is the SecureGroupHeaderTemplate. It runs on login without any errors, but it will not actually spawn any frames until you /reload once. Again, no issues on any other version of WoW. I’m spawning raid frames through oUF in this instance, but even building a demo addon and writing the headers by hand doesn’t works correctly.
Will we see any documentation on this or patches? Trying to debug this in this patch is a black box.
To add to this, the debugtrace() inside of the frame spawn style functions goes through SecureHeader->RestrictedExecution->RestrictedFrames and seems to be based on the state-visibility attribute not evaluating correctly on login.
‘raid,party,solo’ works/worked before, but only works now upon /reload.
Bump, still a major issue with no documentation as to what/if there is a fix.
If a WoW dev sees this - it looks like this happens because UnitGroupRolesAssigned is not defined or something on UI load, but then is defined after and if it has to overwrite anything it will taint.
For instance this loading with an addon will break secureheader
UnitGroupRolesAssigned = UnitGroupRolesAssigned or noop
Even though it shouldn’t (and doesn’t on retail) reach the noop function if the function is defined by wow.