Link Element: Color definitions should exclude Image block which can get linked element (e.g. within Gallery block)

[porg]

Followup Issue

• of Link text does not have its defined color but falsely color from button text #51265
• Eventually I had got @scruffian 's hint working in a cloned TT3 theme.
• The theme.json addition produces the following enqueued CSS:

<style id="wp-block-post-content-inline-css">
  .wp-block-post-content a:where(:not(.wp-element-button)){color: var(--wp--preset--color--link-plain);}
</style>

• Now this yields a followup issue:

Reproduction

1. Insert a native gallery with 3 images.
2. Via the block inspector UI give all images a border-width: 1px.
   • The border-color and border-type hence inherit the defaults.
3. Select the gallery block → Options → LINK TO: Media File.
   • This wraps each gallery <img> within an <a>.
   • ❌ Undesired outcome: The border of the images is now not black anymore but --wp--preset--color--link-plain (blue).
   • ✅ Fix on a CSS level: Extend the :not() selector to also exclude > .wp-block-image, so
     .wp-block-post-content a:where(:not(.wp-element-button, > .wp-block-image)){ ... }

Could someone please integrate that fix?

• In the web browser DevTools of the Frontend view I could fix the CSS selector,
  • But I have now idea where in WordPress that fix needs to be integrated
    • In the Image block?
    • theme.json of TT3?
• I hope a developer can use my hint and knows where to fix it adequately

[porg]

Addendum: Realized this detail only now

• In the UI I had only explicitly set the image border-width: 1px
  • Therefore the border-style and border-color were just inherited.
  • And as the HTML hierarchy is: figure.wp-block-image → a → img if figure.wp-block-image gets no inline styles (strong specificity!) the deeper A element's color then gets inherited down to the even deeper IMG element, which eventually has the borders on it.
  • If in the UI you set an explicit color then figure.wp-block-image gets an element style attribute which prevails!
• Updated issue description accordingly.

But still it is a bug

• The .wp-block-image should definitely be excluded in that :not() lookahead selector.

For now I fixed it in my global.css (custom CSS file) with this:

.wp-block-post-content .wp-block-image a { color: unset; }

Maybe more specifically it could be:

.wp-block-post-content .wp-block-image.has-custom-border a { color: unset; }