Firefox no longer displays link preview for links with pseudo-element
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr140 | --- | unaffected |
| firefox-esr153 | --- | wontfix |
| firefox152 | --- | wontfix |
| firefox153 | --- | wontfix |
| firefox154 | --- | wontfix |
| firefox155 | --- | wontfix |
| firefox156 | --- | wontfix |
| firefox157 | --- | verified |
| firefox158 | --- | verified |
People
(Reporter: soeren.hentzschel, Assigned: mozilla.7fhrv)
References
(Regression)
Details
(Keywords: regression)
Crash Data
Attachments
(1 external file)
Firefox no longer displays a link preview for links with a pseudo-element. This poses a security risk of sorts, as it makes phishing much easier when you can no longer check the link’s destination before clicking on it.
STR:
- Open https://www.camp-firefox.de/artikel/1228-mozilla-ver%C3%B6ffentlicht-umfangreiche-firefox-roadmap-f%C3%BCr-alle-plattformen/
- Move your mouse over an external link (red text with a "↗" after the text), like "Roadmap-Seite".
Actual:
No link preview. Once you set display: none to the a.externalURL::after, it works again.
Expected:
You see a link preview in the corner of the Firefox window.
Tested on macOS and Windows. According to mozregression, it's a regression from bug 2023374.
| Assignee | ||
Comment 1•4 months ago
|
||
It appears that CSS causes ClearFrameRefs.
This is the reproduction code:
<html><head>
<style>
a { display: inline; }
a::hover { display: inline-flex; }
</style>
</head><body>
<a href="https://example.com">foo</a>
</body></html>
| Assignee | ||
Comment 2•4 months ago
|
||
ClearFrameRefs unconditionally cleared the status bar even if the
content was still in the document (e.g. when a CSS change caused the
frame to be reframed).
Only clear the status bar if the content is no longer in the composed
document.
Regressed by: Bug 2023374
Updated•4 months ago
|
Updated•4 months ago
|
Updated•4 months ago
|
Comment 3•3 months ago
|
||
Set release status flags based on info from the regressing bug 2023374
| Reporter | ||
Comment 4•3 months ago
|
||
Can we please make some progress on this? If the link destination isn't visible before the user clicks, it has security implications (increased risk of phishing).
| Reporter | ||
Comment 5•3 months ago
|
||
The author of the regression and the patch used to fix it appears to have been inactive for the past month. See comment #4 for why I think this is a bad regression that has been in the product since Firefox 151, and which I would like to see fixed as soon as possible.
| Assignee | ||
Comment 6•3 months ago
|
||
(In reply to Sören Hentzschel from comment #5)
The author of the regression and the patch used to fix it appears to have been inactive for the past month. See comment #4 for why I think this is a bad regression that has been in the product since Firefox 151, and which I would like to see fixed as soon as possible.
Sorry, I'm the author, and rather than being inactive, I'm waiting for comment on phabricator.
https://phabricator.services.mozilla.com/D310891#10787728
Updated•3 months ago
|
| Reporter | ||
Comment 8•3 months ago
•
|
||
Sorry, I'm the author, and rather than being inactive, I'm waiting for comment on phabricator.
After re-reading my comment, I think it sounds more accusatory than I intended. Sorry for that! I was just going by the Bugzilla activity and didn't check the Phabricator revision for comments. Thanks for working on this!
Updated•3 months ago
|
Updated•3 months ago
|
Comment 10•2 months ago
|
||
Comment 11•2 months ago
|
||
Reverted this because it was causing bp-nu bustages.
Comment 12•2 months ago
|
||
There is an r+ patch which didn't land and no activity in this bug for 1 week.
:mozilla.7fhrv, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit BugBot documentation.
Comment 13•2 months ago
|
||
Comment 14•2 months ago
|
||
| bugherder | ||
Updated•2 months ago
|
Comment 16•2 months ago
|
||
Copying crash signatures from duplicate bugs.
Updated•2 months ago
|
Updated•2 months ago
|
Comment 17•2 months ago
•
|
||
I was able to reproduce the issue on Win11x64 using Firefox build 155.0.
Verified as fixed on Win11x64 using Firefox builds 158.0a1 and 157.0b1. Pending verification on esr 153 if uplifted.
Updated•27 days ago
|
Updated•27 days ago
|
Description
•