DisplayFusion RSS: [BUG] Window created trigger doesn't detect Waterfox Classic console https://www.displayfusion.com/Discussions/RSS/?TopicID=717a9c87-0322-49e2-8639-e0c0d025221d DisplayFusion RSS: [BUG] Window created trigger doesn't detect Waterfox Classic console Sun, 19 Apr 2026 16:21:22 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=717a9c87-0322-49e2-8639-e0c0d025221d RE: [BUG] Window created trigger doesn't detect Waterfox Classic console https://www.displayfusion.com/Discussions/View/bug-window-created-trigger-doesnt-detect-waterfox-classic-console/?ID=717a9c87-0322-49e2-8639-e0c0d025221d#6 Thu, 11 Jun 2020 19:43:22 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/bug-window-created-trigger-doesnt-detect-waterfox-classic-console/?ID=717a9c87-0322-49e2-8639-e0c0d025221d#6 DisplayFusion That is weird for sure. I've added this to our list to investigate further and we'll see what we can find out.

Thanks! ]]> RE: [BUG] Window created trigger doesn't detect Waterfox Classic console https://www.displayfusion.com/Discussions/View/bug-window-created-trigger-doesnt-detect-waterfox-classic-console/?ID=717a9c87-0322-49e2-8639-e0c0d025221d#5 Tue, 09 Jun 2020 21:28:54 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/bug-window-created-trigger-doesnt-detect-waterfox-classic-console/?ID=717a9c87-0322-49e2-8639-e0c0d025221d#5 DisplayFusion It's just weird that setting would disable triggers...and only for some applications, not all. ]]> RE: [BUG] Window created trigger doesn't detect Waterfox Classic console https://www.displayfusion.com/Discussions/View/bug-window-created-trigger-doesnt-detect-waterfox-classic-console/?ID=717a9c87-0322-49e2-8639-e0c0d025221d#4 Tue, 09 Jun 2020 20:28:15 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/bug-window-created-trigger-doesnt-detect-waterfox-classic-console/?ID=717a9c87-0322-49e2-8639-e0c0d025221d#4 DisplayFusion It's not really broken, that's the expected behaviour, the shortcut option will override the Trigger rules. I'll check to see if we can add a note about that in the help docs :)

Thanks! ]]> RE: [BUG] Window created trigger doesn't detect Waterfox Classic console https://www.displayfusion.com/Discussions/View/bug-window-created-trigger-doesnt-detect-waterfox-classic-console/?ID=717a9c87-0322-49e2-8639-e0c0d025221d#3 Mon, 08 Jun 2020 21:24:20 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/bug-window-created-trigger-doesnt-detect-waterfox-classic-console/?ID=717a9c87-0322-49e2-8639-e0c0d025221d#3 DisplayFusion Disabling "Force application to start on same monitor..." worked. Thank you.

Maybe it would be a good idea add a note to that setting regarding this issue until it's fixed? ]]> RE: [BUG] Window created trigger doesn't detect Waterfox Classic console https://www.displayfusion.com/Discussions/View/bug-window-created-trigger-doesnt-detect-waterfox-classic-console/?ID=717a9c87-0322-49e2-8639-e0c0d025221d#2 Mon, 08 Jun 2020 17:05:28 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/bug-window-created-trigger-doesnt-detect-waterfox-classic-console/?ID=717a9c87-0322-49e2-8639-e0c0d025221d#2 DisplayFusion If you disable the "Force application to start on same monitor..." option in the DF shortcut, does that make any difference? I believe that can prevent Trigger rules from running on the window. ]]> [BUG] Window created trigger doesn't detect Waterfox Classic console https://www.displayfusion.com/Discussions/View/bug-window-created-trigger-doesnt-detect-waterfox-classic-console/?ID=717a9c87-0322-49e2-8639-e0c0d025221d Sun, 07 Jun 2020 20:54:03 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/bug-window-created-trigger-doesnt-detect-waterfox-classic-console/?ID=717a9c87-0322-49e2-8639-e0c0d025221d DisplayFusion Hello.
This is a very wierd issue. When waterfox launched with -jsconsole command line argument it opens Browser Console before it's main window. When it launched from a desktop shortcut DF trigger properly detects the console, however when it launched from a pinned to DF taskbar shortcut, trigger doesn't detect the console.
This only affects Waterfox Classic, Waterfox Current has no issue.
I also should mention, this only happens under certain conditions:
1) the browser profile already exists and initialized (aka it was launched once)
2) startupCache folder in profile folder is deleted or read/write protected

I'm using the following setup:

Steps to reproduce (assuming profile folder is empty):
  • 1) launch Waterfox via desktop or taskbar shortcut = the notification balloon should popup
  • 2) close Waterfox, make sure ALL windows are closed
  • 3) delete C:\myprofilefolder\startupCache folder
  • 4) launch Waterfox via DF taskbar pinned shortcut = no notification balloon shown
  • 5) repeat step 2 and 3, launch Waterfox again but this time via desktop shortcut = the notification balloon shown.

Currently the solution is quite simple, instead of using path to waterfox.exe and providing arguments in DP pinned shortcut window, use path to shortcut on desktop instead and leave arguments field empty (see DF_waterfox_pinned_fix) The only drawback is once launched it will be shown as non-pinned item at the DF taskbar.

I'm curious to find why this happening, what does DF different when launching applications than explorer does?

Thank you.

P.S.
After investigating further, I learned that this issue temporary fixes if ANY of these preferenced in pref.js in Waterfox's profile modified or removed

Code
Copy
Select All

user_pref("sanity-test.advanced-layers", false);
user_pref("sanity-test.device-id", "0x1e07");
user_pref("sanity-test.driver-version", "26.21.14.4614");
user_pref("sanity-test.running", false);
user_pref("sanity-test.version", "MOZ_BUILDID");
]]>