Alertmanager UI is not opening using IPV6 literal

What did you do?
Open the alertmanager UI using the ipv6 literal. http://[x❌x::x]:9093/. It works if we pass hostname instead of IPV6 literal.

What did you expect to see?
Alertmanager UI
What did you see instead? Under which circumstances?
Attached error is what is observed in the Google developer tool console.
Environment
Linux vm-xxx-fpm-cpro 3.10.0-957.12.2.el7.x86_64 #1 SMP Fri Apr 19 21:09:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

• System information:

  insert output of uname -srm here
  Linux 3.10.0-957.12.2.el7.x86_64 x86_64

• Alertmanager version:

  insert output of alertmanager --version here (repeat for each alertmanager
  version in your cluster, if relevant to the issue)
  0.20.0

• Prometheus version:

  insert output of prometheus --version here (repeat for each prometheus
  version in your cluster, if relevant to the issue)

• Alertmanager configuration file:

insert configuration here

• Prometheus configuration file:

insert configuration here (if relevant to the issue)

• Logs:

insert Prometheus and Alertmanager logs relevant to the issue here

Following is the google groups thread where this was discussed. https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/prometheus-users/e0NbZX6oDpo/ls76u_hnBgAJ

Suspecting this issue due to 3rd party component Elm/Url. https://github.com/elm/url/issues/12.

Reproduce the failure by opening http://[x❌x::x]:9093/ in a browser and compare it with hostname access. Read the linked Elm/Url issue and the referenced Google Groups discussion for the reported console error and possible scope. Done means the Alertmanager UI opens when accessed through an IPv6 literal.