Skip to content

Conversation

@Borreg0
Copy link
Contributor

@Borreg0 Borreg0 commented Jan 28, 2026

Resolves #5782

@Elblinator Elblinator removed their assignment Jan 29, 2026
// After that, the document should stay as it is. Hence, we remove the ol-colliding-change class
// from the holder element to the comment.
if (el.classList.contains(`os-colliding-change-comment`)) {
if (!el.hasAttribute(`data-change-is-colliding`)) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The purpose of this was to prevent running the procedure on an input that was already processed.
The comment should also be updated to reflect that attributes are now added instead of classes.

Suggested change
if (!el.hasAttribute(`data-change-is-colliding`)) {
if (el.hasAttribute(`data-comment-change-is-colliding`)) {

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Borreg0 Not fully resolved.

@bastianjoel bastianjoel assigned Borreg0 and unassigned bastianjoel Jan 30, 2026
Borreg0 and others added 2 commits January 30, 2026 10:25
…e-recommendations/services/motion-diff.service/motion-diff.service.ts

Co-authored-by: Bastian Rihm <[email protected]>
…e-recommendations/services/motion-diff.service/motion-diff.service.ts

Co-authored-by: Bastian Rihm <[email protected]>
@Elblinator Elblinator removed their assignment Jan 30, 2026
@bastianjoel bastianjoel assigned Borreg0 and unassigned bastianjoel Jan 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Motion: conflict view in editorial view is missing

3 participants