guardian/scribe

Chrome: Pasting from Word into pristine editor creates extraneous P element and misplaces the caret

Open

#137 opened on Apr 30, 2014

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (3,516 stars) (265 forks)batch import
browser inconsistencyformattershelp wanted

Description

image

Pasted into a pristine editor:

image

  • The caret is before the "3" when it should be after.
  • There is an extraneous P element containing only whitespace after the paragraph containing "2".

To do: create isolated case.

Introduced by https://github.com/guardian/scribe/pull/131.

Contributor guide

Tech stack
javascripthtmlcss
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
familiarity with Scribe codebaseunderstanding of rich text editingknowledge of clipboard APIs
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Examine the changes introduced in PR #131 (https://github.com/guardian/scribe/pull/131) that caused this regression. Look at the paste handling code in Scribe to identify where an extraneous P element is created after pasting from Word in Chrome. Additionally, debug the caret positioning logic to ensure the caret is placed after the pasted content. The issue suggests creating an isolated test case to reproduce the behavior.