Problem/Motivation
Because of #3083275: [meta] Update tests that rely on Classy to not rely on it anymore and Classy being deprecated in Drupal 9 + removed in Drupal 10,: Tests that aren't specifically testing Classy yet declare $defaultTheme = 'classy'; should be refactored to use Stark as the default theme instead.
Proposed resolution
Update AssertBreadcrumbTrait trait to use Stark as the default theme.
The tests that use AssertBreadcrumbTrait are:
BlockContentTypeTestin block_content.moduleHelpTopicTestin help_topics.moduleTermTranslationTestin taxonomy.moduleNodeTypeTestin node.moduleBreadcrumbFrontCacheContextsTestin system.moduleBreadcrumbTestin system.module
(already uses stark!?!?)
Rather than worrying about updating those now, let's just update the Trait to work with stark or classy.
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 3248309-2.patch | 740 bytes | danflanagan8 |
Comments
Comment #2
danflanagan8Here's a patch that changes one selector in the trait to make it work with stark (and classy, FWIW).
I should not that this trait uses another trait called
AssertMenuActiveTrailTrait. That trait has one function,assertMenuActiveTrail(), which will never work withstarkbecause it tests for themenu-item--active-trailclass, which stark only puts on the toolbar.This turns out not to be a big deal though. This function is only called during one test class, which is
BreadcrumbTest. (That's the only test that passes a$treetoAssertBreadcrumbTrait::assertBreadcrumb(). That test uses thestandardprofile and it can continue to use the standard profile. So we can just leave it as is.Comment #3
danflanagan8Comment #4
joachim commentedLGTM.
Comment #8
catchCommitted/pushed to 10.0.x and cherry-picked to 9.4.x and 9.3.x, thanks!
Agreed it's fine to leave
AssertMenuActiveTrailTraitfor now.