Thanks, Kaity!
I'm not that surprised by the context stuff. There's a lot going on in that top toolbar, and on a big tablet screen, that area is likely to be quite far away from (and thus totally contextually detached from) the link/reference the user has just tapped.
I'm not convinced, though, that simply adding a more prominent call to action in the toolbar and/or highlighting the target will be enough to overcome the usability hurdle; to me, this requires a rethink of the location/shape of the dialog, testing a version that's a floating tooltip like on desktop, etc. I'm CC-ing James because we should work out whose purvey this now falls under. We're still kinda muddling our way through our collaboration ;) but now that tablet VE has gone into stable, we should start thinking more intentionally about the ownership and prioritization of things like this. Specifically:
* Who owns the product specification, design, and engineering work of iterations on existing mobile VE features and new features?
* Who prioritizes this work against the bigger backlog of VE features and bugs?
It seems to me that one product owner and one team should be responsible for both of these points – otherwise we might get into a weird situation where one team spends a lot of time designing something and then it doesn't go live because it gets deprioritized by the other team, or where new VE features are designed with one specific platform in mind and the other platform has to play catchup to work right.
James, going forward, I see work like this (e.g., refining and testing the mobile tablet context menu workflow) as an Editing team thing – does that sound right to you?
Of course, realistically, the Mobile Web team still has a lot of the domain expertise in mobile devices/browsers and will need to continue helping to iron out any mobile-specific issues, review and test stuff, etc. But as far as who makes the call on whether to iterate on this design versus build some new feature on VE, and who does the majority of the architectural legwork to make that happen, the ball seems to be more in the Editing team's court at this point. James (and anybody else who's been involved in the MFE-VE collaboration, of course), lemme know what your thinking is on all this.