I'm not sure why we currently have the marquee effect for the page URL in the overlay ATM. My suspicion is that it has something to do with seeing the entire URL. But I think the user has more context to what they're sharing by way of the interactions leading up to this screen. I don't think this is necessary, especially with the full page screenshot in the back. In some way's, it seems to me like a moving URL is also not the best way to improve issues of legibility either. It's pretty distracting, and inconsistent with the rest of our visual style. For simplicity, I'd suggest removing the effect and truncating the URL to show that the link the user see's has more to it. I think that's all that's necessary at this point of the UX. Combined with the page title, I think this works better together.

The motivation was mostly because it made the popups at the time pretty unhelpful. I was testing it out with Reddit links, so you ended up with a popup like: title: "Reddit: The front page of the inter..." URL: "http://www.reddit.com/r/aww/..." Both of which fairly comprehensively failed to express what was being shared.

(In reply to Chris Kitching [:ckitching] from comment #1) > The motivation was mostly because it made the popups at the time pretty > unhelpful. > > I was testing it out with Reddit links, so you ended up with a popup like: > > title: "Reddit: The front page of the inter..." > URL: "http://www.reddit.com/r/aww/..." > > Both of which fairly comprehensively failed to express what was being shared. Don't you have that context and knowledge (of what website you're viewing) before you get to this step? A lot of that information seems redundant here. Plus, at 300 dp max width, with the tab still in the background, I think we can show enough of a hint to help remind the user what they just saw moments ago.

Since the Reddit app I was using had the property that its share buttons were quite fiddly, it seemed plausible that someone would accidentally hit the one for the adjacent link instead of what they wanted. This is presumably the purpose of displaying this information here: to confirm to the user exactly what they are about to share (so they don't end up accidentally posting an entirely unrelated cat picture to their Facebook, which could of course be catastrophic).

(In reply to Chris Kitching [:ckitching] from comment #3) > Since the Reddit app I was using had the property that its share buttons > were quite fiddly, it seemed plausible that someone would accidentally hit > the one for the adjacent link instead of what they wanted. That's fair. But I think our users could be coming from any applications. Plus, they can still see what's behind the "sheet" here. They could even dismiss it to make sure if it was really that important, I doubt a marquee URL is enough confirmation. > This is presumably the purpose of displaying this information here: to > confirm to the user exactly what they are about to share (so they don't end > up accidentally posting an entirely unrelated cat picture to their Facebook, > which could of course be catastrophic). But we can only Bookmark, Add to RL, or Send to a device from this screen. All of which are relatively low cost to undo as well.

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.