Just recently, we noticed some of our webpage API tests were failing with 0.4 where they passed successfully in 0.3. Worried that we broke our backwards compatibility policy, John investigated and noticed that we exposed some properties as read-write when they shouldn’t have been.

So 0.4 is now doing the right thing (not the write thing, har har har) by not allowing remote webpages to set certain properties on mediaItems that were previously settable. On the plus side, John found a few things that *weren’t* accessible, and fixed those (so now you can access and modify rating and mediaListName, yay!)

Anyway, apologies if you were relying on the 0.3 behaviour of being able to set properties you weren’t supposed to - but in the interest of making Songbird secure and trustworthy - we’ve now locked those properties down.