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): |
https://gitlab.com/eyeo/adblockplus/adblockpluschrome/merge_requests/58 |
||
Description (last modified by geo)
Environment
ABP 0.9.13 & APB dev 0.9.13.2260
Windows 10, EdgeHTML 18.17763
How to reproduce
- Got to https://togetheroo.com/playspace/
- Join the same playspace as above but from a different device
- Add the following filter $webrtc,domain=togetheroo.com to ABP on the first device
- 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
comment:4 Changed on 04/03/2019 at 08:39:42 PM by abpbot
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
Note: See
TracTickets for help on using
tickets.
A commit referencing this issue has landed:
Issue 7329 - Assign to textContent when injecting scripts on Edge