Open
Bug 1558274
Opened 6 years ago
Updated 2 years ago
Test-case where active content cannot be clicked in Firefox, but can in Chrome.
Categories
(Core :: Web Painting, defect, P2)
Core
Web Painting
Tracking
()
NEW
| Webcompat Priority | P3 |
People
(Reporter: twisniewski, Unassigned)
References
()
Details
Attachments
(1 file)
|
516 bytes,
text/html
|
Details |
In the attached test-case, the lone link cannot be clicked/tapped in Firefox, but can in Chrome. It seems the combination of applied CSS properties aren't interoperable in some way, but it's unclear to me what's going on.
This is breaking site interactivity on byggebolig.no's small-screen responsive breakpoint, as reported https://webcompat.com/issues/31337
|
||
Comment 1•6 years ago
|
||
The priority flag is not set for this bug.
:dbaron, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(dbaron)
|
||
Comment 2•6 years ago
|
||
Looks like hit-testing / paint-order stuff.
Component: Layout → Web Painting
Flags: needinfo?(dbaron)
Priority: -- → P2
|
||
Updated•5 years ago
|
|
|
||
Updated•5 years ago
|
|
||
Updated•4 years ago
|
Webcompat Priority: ? → P3
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•