Comment 17 for bug 1466290

It would be confusing because people will think they are supported when they are not, which is no different than the current situation with the existing webkit (which we must not carry forward).

Ultimately (and I've said this before-- indeed it is part of the MIR team review process), I think Gnome should move to a supportable webengine. Oxide is designed specifically for this: the chromium content api updates for security, performance and web compatibility but the APIs exposed to apps remain stable. Oxide is designed to have an arbitrary number of bindings, and gtk bindings would be most welcome and benefit everyone. Perhaps webkitgtk APIs can map to oxide in ways to minimize transition pain, perhaps not. If this is something people are interested in (and I hope they are! :), please participate on the mailing list at https://launchpad.net/~oxide-developers.

Of course, this doesn't help for 15.10. I see only a few options currently:
 1. don't update to 3.16
 2. update to 3.16 but don't build the parts that need webkit so it can stay in main
 3. update to 3.16 but demote to main
 4. do a combination of 3 and 4: have 2 source packages, one that is in main but doesn't build with webkit and one that is in universe that does

Any of the above will satisfy/obviate this MIR from a security team standpoint, so unsubscribing us for now. Please feel free to resubscribe as needed.