Specificity issue after upgrading to 3.3.1

[krampstudio]

I have the following setup:

darkMode : 'class'

in a css file

@layer base {
	.dark .text-black {
		@apply text-gray-200;
	}
}

And in my HTML, I have some places I override the text-black to have black on white, ie

<button class="dark:bg-white dark:text-black">I'm a black text on a white background even in dark mode</button>

With tailwind 3.2 it was working, getting in the generated code:

.dark .text-black{
  --tw-text-opacity: 1;
  color: rgb(229 231 235/var(--tw-text-opacity));
}
.dark .dark\:text-black {
  --tw-text-opacity: 1;
  color: rgb(0 0 0/var(--tw-text-opacity));
}

But with tailwind 3.3, the specificity of the base style increases:

.dark :is(.dark .dark\:text-black) {
  --tw-text-opacity: 1;
  color: rgb(229 231 235 / var(--tw-text-opacity));
}
:is(.dark .dark\:text-black) {
  --tw-text-opacity: 1;
  color: rgb(0 0 0 / var(--tw-text-opacity));
}

I'm wondering why there's an additional .dark in front of the :is()?

[krampstudio]

To work it around I had to move away all .dark overrides from the @layer

[krampstudio]

The trick above doesn't seem to work anymore in tailwind 3.4