bug.n icon indicating copy to clipboard operation
bug.n copied to clipboard

Automatically open the Edge browser

Open D1ngkai opened this issue 6 years ago • 8 comments

When I using bug.n,the Edge browser automatically open without any operation.How to fix it?Thx

D1ngkai avatar Dec 11 '18 14:12 D1ngkai

That would be Edge running in background; you may set this in the Windows 10 system settings under apps (? Sadly, I currently have no up-to-date version at hand.). The same would go with system settings itself, calculator and other Windows Store Apps.

Although not starting Edge itself, bug.n detects the Edge window at start and makes the hidden window visible. Oddly, Windows Store Apps use a window class called "ApplicationFrameWindow", which is handled differently.

You may also omit Edge from being managed by bug.n with the following Config.ini-line: Config_rule_#18=ApplicationFrameWindow;.*Edge;;0;0;0;0;1;0;

... or put it straight away to a different view (in this case view # 3) with the following Config.ini-line: Config_rule_#18=ApplicationFrameWindow;.*Edge;;1;0;4;0;1;0;

joten avatar Dec 13 '18 14:12 joten

This is also happening to me with Windows Settings, on the same intervals as Edge (they both appear at the same time, and only after the machine has been idle a while).

Config_rule=ApplicationFrameWindow;Settings;;1;0;4;0;1;0;

diiq avatar Dec 29 '18 14:12 diiq

It happens to me too. Edge Start is present on every workspace. I don't have any Config_rule regarding it. My workaround is to minimize it with #^m.

Also, I'm not sure if it's related or not, but sometimes Edge causes workspace to switch back. For example, I have Edge on the 2nd workspace, then I switch to 4th, in a second it switches back to the 2nd workspace. It happens too with Hyper-V Manager

Kukunin avatar Jan 21 '19 03:01 Kukunin

That seems to be Edge being reactivated from background after it has already been managed by bug.n; with Config_onActiveHiddenWnds=view (default configuration setting) the view is changed by bug.n to the view on which the window, which has been reactivated is associated with.

With the hotkey WinI pressed, when Edge is the active window, you may get the window's information with the currently used bug.n settings (managed, monitor, view etc.). Edge should be managed and on not more than one view. Has the window of "Hyper-V Manager" also the class "ApplicationFrameWindow"?

joten avatar Jan 25 '19 16:01 joten

Something weird happens to Edge. I've restarted bug.n without last session, Win I on Edge (Start window) gives

ID: 0xdb0948
class:	ApplicationFrameWindow
title:	Start ‎- Microsoft Edge
process:	ApplicationFrameHost.exe [11716]
style:	0x95CF0000
metrics:	x: -14, y: 30, width: 3227, height: 1783
tags:	1

Config_rule=ApplicationFrameWindow;Start ‎- Microsoft Edge;;1;1;1;0;1;0;maximize

The window is only on a single view, but Edge icon on the Task Bar is present on every view (it shows as a running app). After I close and start Edge again, it becomes unmanageable and presents on every view. Win I is:

ID: 0xdb0948
class:	ApplicationFrameWindow
title:	Start ‎- Microsoft Edge [hidden]
process:	ApplicationFrameHost.exe [11716]
style:	0x95CF0000
metrics:	x: -16, y: -16, width: 3232, height: 1732
tags:	--

Config_rule=ApplicationFrameWindow;Start ‎- Microsoft Edge;;0;;;;;1;maximize

My config doesn't contain anything related to Edge at all. I'm on the 125bcdd7dd49baf6af1829431d12cb1eefb436cd commit But that's not critical at all, since I (I don't know what changed), but Edge doesn't re-appear when closed.


As for the problem with focus stealing, it seems it appears to any privileged windows for me, such as Powershell terminal or VisualStudio Installer. Config_onActiveHiddenWnds=tag solves the issue, and the privileged window appears on the same view instead of switching to the previous view.

I assume I have to run bug.n with privileged rights too to make elevated windows manageable.

Kukunin avatar Jan 26 '19 01:01 Kukunin

The window is only on a single view, but Edge icon on the Task Bar is present on every view

That is the case with "ApplicationFrameWindow"; they cannot be fully hidden. The first window information looks ok, though. Why it becomes unmanagable after closing and opening the window, I do not know; it still has the same window and process id. It seems to run in the background after it has been closed.

For new Edge windows there is Config_rule_#18, but it may be, that after closing the window, putting the app in the background, bug.n may recognize it as closed, removes the windows id from the list of managed windows and therewith resulting in the observed behaviour. You may use the following Config.ini-line to set the hotkey WinCtrlO, with which you may force the active window to be managed. Config_hotkey=#^o::Manager_override(1;0;0;0;1;0;) You may also deactivate the backgroud option for Edge in the Windows Settings.


Regarding the problem with focus stealing you are right.

joten avatar Jan 27 '19 12:01 joten

@YnnhojDK You should be able to prevent Edge running in the background. In Windows 10 this is done by opening Settings > Privacy > Background Apps (on left hand menu) and turn off Edge.

blokeley avatar Jun 17 '19 11:06 blokeley

Having the same problem. Stopped it in background apps.

abhirup-dev avatar Nov 16 '19 04:11 abhirup-dev