Closed Bug 1753454 Opened 2 years ago Closed 10 days ago

Event retargeting breaks UniConsent cookie consent toggles

Categories

(Core :: Layout, defect)

defect

Tracking

()

RESOLVED WORKSFORME
Webcompat Priority P3

People

(Reporter: denschub, Unassigned)

References

(Blocks 1 open bug, )

Details

(Keywords: webcompat:site-wait)

In a recent WebCompat bug, we discovered another issue related to event retargeting.

On this site using the UniConsent-powered cookie consent dialog, if you select "Manage Options", you cannot toggle anything there.

The touch events get redirected from the visual-slider-thingie to the text boxes next to it, which unfortunately have role="button" set as they also have interactive functionality...

Dennis, can you please attach a simple case here? On my environment, I can't see the privacy dialog unfortunately.

Severity: -- → S3
Flags: needinfo?(dschubert)
Webcompat Priority: --- → ?

Still investigating this, but it's not affecting anything else. I'll set this as a WebCompat P3 for now, just to get this off our queue.

Webcompat Priority: ? → P3

If it looks like I dropped the ball on this one - than that's because that's exactly what happened here. Sorry for that. I just re-tested on the site, which now looks slightly different, but is still using the UniConsent banner. The issue still reproduces there, but it's worth nothing that this does not reproduce on other sites using the same UniConsent framework.

Oddly enough, I completely fail to build a testcase here. The consent banner is loaded in an iFrame, and if I load the source from that frame as-is, the buttons work fine. Even if I build an iFrame myself with the same dimensions and placement, it still works. There's something incredibly odd about that specific site that I somehow fail to find.

I've sent an email to both UniConsent and someone who hopefully works at that site. That's probably more efficient here, given that this seems to be site-specific.

Flags: needinfo?(dschubert)

The site in question works now just fine in my tests. I can't tell if we changes some re-targeting logic or if the site changed, but since we have no isolated testcase for this specific instance (I tried, but didn't succeed at the time), I'll close this as worksforme.

Status: NEW → RESOLVED
Closed: 10 days ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.