Problem/Motivation

While creating custom basic block through the layout builder using the Claro theme, form descriptions do not have proper contrast which makes them unreadable.

Regarding question in comment #6:

Can you elaborate why someone would be using Claro for their front-end theme?

One scenario is when the site is decoupled and you want the content editor to just see the same theme for the CMS "frontend" and "backend" because Drupal is not being used for the user-facing "frontend".

Steps to reproduce

  1. Choose Claro as the default site theme
  2. Home > Administration > Structure > Content types > Article > Manage display: under layout options, check layout builder
  3. Go to an article node and click Layout tab
  4. Click on Add block and create a Custom block > Basic block
  5. Results: Title input field description is not readable
  6. Expected results: Title input field description is readable

Proposed resolution

Update the CSS to ensure the styling of the description is readable.

Remaining tasks

  • Create patch
  • Review and test patch
  • Decide if this use case is valid for core
  • If so, commit

User interface changes

Can properly read the description text.

API changes

Data model changes

Release notes snippet

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tushar_sachdeva created an issue. See original summary.

Sakthivel M’s picture

Status: Active » Needs review
FileSize
869 bytes

#2 Please review the patch

manojithape’s picture

Assigned: Unassigned » manojithape
manojithape’s picture

Assigned: manojithape » Unassigned
FileSize
94.75 KB
91.04 KB

Verified and tested patch#2 on the drupal 9.3.x-dev version and Claro 9.3.0-dev version. Patch applied successfully and looks good to me.

Testing Steps:

  1. Install drupal 9.3.x-dev version.
  2. Go to Appearance -> Set Claro theme as admin and default theme
  3. Home>Administration>Structure>Content types>Article,under layout options check layout builder.
  4. Go to the article node, click on layout.
  5. Click on Add block, create a custom block>basic block.
  6. Observe title Input field description is not visible.
  7. Now apply the patch and clear the cache.
  8. Again Go to the article node, click on layout.
  9. Click on Add block, create a custom block>basic block.
  10. Verify title Input field description is visible.

Testing Results:

After applying the patch title Input field description is visible.
Please refer attached Before patch and After patch images for reference.

Moving this ticket to RTBC.

manojithape’s picture

Status: Needs review » Reviewed & tested by the community
larowlan’s picture

Status: Reviewed & tested by the community » Needs review

Claro is an admin theme. Layout builder uses the site's front-end theme.

Can you elaborate why someone would be using Claro for their front-end theme?

Sakthivel M’s picture

Status: Needs review » Needs work
Issue tags: +Needs reroll
Sakthivel M’s picture

Status: Needs work » Needs review
FileSize
881 bytes

#8 Please review the patch

kleiton_rodrigues’s picture

Assigned: Unassigned » kleiton_rodrigues
kleiton_rodrigues’s picture

Assigned: kleiton_rodrigues » Unassigned
FileSize
94.95 KB

The patch #8 applies cleanly in drupal version 9.3.x-dev, the & concatenates the parent class is good in #drupal-off-canvas...
Works as expected good for me

chetanbharambe’s picture

Verified and tested patch #8.
Patch applied successfully and looks good to me.

Testing Steps:
# Go to Appearance -> Set Claro theme
# Goto Extend: Install Layout builder module
# Goto: Home>Administration>Structure>Content types>Article, under layout options check layout builder.
# Go to the article node, click on layout.
# Click on Add block, create a custom block
# Observe title Input field description is not visible

Expected Results:
# Title Input field description is visible

Actual Results:
# Title Input field description is not visible

Please refer attached screenshots.
Looks good to me.
Need +1 RTBC.

kostyashupenko’s picture

Issue tags: -Needs reroll
vikashsoni’s picture

Applied patch #8 working fine
After patch the title field is visible
for ref sharing screenshot ....
Thanks or the patch

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

bnjmnm’s picture

Issue tags: +stable blocker
ranjith_kumar_k_u’s picture

Satyajit1990’s picture

Testing Steps :
1. Go to Appearance -> Set Claro theme as admin and default theme
2. Home>Administration>Structure>Content types>Article, under layout options check layout builder.
3. Go to the article node, click on layout.
4. Create Basic Page (Content >> Add Content >> Select Basic page)
5. Fill the mandatory field Tile, Body
6. Change the draft to published and save
7. Now click on Layout tab on the created page
8. Click on Add block on configure section 1 >> Choose a block section will appear on the right side
9. Now Click on create custom block and select Basic Block and verify the Title Input field description is visible or not

Expected Results: Title Input field description is visible

Actual Results: Title Input field description is not visible
Please refer the screenshot below attached in the file
Screenshot 2022-02-14 at 3.06.15 PM.png (415.38 KB)

Kristen Pol’s picture

Thanks for testing. Moving back to needs work based on #17.

Kristen Pol’s picture

Status: Needs review » Needs work

Whoops. For real this time.

Kristen Pol’s picture

Status: Needs work » Needs review
Issue tags: +Needs manual testing

There was likely something wrong with DrupalPod when testing in #17 so moving back to needs review for #16.

Devashish Jangid’s picture

FileSize
55.99 KB

Verified and tested patch #16.
Patch applied successfully and looks good to me.
Sharing screenshot for the reference.
Moving this ticket to RTBC.

Kristen Pol’s picture

Thanks for testing.

I'm just now seeing #6 asking:

Claro is an admin theme. Layout builder uses the site's front-end theme.

Can you elaborate why someone would be using Claro for their front-end theme?

so tagging for issue summary update to explain the use case.

I thought that we could configure Drupal to use the frontend or backend theme for content editing... was that just an older version? I'll see if I can find the configuration option... unless it's just for older versions.

Kristen Pol’s picture

This is the setting that let's you toggle content editing between the two themes:

Kristen Pol’s picture

Okay, I misunderstood. I was assuming that that checkbox was used for anything for editing the content but see what @larowlan was saying.

The "Use administration theme when editing or creating content" does not affect the layout builder. It's always using the frontend theme. You would have to use Claro as the frontend theme to see this issue. Since Claro is meant to be used for the admin theme and not the frontend theme, @larowlan's question remains:

Can you elaborate why someone would be using Claro for their front-end theme?

I have one scenario which is when the site is decoupled and you want the content editor to just see the same theme for the CMS "frontend" and "backend" because Drupal is not being used for the user-facing "frontend".

Kristen Pol’s picture

Issue summary: View changes
Status: Needs review » Reviewed & tested by the community
Issue tags: -Needs issue summary update +Accessibility

Marking RTBC to be assessed for commit. I have updated the issue summary with a possible use case along with clarifying the steps to reproduce and filling in the issue summary template.

1. Assumes using Claro for "frontend" theme is valid (see issue summary update).

2. Tests pass.

3. Manual testing passes.

4. Assumes adding additional tests can't be added easily.

5. Code is simple CSS change though I'm not 100% this is the approach that the Claro team would endorse.

alexpott’s picture

Version: 9.4.x-dev » 9.3.x-dev
Status: Reviewed & tested by the community » Fixed

@kleiton_rodrigues please don't post screenshots of code applying to issues.

Thanks everyone who posted screenshots of the patch working and the bug.

Given that Claro already has work arounds for drupal-off-canvas I think it's fine to continue. I would question the use of layout builder on a decoupled site - it's going to be a lot of "fun" to re-building an understanding of layout builder in your frontend!

Committed and pushed 035cd7de47 to 10.0.x and e76eaf19eb to 9.4.x and 088986959a to 9.3.x. Thanks!

Backported to 9.3.x since claro is not yet stable.

  • alexpott committed 035cd7d on 10.0.x
    Issue #3213556 by Sakthivel M, ranjith_kumar_k_u, manojithape,...

  • alexpott committed e76eaf1 on 9.4.x
    Issue #3213556 by Sakthivel M, ranjith_kumar_k_u, manojithape,...

  • alexpott committed 0889869 on 9.3.x
    Issue #3213556 by Sakthivel M, ranjith_kumar_k_u, manojithape,...
Kristen Pol’s picture

Issue tags: +Bug Smash Initiative

Thanks! I forgot to tag that this was part of bugsmash!

UPDATE:

Just read...

I think it's fine to continue. I would question the use of layout builder on a decoupled site - it's going to be a lot of "fun" to re-building an understanding of layout builder in your frontend!

Haha, good point :D

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.