Right now, CHBrowserListener is a formal protocol, leading to silly things like KeychainService having 12 empty callback functions, and having to find and update every listener any time any one of them ends up needing to know about a new event. It seems like it would be saner for it to be an informal protocol, and have the dispatcher do a respondsToSelector: check. Simon, pink, is there any reason we wouldn't want to do this?
Fine by me.
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.