Opened 19 months ago

Last modified 7 weeks ago

#5746 new defect

Notification not shown in Edge

Reported by: Ross Assignee:
Priority: Unknown Milestone:
Module: Unknown Keywords:
Cc: sebastian, oleksandr, geo Blocked By:
Blocking: Platform: Edge
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description

Environment

ABP 0.9.11.1849
Edge 40 / Windows 10

How to reproduce

  1. Setup Fiddler (or other proxy) to intercept requests from Edge.
  2. Setup Fiddler/proxy to respond to notification.adblockplus.org/notification.json with the test json below.
  3. Install ABP Edge build.
  4. Wait for notification request from extension.

Observed behaviour

Edge receives the notification but appears to do nothing with it.

Expected behaviour

The same notification.json sent to ABP Chrome (with target as adblockpluschrome) shows a "Test" notification as expected.

Example json

{ \"notifications\": [ { \"targets\": [{ \"extension\": \"adblockplusedge\" }], \"id\": \"1\", \"message\": { \"en-US\": \"Test\" }, \"severity\": \"normal\", \"title\": { \"en-US\": \"Test\" } } ], \"version\": \"201707281538\" }

Change History (2)

comment:1 Changed 19 months ago by Ross

To get Fiddler to respond add the following to OnBeforeResponse in Rules > Customize Rules:

if( oSession.PathAndQuery.Contains("notification.json"))
{

var res = "escapedjsonstringhere";
oSession.utilSetResponseBody(res);

}

comment:2 Changed 7 weeks ago by sebastian

  • Cc geo added

Also see #7347.

Last edited 7 weeks ago by sebastian (previous) (diff)
Note: See TracTickets for help on using tickets.