Opened on 03/05/2019 at 09:50:04 PM

Closed on 04/03/2019 at 10:37:11 PM

Last modified on 06/18/2019 at 10:19:41 AM

#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).

Attachments (0)

Change History (6)

comment:1 Changed on 03/05/2019 at 09:55:33 PM by sebastian

  • Priority changed from Unknown to P3
  • Ready set

comment:2 Changed on 03/07/2019 at 02:52:15 PM by geo

  • Owner set to geo

comment:3 Changed on 04/03/2019 at 12:54:44 PM by geo

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

comment:4 Changed on 04/03/2019 at 08:39:42 PM by abpbot

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

comment:5 Changed on 04/03/2019 at 10:37:11 PM 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 on 06/18/2019 at 10:19:41 AM by ukacar

  • Verified working set

Add Comment

Modify Ticket

Change Properties
as closed .
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from geo.
Note: See TracTickets for help on using tickets.