Opened 13 months ago

Closed 12 months ago

Last modified 10 months ago

#7329 closed defect (fixed)

WebRTC connections are not blocked on Edge

Reported by: geo Assignee: geo
Priority: P3 Milestone: Adblock-Plus-for-Chrome-Opera-Firefox-next
Module: Platform Keywords:
Cc: sebastian, kzar, Ross Blocked By:
Blocking: Platform: Edge
Ready: yes Confidential: no
Tester: Unknown Verified working: yes
Review URL(s):

Description (last modified by geo)


ABP 0.9.13 & APB dev
Windows 10, EdgeHTML 18.17763

How to reproduce

  1. Got to
  2. Join the same playspace as above but from a different device
  3. Add the following filter $webrtc, to ABP on the first device
  4. Refresh the page

Observed behaviour

Nothing happens, the connections are not blocked.

Expected behaviour

The connections are blocked just like on Chrome (you can confirm that on the second device).

Change History (6)

comment:1 Changed 13 months ago by sebastian

  • Priority changed from Unknown to P3
  • Ready set

comment:2 Changed 13 months ago by geo

  • Owner set to geo

comment:3 Changed 12 months ago by geo

  • Description modified (diff)
  • Review URL(s) modified (diff)

comment:4 Changed 12 months ago by abpbot

A commit referencing this issue has landed:
Issue 7329 - Assign to textContent when injecting scripts on Edge

comment:5 Changed 12 months ago by geo

  • Milestone set to Adblock-Plus-for-Chrome-Opera-Firefox-next
  • Resolution set to fixed
  • Status changed from new to closed

comment:6 Changed 10 months ago by ukacar

  • Verified working set
Note: See TracTickets for help on using tickets.