<a> href with javascript behavior differs between modern browsers
Categories
(Core :: DOM: Navigation, defect, P3)
Tracking
()
Webcompat Priority | P2 |
People
(Reporter: alice0775, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: parity-chrome, parity-edge)
Attachments
(1 file)
305 bytes,
text/html
|
Details |
<a> href with javascript behavior differs between modern browsers * Firefox55.02(Nightly57.0a1), IE11: string, number, boolean and object of href may navigate to the value * Edge40.15063.0.0, Chrome62.0.3175.3: string of href may navigate to the value. however, number, boolean and object of href do not navigate to the value Reproducible: always Steps To Reproduce: 1. Open attached html 2. Click links Expected Results: all browser should have same behavior
Comment 1•7 years ago
|
||
Anne, what's the expected behaviour here from the spec point of view? It seems to me this is with rather low priority as javascript: pseudo protocol is discouraged ... Did I miss something?
Comment 2•7 years ago
|
||
This is https://github.com/whatwg/html/issues/1896 I think. Bug 1326162 also seems related (this might even be a duplicate). javascript: URLs are indeed discouraged, but they're also a source of interoperability issues due to all the subtle behavioral differences. :/
Comment 4•6 years ago
|
||
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Updated•3 years ago
|
Comment 5•3 years ago
|
||
This is causing problems in the wild as this page of a major parking company in Sweden now no longer works in Firefox:
https://service.apcoa.se/Account/Login/
Clicking "Logga in med APCOA konto" works in Chrome, but not in Firefox.
The vendor is entirely unsympathetic and just replies to bug reports with "Use Chrome".
Updated•3 years ago
|
Comment 6•2 years ago
|
||
The webcompat team will attempt outreach for APCOA (dennis), but the issue still exists.
It doesn't seem to have been discussed further on whatwg. (last comment 2018)
https://github.com/whatwg/html/issues/1896
Updated•2 years ago
|
Comment 7•1 year ago
|
||
I re-pinged them, but I'm not too hopeful about them changing their site.
Comment 8•1 year ago
|
||
Bumping to webcompat-priority to P2 based on a second real-world breakage.
Updated•11 months ago
|
Updated•7 months ago
|
Updated•6 months ago
|
Updated•3 months ago
|
If we have multiple confirmed reproductions such as mine at 131350 why is this marked as unconfirmed and unfixed after 7 years?
Comment 10•3 months ago
|
||
(In reply to Derek from comment #9)
why is this marked as unconfirmed and unfixed after 7 years?
Because nobody has built a fix yet.
Comment hidden (advocacy) |
Description
•