Thanks, I believe you read correctly that we hide the TLD from the app's home screen, which also functions right now as its tab switcher. While the user is on the site, they can view the entire URL on the URL bar, starting from the schema. Tapping on the URL bar provides the ability to view, scroll, or change the entire URL. UX perhaps was thinking more about ease of use than potential exploits. Is this reasonable or should I add a patch to keep the eTLD on the tab switcher screen? I believe one may debug by enabling remote debugging via USB in the Settings.
Bug 1554984 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks, I believe you read correctly that we hide the TLD from the app's home screen, which also functions right now as its tab switcher. While the user is on the site, they can view the entire URL on the URL bar, starting from the schema. Tapping on the URL bar provides the ability to view, scroll, or change the entire URL. UX perhaps was thinking more about ease of use than potential exploits. Should I add a patch to keep the eTLD on the tab switcher screen? I believe one may debug by enabling remote debugging via USB in the Settings.
Thanks, I believe you read correctly that we hide the TLD from the app's home screen, which also functions right now as its tab switcher. While the user is on the site, they can view the entire URL on the URL bar, starting from the schema. Tapping on the URL bar provides the ability to view, scroll, or change the entire URL. UX perhaps was thinking more about ease of use than potential exploits. Should I add a patch to keep the eTLD on the tab switcher screen? I believe one may debug by enabling remote debugging via USB in Firefox Preview Settings.