Closed (outdated)
Project:
Drupal core
Version:
8.5.x-dev
Component:
CSS
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
17 Jan 2015 at 07:05 UTC
Updated:
4 Jan 2018 at 22:24 UTC
Jump to comment: Most recent, Most recent file

Comments
Comment #1
manjit.singhIt feels like this was succeeded by #2280035: Add another responsive tables solution that doesn't hide content.. Feel free to reopen though.
Comment #2
nitishchopra commentedComment #3
ram4nd commentedChanged the tag for consistancy by Topical issue tags.
Comment #4
manjit.singhComment #5
alexandr.khlopkov commentedComment #6
alexandr.khlopkov commentedpatch with alignment "system bread crumbs" menu (and not only) is missaligned structure->blocks (bartik theme)
Comment #9
manjit.singhI hope we can close it till the first release of Drupal 8. tagging it with + rc deadline
Comment #10
meenakshi.r commentedComment #11
meenakshi.r commentedComment #12
joelpittetRC deadline has past but I think this can likely be fixed? Tagging for release manager review.
But this issue really needs screenshots in the issue summary to show the problem.
Comment #13
alvar0hurtad0Now,
this is how we can see the /admin/structure/block page at the moment.
Comment #14
alvar0hurtad0@alexandr.khlopkov I'm not sure if you're still working. I've done the reroll.
Comment #15
alvar0hurtad0I forgot the status
Comment #18
iamDamon commentedwrong indentation and missing a space after the colon
Comment #19
manjit.singhcorrect Indentation and Adding space as per #18.
Comment #20
xjmAs a straight bugfix, this could potentially go into 8.0.x. However, looking at the patch, the CSS changes seem like they are broader than just the bug being fixed, and might also disrupt themes. Tagging for a CSS maintainer to help evaluate whether the fix is correct and what would be safe for existing themes and sites in 8.0.x. Thanks!
Reference: https://www.drupal.org/core/d8-allowed-changes#patch
Comment #21
Fred Martin commentedComment #23
cilefen commentedI removed the Novice tag because we are waiting for a maintainer's opinion.
Comment #24
iamanupmenon commentedI tested #19 patch and am still facing the same issue.

Comment #25
iamanupmenon commentedComment #26
brahmjeet789 commented@iamanupmenon i have created patch for this,please test and review it.
Comment #27
brahmjeet789 commentedComment #28
chernous_dn commentedHi @brahmjeet789 looks fine, attach screenshot. Test on dev 8.1
Comment #29
chernous_dn commentedBut you created patch with errors,
87 ++.draggable .block {attach screenshot. And you need add space here+ justify-content:center;like thisjustify-content: center;Comment #30
chernous_dn commentedComment #31
Vidushi Mehta commentedHere is the updated one. Please review.
Comment #32
chernous_dn commentedHi @Vidushi Mehta the same error
87 ++.draggable .block {Comment #33
chernous_dn commentedUpdate patch from #31
Comment #34
NikitaJain commentedVerified and tested the above patch (system_breadcrumbs_menu-2409009-33.patch) on dev 8.1. The patch applied successfully and its working fine. Screenshots attached.
Comment #35
star-szrThe patch in #33 won't have any effect when viewing core themes (Seven or Bartik) because at this point they both inherit from the Classy (and Stable) base themes, not the CSS in core/modules.
I think we need clear before and after screenshots and an updated issue summary (both tags are already there), I'm not sure from the issue summary or any comments or screenshots what the bug is that we're fixing. Looking at the code it seems to be something to do with the tabledrag but based on the title I would think it's relating to the breadcrumbs shown on that admin page.
Wait, is this talking specifically about the breadcrumbs block tabledrag row on the block layout page? The breadcrumbs block has a longer first word than most of the other blocks which causes it to look different at narrower resolutions. Attaching a screenshot:
If I have correctly decoded the bug described here (if this is the bug it shouldn't have taken this much of a leap to arrive at this conclusion), my opinion after looking at the screenshot is I'm not sure it's worth the fuss unless we can fix this in a generic way that will also work for longer words/titles. I suspect the proper solution may be larger than the scope of an issue like this, for example #2280035: Add another responsive tables solution that doesn't hide content as was pointed out in #1. Thanks everyone for your time so far.
Comment #38
joelpittetThis has been a year with no response to @Cottser so I'm closing for now