Problem/Motivation
Steps to reproduce the problem:
- Enable the
tracker(human-readable name Activity Tracker) module of Drupal core. It requires no further configuration. - Create a piece of content, for example a Page or Article.
- Log in to the site with an other user account different from who the content has created.
- Visit the /activity URL path of the site. You should see a table listing the only one content.
- Beside its node title a colored "new" or "updated" text appears.
The <span class="marker">updated</span> element containing the status text has no gap from the <a> element containing the node title. This is bad not only for human reading, but for accessibility reasons as well.

Drupal core: 8.8.0-beta1
Apache: 2.2.34
PHP: 7.3.8 / Mem: 128M
MySQL: 5.7.26
mac OS: 10.13.6
Proposed resolution
Insert an extra non-breaking space ( ) character between these two elements. Advantages are that they will stay together in any circumstances (not breaking under into a new line, for example) and being theme/CSS agnostic.
Remaining tasks
Probably no further tasks are known.
User interface changes
Hopefully a minor visual improvement fixed.
API changes
N/A
Data model changes
N/A
Release notes snippet
N/A
Original report by [username]
N/A
| Comment | File | Size | Author |
|---|---|---|---|
| #31 | tracker-3095533-31.patch | 571 bytes | richard.walker.ardc |
| #24 | After--patch.jpg | 30.25 KB | ranjith_kumar_k_u |
| #24 | Before--patch.jpg | 29.73 KB | ranjith_kumar_k_u |
| #23 | Screenshot 2021-06-06 at 12.37.10.png | 67.31 KB | gauravvvv |
| #23 | marker-spacing-3095533-23.patch | 604 bytes | gauravvvv |
Issue fork tracker-3095533
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
baluertlAttaching patch for review.
Comment #3
dinesh18 commented#2 patch looks good to me. +1 to RTBC.
Here are the screenshots attached. Changing the status to RTBC.
The automated script will pass hopefully.
Comment #4
baluertl@Dinesh18 thanks for the quick response. After consulting with one of my colleagues I removed the concatenation from the second place to make the code more consistent.
Comment #5
dinesh18 commentedLooks better.
Comment #7
baluertlComment #8
baluertlSetting back issue status to RTBC as tests on more modern PHP versions are passing.
Comment #9
hardik_patel_12 commented@Balu Ertl,
+++ b/core/modules/tracker/js/tracker-history.es6.js
@@ -19,7 +19,7 @@
if (timestamp > lastViewTimestamp) {
const message =
lastViewTimestamp === 0 ? newNodeString : updatedNodeString;
- $(placeholder).append(`${message}`);
+ $(placeholder).append(` ${message}`);
}
});
}
changes is not required.
Comment #10
hardik_patel_12 commentedComment #11
hardik_patel_12 commentedKindly follow a new patch.
Comment #12
hardik_patel_12 commentedComment #13
baluertl@Hardik_Patel_12
I see your point: you state that only the
.jsfile needs to be patched, but the.es6.jsfile not.However, afaik the native (.js) file is the result of transpiling from the source (.es6.js) file regarding this change record from 20 May 2017. For more information on the background of this decision see the reasoning in this comment.
Therefore I still believe that my patch from #2 is the correct one as it modifies both files.
Comment #14
alexpott@Balu Ertl you're correct that the .es6.js file is the one where changes should be made and then transpiled to the .js using the dev tools.
However, as far as I can see you're rtbc'ing your own patch which is not how this works. The patch should be reviewed by someone other than the patch author and they should set it to rtbc.
One of the things missing from this issue is an analysis of how this change might affect existing sites. That said it does appear that in Drupal 7 days theme_mark would add this space and here we're removed it for no obvious reason.
Also it is very helpful if the most recent patch on the issue is the correct patch.
Comment #15
swatichouhan012 commentedComment #16
swatichouhan012 commentedHere is the new patch with interdiff and screenshot please review.
Comment #18
kishor_kolekar commentedI've re-rolled patch for 9.1
Comment #19
alexpottElsewhere in core we're not encoding a space as - I'm not sure we need to. See Drupal.theme.quickeditImageDropzone for an example where we are using a space instead.
Comment #22
richard.walker.ardc commentedPatch 18 works for me; any chance it can be merged?
Comment #23
gauravvvv commentedSpacing fixed with CSS. No need of &nsbp;
Adding after patch screenshot for reference. Please review.
Comment #24
ranjith_kumar_k_u commentedThe above patch works fine.

Before patch
After patch

Do we need to fix this through CSS?
We can simply fix it by adding a normal space before "
<span>", like the following codeComment #28
quietone commentedThis extension is deprecated and scheduled for removal in Drupal 11.
This is now Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.
It will be moved to the contributed extension once the Drupal 11 branch is open.
Comment #30
andypostMR needs rework for contrib module now
Comment #31
richard.walker.ardc commentedRe-roll of patch of #18 for 10.2.6 attached.
Comment #34
rajeshreeputraCreated MR against contrib module