Just a quick report about Font-your-face module and Claro, the view display seems to have problems (cf screenshot).
(Not quite sure about the Claro version, I have activated the one in Drupal 8.8.6)
Thanks anyway for this admin theme, really nice to use on a daily basis.

Comments

Toki created an issue. See original summary.

shalinigaur’s picture

Assigned: Unassigned » shalinigaur
shalinigaur’s picture

Status: Active » Needs review
StatusFileSize
new529 bytes
new405.45 KB

Hi, created a patch 3143782-3.patch for Claro 8.x-1.0-beta1. Please check screenshot

sc

shalinigaur’s picture

Assigned: shalinigaur » Unassigned
shalinigaur’s picture

StatusFileSize
new507 bytes
lauriii’s picture

Project: Claro » Drupal core
Version: 8.x-1.0-beta1 » 9.1.x-dev
Component: User interface » Claro theme

Moving to the Drupal core queue because Claro has been moved to Drupal core.

asmita26’s picture

Assigned: Unassigned » asmita26
asmita26’s picture

Status: Needs review » Needs work

#5 Committed patch failed for D8.9 hence moving it to needs work to re-roll the patch.

ravi.shankar’s picture

Status: Needs work » Needs review
StatusFileSize
new589 bytes

Here I have added a re-roll of patch #5 for Drupal 9.1.x.

asmita26’s picture

Assigned: asmita26 » Unassigned
Status: Needs review » Needs work
StatusFileSize
new328.76 KB

Hi @ravi.shankar The patch needs to be recreated as pcss.css files are missing and must be verified with Font-your-face module but when i verified the Font-your-face module seems not compatible with D9 hence this issue is blocked till then.

hansa11’s picture

Assigned: Unassigned » hansa11
bnjmnm’s picture

Status: Needs work » Postponed

The font your face module is not compatible with Drupal 9, so setting this to postponed. This is probably more appropriate as an issue in font-your-face, but I'm not certain of that. I am

+++ b/core/themes/claro/css/layout/layout.css
@@ -28,3 +28,18 @@
+}

I do know that the current approach in the patches will definitely not work as it changes the styles for item-list ul, h4 and h5 elements everywhere in Claro. This will break styling in a number of places. The selectors will need to be more targeted. If that targeting is a selector added by font-your-face, then the change should be in that module. I recommend moving it there but won't do the moving in case there was a specific reason for adding it as a Claro issue that I'm unaware of.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

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

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

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.

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

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Assigned: hansa11 » Unassigned
Status: Postponed » Active

If I am reading this correctly, this was postponed because @font-your-face is not compatible with Drupal 9. That was fixed in #3042792: Drupal 9 Deprecated Code Report, so setting to active.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

gauravvvv’s picture

Status: Active » Needs review
StatusFileSize
new7.03 KB

I have themed the @font-your-face view. I have attached patch for same. please review

bnjmnm’s picture

Status: Needs review » Needs work
+++ b/core/themes/claro/css/components/views-ui.pcss.css
@@ -574,3 +574,121 @@ details.fieldset-no-legend {
+.view-fontyourface-font-manager {

There is no core fontyourface view, and this entire patch is based on styling a fontyourface view. This would absolutely not be commite to core as it's styling something that isn't in core - it's something you get from a specific contrib module.

If this is the desired approach , then it should be added to https://www.drupal.org/project/fontyourface, not core.

If you opt for a more generic solution (one that doesn't have CSS full of 'fontyourface'), it could go in core.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

nishamukta’s picture

Assigned: Unassigned » nishamukta

I agree with @bnjmnm that the patch should be applied to the "fontyourface" module, not Claro, because view display appears to be an issue when this module is installed, and the issue is now tagged to version 11.x-dev, where the fontyourface module is not available; it is only available till Drupal 10. I think tagging should be corrected.

nishamukta’s picture

Assigned: nishamukta » Unassigned

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

quietone’s picture

Status: Needs work » Postponed

The Claro theme was approved for removal in #3576460: [policy, no patch] Deprecate and remove Claro.

This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.

The deprecation work is in #3576668: [meta] Tasks to deprecate Claro and the removal work in #3584638: [meta] Tasks to remove the Claro theme.

smustgrave’s picture

Project: Drupal core » Claro
Version: main » 3.0.x-dev
Component: Claro theme » Code
Status: Postponed » Postponed (maintainer needs more info)
Issue tags: +Needs issue summary update

Claro has moved to contrib

But this needs an IS update before it can be worked on