1222410 - Paste and go - trim should remove leading and following characters if they're invisible

Status: RESOLVED INACTIVE

(Firefox for Android Graveyard :: General, defect)

Description

[Djfe]

User Agent: Mozilla/5.0 (Android 5.1.1; Tablet; rv:43.0) Gecko/43.0 Firefox/43.0
Build ID: 20151103024436

Steps to reproduce:

I copied this url from a text document:
"http://mpeg.chiariglione.org/standards/mpeg-2/systems"
Using the ES File Explorer as well as the Dropbox editor
The text file was a text file in my Dropbox.
Anyways, I pasted the URL into the URL bar of Firefox and wanted it to open the Web page.


Actual results:

Firefox misinterpreted as text and started a Google search with that url instead of opening it directly.
Other links I have tested following the same procedure worked fine (Wikipedia for example)


Expected results:

Firefox should have loaded the URL instead of Google

Comment 1

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

Did you copy this url with the quotes? I can reproduce if the leading quote is included, otherwise I cannot.

Comment 2

[Kevin Brosnan [Ex-Mozilla]]

I would believe a non-printing character or leading space could result in the search behavior as well. Though ideally we would discard a leading space, carriage return, line feed or other non printing character.

Comment 3

[Djfe]

No I only added the quotes in my post.

I now had time to view the file on pc:
http://i.imgur.com/CMh2OEP.png
the first link has three invisible characters at the beginning

do you think firefox should remove those from the urlbar field (atleast from the beginning and the end)?

Now that I know it's not a general issue I wouldn't mind, if it stays like it is
but I still don't think it is a desired behaviour

Comment 4

[Djfe]

Attachment: Transportstream.txt

so you can see yourself
I only copied the first line and pasted it into Firefox's addressbar

Comment 5

[Firefox Bug Husbandry Bot]

Closing per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195

Contact :susheel if you think this bug should be re-opened