nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bug with "Open Payees & Rules List..." (Q Mac)

Scott Rose

I've discovered a bug in Quicken Mac Version 7.1.2 (Build 701.49356.100) running on macOS 13.4.1.

This is a keyboard-only bug, so be sure that you DON'T use your mouse during the steps below, or else it will work properly:

Go into one of your bank account's "transactions" window.
Hit command-N to create a New Transaction.
Hit tab until you get to the "Payee" field.
Start typing the name of an already-existing Payee.
Don't hit return or select any of the matching payees that show up in the dropdown list. Simply use the down arrow on your keyboard to navigate downwards to "Open Payees & Rules list…"
When "Open Payees & Rules list…" is highlighted, hit return on your keyboard.
BUG: The Payees & Rules list will not open in the foreground. It actually opens in the background where you can't see it.

Find more posts tagged with

Comments

Jon

It opened in the background for me also. I was able to see part of the window sticking out from behind the main window; didn't do me a whole lot of good though since it also automatically selected a payee for me & jumped ahead to the Category field. It doesn't do any of those things if you use the mouse to select "Open Payees & Rules List…".

Happens with both 7.1.2 and 7.2.0.

jacobs

Two notes:

(1) I have never, in the 9 years I've been using modern Quicken Mac, (a) selected "Open Payees & Rules list" from the transaction Payee selection menu or (b) even noticed that this option was at the bottom of the menu! 😂

(2) I tried this on an Intel-powered iMac running macOS Catalina and the just-released 7.2, and this bug did not occur. That is, selecting "Open Payees & Rules list" from the Payees dropdown menu resulted in the Payees & Rules window opening, as expected, in the foreground. I then tested the steps above on an M2-powered Macbook Air running macOS Ventura, and the bug does occur when following the steps above. So this problem is specific to either the chip hardware or the operating system. (I don't have more eMacs to test different permutations of Mac and operating system.)