I realize that this bug is about libunity-webapps and not about the browser extensions, but this bit concerns me: "Part of the WebApps technology, integration scripts that expand the "scope" of a given website (URL) are being "run" along with a given webpage by dedicated extensions (for chromium and firefox)."
What guarantees do we have that the extension won't break in the next browser security update? Are there tests (preferably automated) that can be run to verify that the new browser works with the old extension? Who will be doing this testing? Who is maintaining the browser extension code in stable releases? I have quite a few concerns here because these updates come every 3-6 weeks and we don't want to have to decide between providing a timely, important security update to our users and breaking the browser extension (and therefore webapps). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043461 Title: [FFE] Update WebApps to support dpkg distribution mechanism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1043461/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
