Closed (fixed)
Project:
Context
Version:
8.x-4.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Jun 2020 at 19:39 UTC
Updated:
24 Jul 2020 at 16:19 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
paulocsHello @vector_ray,
Could you be more specific how to reproduce the issue?
Steps I did to try to reproduce:
1) Installed Context 8.x-4.x-dev
2) Created a new context in structure->context->add new context
3) In my context I used as Conditions a node bundle for articles and in Reactions I placed a main navigation in the Header
My attributes are not broken.
Thanks :)
Comment #3
vector_ray commented1) Install fresh copy of drupal 8.9.1
2) Set Bartik as the default theme
1) Installed Context 8.x-4.x-dev
2) Created a new context in structure->context->add new context
3) In context set no condition and do not check 'Include blocks from Block layout' I placed the core main navigation in the Header.
Now this is all I see when visiting the homepage

When viewing the source code on the main navigation block I see that the aria-labelledby attribute on block div and the id attribute on the block title are '-menu'

In the twig template in stable, classy and bartik: block--system-menu-block.html.twig
is printing out a variable
attributes.idwhich is missing. If I place the menu block using the block layout system that variable is printing correctly.I hope this is enough to go on.
Comment #4
thallesIn my enviroment this don't reproduce, see:

my contex settings:
The output:

Comment #5
thallesI am using Drupal 8.9.1 and dev branch
Comment #6
paulocs@vector_ray, please try git pull in the 8.x-4.x-dev branch and see if it is happening.
Thanks @thalles!
Comment #7
vector_ray commentedSteps I've taken:
1. Pulled the latest 8.x-4.x-dev version via composer
2. ran
drush updbThe following updates are pending:
context module :
8003 - Add default "custom_id" property to all blocks reactions.
Do you wish to run all pending updates? (y/n): y
Performing context_update_8003
3. Ran the pending change
4. tested and confirmed that this is fixed in the latest dev version.
Thanks for your help guys. Any idea when we can expect this in a stable release? I have some projects whose security requirements do not allow dev releases or patches in their codebase.
Comment #8
paulocsWe are working on a next release. See issue #3156120: Plan for a new release
We will release a new version soon!