It's about handing over control of the feedback to the client. Currently the client waits on the JS title-change event which only happens when the purchase is complete/failed - we'd like that event to instead happen when the purchase is initialised, and enabling the client to use the API to check the status itself and update the UI. So yes, bug 649715 sounds like a different way of achieving a similar result, afaics.
It's about handing over control of the feedback to the client. Currently the client waits on the JS title-change event which only happens when the purchase is complete/failed - we'd like that event to instead happen when the purchase is initialised, and enabling the client to use the API to check the status itself and update the UI. So yes, bug 649715 sounds like a different way of achieving a similar result, afaics.