WordPress.org

Make WordPress Core

Opened 9 months ago

Last modified 8 months ago

#48684 new defect (bug)

Twenty Twenty: Issue with primary color when using Gutenberg

Reported by: grafruessel Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 5.3
Component: Bundled Theme Keywords: has-screenshots needs-testing
Focuses: css Cc:

Description (last modified by SergeyBiryukov)

Hi there,

I found an error in css , when working with gutenberg editor in backend.

When I select the primary color as background color the row editable functions dont work due to css error.

This class should be fixed:

.has-background.has-accent-background-color *:not(.has-text-color) {
    color: #f9f9f9;
}

We can just delete this class or where else is it needed?

Thanks Niko

Attachments (2)

de_twentytwenty_linkcolor.png (881.2 KB) - added by grafruessel 9 months ago.
wpbeta5.4-gutenberg-error.png (713.2 KB) - added by grafruessel 8 months ago.

Download all attachments as: .zip

Change History (13)

#1 @nielslange
9 months ago

  • Keywords needs-patch added; has-patch removed
  • Summary changed from twenty twenty theme - primary color & gutenberg error to Twenty Twenty: Issue with primary color when using Gutenberg

#2 @grafruessel
9 months ago

  • Keywords needs-patch removed
  • Summary changed from Twenty Twenty: Issue with primary color when using Gutenberg to twenty twenty theme - primary color & gutenberg error

Steps to reproduce:

  1. edit a page
  2. select gutenberg block "Media & Text"
  3. on the text side use a background color in dark
  4. the editable sections becomes light (photo attached)

Expected behaviour:
the buttons should stay visible

Current behaviour:
the text color (#f9f9f9) is almost the background color (#ffffff)

Last edited 9 months ago by grafruessel (previous) (diff)

#3 @grafruessel
9 months ago

  • Summary changed from twenty twenty theme - primary color & gutenberg error to Twenty Twenty: Issue with primary color when using Gutenberg

#4 @SergeyBiryukov
9 months ago

  • Description modified (diff)

#5 @nielslange
9 months ago

#48723 was marked as a duplicate.

#6 @ianbelanger
9 months ago

#48723 was marked as a duplicate.

#7 @ianbelanger
9 months ago

  • Milestone changed from Awaiting Review to 5.3.1

#8 @ianbelanger
9 months ago

  • Keywords needs-testing added
  • Milestone changed from 5.3.1 to Awaiting Review

#9 @melchoyce
8 months ago

Able to reproduce running WordPress 5.3, Twenty Twenty 1.0, and Gutenberg 7.0.0.

@karmatosed is unable to reproduce on WordPress 5.4-alpha-46812, Twenty Twenty 1.0, and Gutenberg master — so it might be fixed in Gutenberg master?

#10 @grafruessel
8 months ago

@karmatosed, @melchoyce nope the error still exists.

Just tested with development version (5.4-alpha-46829) and with development version (5.4-alpha-46885)
Both versions you don't see the right color.
Twenty TwentyVersion: 1.0

I don't where I can check the Gutenberg Version.

If anyone want a login to the backend, just write me in slack. (same name)

#11 @melchoyce
8 months ago

Thanks @grafruessel. You'd only be running the Gutenberg Master branch if you have it installed via the GitHub repo (vs. the latest plugin release, or the version in core).

Note: See TracTickets for help on using tickets.