Closed Bug 1520748 Opened 6 years ago Closed 4 years ago

history entry without port

Categories

(Firefox for Android Graveyard :: General, enhancement, P5)

Product:
Firefox for Android Graveyard
Component:
General
Version:
Firefox 64
Platform:
ARM
Android
Type:
enhancement

Tracking

(firefox66 wontfix, firefox67 affected)

Status:
RESOLVED INCOMPLETE
Tracking Flags:
Tracking Status
firefox66 --- wontfix
firefox67 --- affected

People

(Reporter: s.kolodziejczak95, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Steps to reproduce:

I'm very often visit website with custom port. This page has been added to popular tab.

Actual results:

The entry is without port. Same with the search hints: no port included.

Expected results:

I expect that browser will include port in entry history.

Thanks for your report!
Moving this to enhancement.

Severity: normal → enhancement
OS: Unspecified → Android
Hardware: Unspecified → ARM

Pretty sure I've seen this in a similar bug report.

status-firefox66: --- → wontfix
status-firefox67: --- → affected
Keywords: dupeme

Bug 764062 is likely what I was thinking of.
Mak, do you recall if the work in 764062 supported Fennec?

Flags: needinfo?(mak77)
See Also: → https://bugzilla.mozilla.org/show_bug.cgi?id=764062

Firefox and Firefox for Android use completely different awesomebar implementations.

Ah, ok. I may be wrong and this might not have ever worked on Fennec.

Flags: needinfo?(mak77)

Yeah, there is a whole daisy-chain of bugs basically reporting the same error: that this autocompletion feature seems to have been designed by someone who never heard of port number nor realised that it is not an option extra but an essential part of the protocol when specifying a URL.

What is even more annoying is that not only will it fail to connect but it with then start trying to connect to something stupid like localhost.com so cannnot just add the :port you have to send you to google.com with a dumb search, meaning more effort to correct.

This has been flagged for at least 6 or 7 years now.

Needs fixing.

Marking P4 per triage discussion.

Priority: -- → P4

P4 is not a suggested priority it should be p3 or p5. https://mozilla.github.io/bug-handling/triage-bugzilla

Priority: P4 → P5

P5 Will not fix, but will accept a patch

Cool, so it has taken 6 years to get this functional bug and lack of respect of the spec of what constitutes a URL as far as "will not fix".

Outstanding.

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.
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.