Kind of a niche use case here I guess.
Since the earliest versions of NightTab I've been able to use VivaldiFox (Github) (AMO) to color the browser's toolbars the same color as NightTab's header shade.

With the latest version though, assuming because of the header logic or layout control changes, VivaldiFox fails to load the right color, selecting some grey shades apparently picked while NightTab is still loading.
If I may suggest a workaround, VF still seems to load the accent color as the toolbar color when there is a border on top of the shade. So maybe a toggle for the border color to switch between accent color and the shade's natural color (before taking into account the opacity settings)?
This should make sense with the new layout options so you can have, for example, a transparent shade below the bookmarks with the dark grey borders on top and/or bottom.
I'm new to VivaldiFox so I will investigate. I'll see if I can learn how VivaldiFox detects the colour to use. A quick bit of digging suggests it may use the <meta name="theme-color" content="#000000"> meta tag.
Will investigate more.
Thank you.
I can't tell what the default setting "Use colors defined by the web page when available" exactly uses but when that setting is unticked (or when the colors aren't defined, I assume):

It looks like VF picks the color from the center pixel:

That's how my VF is set up, and it used to work well before v3.30.6 (now it picks up the white from the white flash that happens before page loading is complete). With that, depending on the method VF uses to detect that page-load is complete, this issue might be related to page load / white flash issues.
Seems to be working almost consistently now when header shade is shown on top and is opaque. When it isn't, the behavior isn't consistent, It will load the dark theme color on first load,

then pick up the wallpaper color on refresh,

sometimes improperly. Rarely even when header shade is opaque and on top:

But, matching the header shade was all I needed, so I'm closing the ticket. Thanks for working on this.
Understood. I'll continue to look into this behaviour nonetheless.