Community
Participate
Working Groups
3.0 RC3. In the content type manager we give clients the opportunity to register listeners for changes to content types. When changes are actually made to content types, the listeners are not being notified. This is due to a late-breaking API addition at the end of the 3.0 cycle.
Although bug 59899 depends on this one, I don't think this specific scenario has to be supported for 3.0.1. In the SDK, no UI is provided for changing content type preferences. Otherwise, this bug should me marked as targetting 3.0.1. DJ, thoughts?
Fixed. Released to the maintenance stream. Will close when released to HEAD.
Fix was co-written with DJ. Released to HEAD as well. Closing...