The Blueprint class triggers fake and faked events against Frame instances inconsistently with the way that other Frame methods trigger events.
The work around currently is to use a classmethod (to receive the sender) over using a staticmethod. Fixing this issue will break backwards compatibility so I look into a solution that can cater for both in the short term (it's a pretty simple fix to upgrade, however, switch classmethods to staticmethods).
Note This bug doesn't not affect documented functionality.