Firefox does not allow navigating for links with target set to parent for applications inside an iframe
Categories
(Core :: DOM: Navigation, defect, P2)
Tracking
()
People
(Reporter: alicja.majewska, Unassigned)
References
Details
Steps to reproduce:
Clicking on links inside application run within an iframe with target set to parent (Jira Cloud plugin) does not lead to changing the url (works well on right clicking and opening the link in a new tab).
I use Firefox 94.0.2 for MacOS, but it's hard to reproduce the issue, seems to happen to random browsers.
There are more users (and apps) experiencing the same problem, discussion on Jira Cloud Community:
https://community.developer.atlassian.com/t/in-firefox-redirect-and-links-do-not-work-from-plugin-iframe/53937
Creating a new Firefox Profile and switching to that solves the issue.
Actual results:
The links does not react on clicking - no navigation it triggered (onClick event listeners are triggered correctly)
Expected results:
The navigation should be triggered.
|
||
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::DOM: Navigation' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
||
Comment 2•4 years ago
|
||
This might be the same issue as bug 1744321.
|
|
||
Comment 3•4 years ago
|
||
(In reply to alicja.majewska from comment #0)
Creating a new Firefox Profile and switching to that solves the issue.
Maybe because the fission is not enabled on the new profile, could you check if fission.autostart is set to true in about:config when you experience this issue and test again with fission.autostart = false (Note that you would need to restart Firefox after flipping the value)
|
Reporter | |
Comment 4•4 years ago
|
||
Hey, I just tried that and it worked a charm 🥳
Thanks for help!
Can you see any side effects of changing this setting in existing profiles?
Should false be a default value or is it just toggling a feature flag to disable some functionality that has a bug?
Do you consider it a bug and if so, will there be some fix from your side to make sure that this setting is false by default for existing profiles?
Can we inform our users about this workaround?
When can we expect this issue to be fixed?
|
|
||
Comment 5•4 years ago
|
||
It is a bug, STR in comment#0 should work whatever fission is enabled or not.
There is a patch in bug 1744321, it should fix this as well.
|
||
Comment 6•4 years ago
|
||
Aligning Priority/Severity of bug 1744321. Thank you, edgar!
|
|
||
Comment 7•4 years ago
|
||
Per comment 5, this should be NEW.
|
|
||
Comment 8•3 years ago
|
||
Hi alicja, could you try the latest Nightly (with fission.autostart set to true)? bug 1744321 should also fix this case. Thanks!
|
|
Reporter | |
Comment 9•3 years ago
|
||
(In reply to Edgar Chen [:edgar] from comment #8)
Hi alicja, could you try the latest Nightly (with
fission.autostartset to true)? bug 1744321 should also fix this case. Thanks!
Hi, I just checked, it's working fine, well done! 🥳
|
|
||
Comment 10•3 years ago
|
||
Thanks for your help to verify. :)
Description
•