- Status changed to Needs review
almost 2 years ago 1:29pm 18 January 2023 - Assigned to atul_ghate
- Issue was unassigned.
- Assigned to varun verma
- Issue was unassigned.
- Status changed to RTBC
almost 2 years ago 8:16am 20 January 2023 - Status changed to Needs work
almost 2 years ago 10:17am 24 January 2023 - 🇦🇺Australia pameeela
The background should be white like on larger screens.
One set of screenshots is all that is needed for each patch. Here, there are three sets, which makes it confusing and harder to review. Please, do not add new screenshots after they have already been added!
- Status changed to Needs review
almost 2 years ago 11:41am 24 January 2023 - 🇮🇳India gauravvvv Delhi, India
Remove the bg-color as advised in #18. Attached interdiff with #10. Attached patch for same. Please review
The last submitted patch, 19: 3327848-19.patch, failed testing. View results →
- 🇮🇳India DeepaliJ
Able to reproduce the issue using steps in IS
Applied patch #19 on Drupal 10.1.x-dev
The patch applied cleanly.
The background gets removed from the active verticle tab on smaller screens
Refer to the attached screenshotsRTBC +1
- Status changed to RTBC
over 1 year ago 2:01am 17 February 2023 - Status changed to Needs work
over 1 year ago 1:37pm 17 February 2023 - 🇺🇸United States bnjmnm Ann Arbor, MI
The solution appears to deviate from the original Claro designs. Perhaps someone involved with the design such as @ckrina or @saschaeggi should approve or potentially recommend a solution that preserves the design.
- Status changed to Needs review
over 1 year ago 1:52pm 17 February 2023 - 🇫🇮Finland lauriii Finland
The root cause seems to be that we're using incorrect media query in Claro for this rule. This implements a fix according to the designs; keeps the light blue background on mobile and overrides that with a white background on desktop.
This fix isn't entirely correct because
Drupal.behaviors.verticalTabs
allows configuring the breakpoint throughdrupalSettings
. Since the variable would be needed in media query, we would have to use custom media query for this. That is not supported by any browsers so there probably isn't any value in implementing that right now. - Status changed to Needs work
over 1 year ago 9:47pm 17 February 2023 The Needs Review Queue Bot → tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.
Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.
- Status changed to Needs review
over 1 year ago 7:43am 20 February 2023 - 🇮🇳India gauravvvv Delhi, India
Patch #27, contains few irrelevant files.
core/modules/block/src/BlockMachineNameGenerator.php core/modules/block/src/BlockMachineNameGeneratorInterface.php
I have fixed one comment in #25. Please review
- Status changed to RTBC
over 1 year ago 3:23pm 22 February 2023 - 🇺🇸United States smustgrave
This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.
Confirmed this issue on Drupal 10.1 and that the patch #28 solves it.
- Status changed to Fixed
over 1 year ago 5:47pm 29 March 2023 - 🇺🇸United States bnjmnm Ann Arbor, MI
This is committed to 10.1.x and cherry-picked to 10.0.x. Lauri points out that
Drupal.behaviors.verticalTabs
allows the breakpoint to be configurable, but I'd still consider this an unqualified fix as the media query now matches default breakpoint value. Having it match the configured value (of which there is no evidence of it being used) is something that deserves its own scope.Issue credit was not granted to the many, many screenshots provided after a perfectly good set was already there. +1s without additional issue-advancing content also did not receive credit
Automatically closed - issue fixed for 2 weeks with no activity.