Details: see #1991684: Node history markers (comment & node "new" indicator, "x new comments" links) forces render caching to be per user, particularly the issue summary and comments 14 and 40.

This issue was split off from that issue because the render cache breakage of the Comment module's Views integration does not break entity render caching, which is what we were trying to unblock there.

Comments

Wim Leers’s picture

Title: Comment's node_new_comments View field ("new" comment marker) forces render caching to be per user » Comment's node_new_comments View field history markers ("new" comment marker) forces render caching to be per user
Wim Leers’s picture

andypost’s picture

Issue summary: View changes
Issue tags: +Needs issue summary update

@Wim, is this issue still valid?

Wim Leers’s picture

#3: Yes, because Drupal\comment\Plugin\views\field\NodeNewComments is unchanged since #2.

catch’s picture

Just to confirm this is still valid nearly a year later - was just checking the least-recently-updated major bugs.

Version: 8.0.x-dev » 8.1.x-dev

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.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

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.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Wim Leers’s picture

Category: Bug report » Task
Issue tags: +Performance

This is not a bug: nothing is broken, this is about improving performance by improving cacheability, so it's a task.

Version: 8.2.x-dev » 8.3.x-dev

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.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.