Closed (fixed)
Project:
Drupal core
Version:
9.4.x-dev
Component:
Olivero theme
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Mar 2022 at 09:51 UTC
Updated:
9 Apr 2022 at 16:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
catchThis is whats missing. It should not really be necessary for all this to be in the template...
Comment #3
catchComment js also relies on the js-comment class.
Comment #4
mherchelThis is a great find! A couple issues:
1) I really didn't understand what was happening until I looked at Bartik and read the code comment within that template. Lets add the same comment into the Olivero template.
2) I don't believe the
<mark>element is semantically correct here. According to MDNThis isn't what we're doing. This element is simply giving JavaScript something to ingest.
Comment #5
andregp commentedFixed patch according to #4
Comment #6
mherchel#5 looks perfect. Pretty sure this patch should apply for d10... adding a test.
I verified this by creating two users, and a view that shows new comments. When user 1 created a comment, the "new" link was visible to user 2 and hyperlinked properly.
Comment #9
lauriiiShould we open follow-up to change the
<mark>element to a<span>in the comments module?Committed c668e0b and pushed to 10.0.x. Also cherry-picked to 9.4.x. Thanks!