Thanks. I really sympathize with all, and hope the summary/categorization helps accelerate a solution somehow.
I decided to take (what turned out to be a full overtime day) and try it because there were some who periodically did that in a several-years'-running discussion about HP's and others' (NON) driver support for switchable graphics and multifunction wireless/bluetooth cards on the TM2-t convertible laptop, and another on HP's decision to advertise a touchscreen convertible TX-2 (old-timers, look that moniker up) as a graphics machine even though they implemented a non-mainstream, non-Wacom digitizer that would only support a Corel graphics program, not Photoshop. Graphics students were livid. Parents were livid when the laptop/tablet they spent hard-earned cash on was too hot to hold in your lap if the CPU was busy. :-)
In both those situations it was a few users who digested, tested, and summarized/updated. I was so so grateful, even though the TM2 (with Wacom digitizer( was the solution for the TX2). Both had other issues. For instance, the TX2 was a convertible tablet that used an AMD desktop chip that got so hot when it ran Microsoft's new 3-D pond animation that we students joked about getting a small fan and a tube to use the output from the cooling fan to warm our toes (on the Bainbridge Island ferry route). Eventually many TX2s stopped working with a blink code that indicated the CPU was toast. HP had people doing low-level, data-destructive fixes as Apple is now doing. But one user posted a YouTube video of how he discovered that the heat had cooked the large glob of paste between the CPU and its (huge copper) heat sink apart. Having taken mine apart based on his video and related documentation when it failed, I re-did the paste and got it working again for awhile.
I'm really concerned about this 9.3 communication pattern. Feels like the word isn't getting to the "senior" troubleshooters. They need good word. I have been QA, and I know it is hard to convey what the dev needs in language that helps them reproduce and diagnose.
Some of the federal government has moved to iPhone 5S from Blackberry. At least one IT subset has evidently tested and pushed out instructions for their user group to have the updated iOS installed by this Friday (ironically April Fools Day). And take a look at the big summit that is in DC this weekend to understand the impact if that IT group is unaware of this potential issue. So I hope that IT group has the problem sorted out and has pushed a "good" version of iOS. But if Apple missed this, and that IT group hasn't quietly taken care of it, then this is a bad weekend for that IT to unintentionally mess with their user group's iPhones.
That group would not be ones that would install apps like Booking.com, it's true (or any app - IT would lock that down tight),
but I see notes in reply - in comments to the posts at http://9to5mac.com/2016/03/29/apple-ios-9-crashing-bugs-when-tapping-links-fix-s oftware-update/ for example - from people who insist that they *never installed Booking.com* and yet have the Safarfi/email issues.
If it was an easy mistake for Booking.com to blithely supersize their link manifest, then there are probably other similar innocent mistakes in other apps as well.
<Link Edited by Host>