NavParser incorrectly detects URLs with a port but without a scheme as a Search (or app launch) rather than a Navigate

In progress Issue #14671414

Details

Author
Wattana S.
Created
Nov 15, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
41.16299
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

When I re-type a HTTP address with non-standard port, Edge will not load page correctly.

Step to reproduce:

  1. Go to HTTP site with non 80 port. sample
  2. Click to begin edit the address and press enter.
  3. Edge will display the dialog that ask the user to find an app to open [hostname].

Related issue:
http prefix is required when specifying the port in the address bar (mobile)

Attachments

1 attachment

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

    Changed Assigned To to “Scott L.”

    Changed Assigned To to “Venkat K.”

    Changed Assigned To from “Venkat K.” to “Dylan K.”

    Changed Assigned To from “Dylan K.” to “Siddharth R.”

    Changed Status to “Confirmed”

    Changed Assigned To from “Siddharth R.” to “Dylan K.”

    Changed Title from “Protocol (http://) removing in address bar cause when re-type/edit URL” to “NavParser incorrectly detects URLs with a port but without a scheme as a Search rather than a Navigate”

    Changed Title from “NavParser incorrectly detects URLs with a port but without a scheme as a Search rather than a Navigate” to “NavParser incorrectly detects URLs with a port but without a scheme as a Search (or app launch) rather than a Navigate”

    Changed Status from “Confirmed” to “In progress”

  • Hello,

    Thank you for providing this information about the issue. We are presently tracking this issue as a duplicate of an existing internal bug report. We look forward to additional feedback you may have on how we can improve Microsoft Edge.

    Best Wishes,
    The MS Edge Team

You need to sign in to your Microsoft account to add a comment.

Sign in