Closed (fixed)
Project:
Navigation
Version:
1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
16 Jan 2024 at 16:55 UTC
Updated:
27 Mar 2024 at 09:59 UTC
Jump to comment: Most recent, Most recent file


Comments
Comment #2
ckrinaAdjusting summary.
Comment #3
kostyashupenkoComment #5
kostyashupenkoComment #6
finnsky commentedThis code already defined.
Please check.
Comment #7
kostyashupenkoThanks, MR updated, very detailed answer written. Please check
Comment #8
finnsky commentedThat was planned as BEM block and not Drupal. Idk what else can appear in toolbar. Not sure we have to strictly relate them to Drupal entities here.
Comment #9
kostyashupenkoNew changes are based on BEM methodology aswell (sorry for wrong status)
Comment #10
finnsky commentedI see here `toolbar-block` and `navigation-block`...
I can agree that they do not contradict the BEM, but they clearly do not follow it. I see that a second (duplicate) block has appeared just to replicate the Drupal structure. Which, it seems to me, is not final at the moment. So this new file seems like an unnecessary complication to me.
But I'll leave this for review by other community members.
Comment #11
kostyashupenkoI would move `toolbar-block` BEM block on top of drupal's block. Again - we are rendering blocks with menus inside. Blocks can render label and content. So i'm thinking if `toolbar-block` classname should be added to `navigation-block.html.twig` as a wrapper. For menus inside - can be just `toolbar-block__menu` or `toolbar-block__section`.
It can be another task. I agree - this is all can be `toolbar-block` -> but it should start from drupal's block. Otherwise we have situation when we have drupal's block unnamed. And menu inside starts with `toolbar-block`, but should be an element of parent BEM block
Comment #14
ckrinaThis needs to be manually rebaded.
Comment #16
m4oliveiI resolved the merge conflict.
Comment #19
ckrinaI agree with @finnsky: both
.navigation-blockand.toolbar-blockare the same component, and this MR keeps the 2 CSS files/components with the title in one and the rest of CSS in the other. But I agree with you @kostyashupenko that CSS and "PHP"-generated classes should match. Here's some the background behind the previous discussion regarding naming and the agreement we reached (before most of the back-end work started): #3387374 and #3386927.Matching Drupal and BEM structure we have is:
- Navigation&co (wrapper, content...)
- Block (as Drupal block) and
.toolbar-block<-- Here is where we need to add the label.- Menu (as Drupal menu) and
.toolbar-menu- Menu links&co
On a back-end perspective we decided to use Navigation to avoid conflicts with the current Toolbar module. I know they don't match for now and they will have to match before opening a MR to core, but I wouldn't make naming changes in a specific MR that is supposed to only change styles. We'll need to properly discuss and plan the naming strategy now that we have both the front-end and back-end more defined, but let's have a discussion to properly bike-shed on that in another issue ;)
So let's keep the existing
.toolbar-blockfor now and re-structure components or naming in a follow-up.Comment #21
starshapedMet with @ckrina today and discussed #19. I moved the title to be back in `toolbar-block.css` with the additions that were added.
Comment #24
finnsky commentedSmall issue with vertical spacing. Please take a look! All other looks great. Thank you!
Comment #26
ahsannazir commentedRemoved the vertical padding as suggested because there is already ample spacing coming from grid-gap.
Comment #27
ahsannazir commentedComment #28
ckrinaSince we've just merged #3402592: Reset theme css. and touches several CSS files, this needs to be rebased wit the latest changes.
Comment #29
ahsannazir commentedComment #30
finnsky commentedLooks good to me in frontend, but i would like to request backender review here. Since it contains some php.
Comment #31
m4oliveiSee MR comments. A couple of code changes are needed here.
Comment #32
ahsannazir commentedComment #33
finnsky commentedI see it not works now. Gonna fix
Comment #34
plopescCode looks good to me!
Left a minor comment in the MR.
Comment #35
finnsky commentedThere was some misunderstanding in begin so we had 2 definitions.
Now fixed
Comment #36
ckrinaMerged! Thanks all for the work here. This finished a really nice to have feature for the navigation!
Comment #37
ckrina