Extracting the whole snap-decision functionality into a separate dialog service, which would be easier to isolate, feels like a too large effort for rtm, considering the other fires we've to put out still.
Admittedly I've not done a thorough analysis of the expected effort yet. But it will require major changes in lp:unity-notifications, lp:unity8, all the numerous snap-decision using apps, the new dialog-service itself and of course new Design guidelines for how such a service would fit in the current notification-concept. Before such an effort should be started the exact functional requirements need to be ironed out, so we avoid having to fix things up as we implement it... like it happened with snap-decision notifications, which got loaded with more and more typical dialog-like features as we went along. All of the above will additionally also require new qml/AP-tests and of course user- and integration-testing. That's all I can say in a short comment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1306769 Title: pinlock snap decision potentially allows malicious app to gain access to user PIN and Passcode To manage notifications about this bug go to: https://bugs.launchpad.net/unity-notifications/+bug/1306769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
