Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I have a very hard time following comment threads on Bartik. I recently commented on a Bartik site (visible as the last comment in the screenshot). I would not be able to tell that my comment is in reply to the comment above mine (the 4th comment). It looks like I am replying to the third comment.
From what I recall this could be quite tricky to fix, we opted to go for a very flexible approach to accommodate the new image styles feature for user pics - I assume that is in effect here, the fourth comments user name could be forcing the user info column wider (the "user not verified" on the same line is not helping). I need to think about this for a while and consider a new approach.
Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.
Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.
Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)
Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)
Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)
Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)
Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.
Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.
Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.
This issue has not been discussed in 11 years and the comment was to say that this was hard to fix. The image originally posted is no longer available so it is not possible to see the problem. 9 years ago it was asked if this was still a problem and there has been no reply.
Since the information needed to work on this is no longer available and we can't test to see if it is still a problem, I think it is time to close this.
Comments
Comment #1
Jeff Burnz CreditAttribution: Jeff Burnz commentedFrom what I recall this could be quite tricky to fix, we opted to go for a very flexible approach to accommodate the new image styles feature for user pics - I assume that is in effect here, the fourth comments user name could be forcing the user info column wider (the "user not verified" on the same line is not helping). I need to think about this for a while and consider a new approach.
Comment #2
Everett Zufelt CreditAttribution: Everett Zufelt commentedSee somewhat related: #1272870: No semantics for nested comments / bad for screen-readers
Comment #2.0
Everett Zufelt CreditAttribution: Everett Zufelt commentedUpdating input format
Comment #3
mgiffordIs this still an issue?
Comment #15
drummCorrecting issue summary text format which should never have been set to full HTML.
Comment #16
quietone CreditAttribution: quietone at PreviousNext commentedThis issue has not been discussed in 11 years and the comment was to say that this was hard to fix. The image originally posted is no longer available so it is not possible to see the problem. 9 years ago it was asked if this was still a problem and there has been no reply.
Since the information needed to work on this is no longer available and we can't test to see if it is still a problem, I think it is time to close this.
Thanks to everyone who commented!