[MacPorts] #65546: Emacs: strange behavior of menu bar (and tool bar)

[MacPorts]

#65546: Emacs: strange behavior of menu bar (and tool bar)
------------------------+-----------------------
  Reporter:  monte-lin  |      Owner:  monte-lin
      Type:  defect     |     Status:  assigned
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.7.2
Resolution:             |   Keywords:
      Port:  emacs      |
------------------------+-----------------------
Changes (by monte-lin):

 * status:  new => assigned
 * owner:  (none) => monte-lin


Old description:

> I installed emacs with the cmd: "port install emacs +gtk"
> Everything seemed fine, and I got "emacs @28.1_1+gtk+nativecomp+x11"
>
> When run, its frame displayed as expected; both the menu bar and tool bar
> are of light background with black text.
> Immediately after I move the mouse pointer, both bars changed to be in
> black background with gray text on the menu bar (and all levels of menus)
> Even stranger, when we load a large file (such as Emacs manual) that
> spans several pages and then scroll down and up, the menu bar will chang
> to light background with black text ; and change back to dark mode
> immediately after you move the mouse pointer.
>
> There is no such issue when it's run remotely through remote X.

New description:

 I installed emacs with the cmd: "port install emacs +gtk" (on Mac Studo,
 macOS Monterey 12.4)
 Everything seemed fine, and I got "emacs @28.1_1+gtk+nativecomp+x11"

 When run, its frame displayed as expected; both the menu bar and tool bar
 are of light background with black text.
 Immediately after I move the mouse pointer, both bars changed to be in
 black background with gray text on the menu bar (and all levels of menus)

 What is even more weird, with a large file open (such as Emacs manual)
 that spans several pages and when I scroll the page down and up, the menu
 bar will change to light background with black text, and change back to
 dark mode immediately after I move the mouse pointer.

 There is no such issue when it's run remotely through remote X.

--

-- 
Ticket URL: <https://trac.macports.org/ticket/65546#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS