Opened 11 months ago

Closed 3 months ago

#7174 closed defect (rejected)

Block element window is recreated if open when Edge is force closed

Reported by: Ross Assignee:
Priority: Unknown Milestone:
Module: Platform Keywords: closed-in-favor-of-gitlab
Cc: sebastian, kzar, geo, greiner Blocked By:
Blocking: Platform: Edge
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description (last modified by Ross)

Environment

ABP 0.9.11.2206
Edge 42.17134.1.0 / EdgeHTML 17.17134

How to reproduce

  1. Open a web page in Edge.
  2. Select [ABP Icon] > [Block element].
  3. Select any element.

Either:

4a. Force close Edge from the Task Manager. (Easiest)
4b. Accept a Windows update
4c. Restart the Windows machine.

Then:

  1. Open Edge again.

Observed behaviour

At Step 5 when Edge is reopened, the Block Element window also reopens on top of the main browser window and just contains the text "Loading". It also reopens it in a window with the full browser chrome, instead of just the address bar.

Expected behaviour

The Block Element window to not also reopen if the browser is reopened tabs/windows it had open when it was force closed. It does not occur in Chrome for example.

Attachments (1)

7174-blockelement-window.png (69.4 KB) - added by Ross 11 months ago.

Download all attachments as: .zip

Change History (5)

Changed 11 months ago by Ross

comment:1 Changed 11 months ago by Ross

  • Description modified (diff)

comment:2 Changed 11 months ago by Ross

This one is a bit strange but could be confusing if it happens to a user. I noticed this after Windows update decided to randomly reboot my machine and Edge reopened with a tiny Block element window on top of the (also tiny) main window.

comment:3 Changed 11 months ago by Ross

  • Cc greiner added

comment:4 Changed 3 months ago by sebastian

  • Keywords closed-in-favor-of-gitlab added
  • Resolution set to rejected
  • Status changed from new to closed

Sorry, but we switched to GitLab. If this issue is still relevant, please file it again in the new issue tracker.

Note: See TracTickets for help on using tickets.