[CONTEDIT-7] Polish text-editing mechanics and quirks of Article Editor Created: 10/Feb/17  Updated: 02/Mar/17  Resolved: 01/Mar/17

Status: Closed
Project: Content Editor
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Improvement Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by CONTEDIT-6 Seamlessly add, edit and jump between... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Initial Article editor
Sprint: Basel 85
Story Points: 5

 Description   
  • Empty text blocks collapse to 0 height (i.e. disappear for user) when not focused - they should be detached completely.
  • Splitting (pressing Enter) when the cursor is at the beginning of a block/textarea produces confusing results - an empty/collapsed blocks is created, tab-index is seemingly lost. Instead the contents of the current blocks should be pushed into a new block and text input should stay at the current one.
  • In FF when a new block is created as a result of e.g. block splitting - the text input seems to be stalled even though the cursor is visible and the element is seemingly ready for editing.
  • Text blocks should become editable as soon as they're focused - no additional press of RETURN key should be required.
  • Arrow navigation between blocks might be block when going towards the bottom block (down arrow) - cause by sloppy estimation of the caret position.

(also check comments)



 Comments   
Comment by Philip Mundt [ 15/Feb/17 ]

Some new issues were found by creichenbach during QA of the first PR of this issue:

PIQA:
Unfortunately, I found a few new problems now:

  • In Firefox:
    • Focus seems to vanish more often
    • Multiple blocks visually indicate focus at the same time
  • In Chromium:
    • Empty text blocks are sometimes removed, sometimes not
    • Down arrow to jump to next block doesn't work for empty blocks (up works though)
Comment by Philip Mundt [ 15/Feb/17 ]

I also found that when selecting a new text block from the block picker, the text defaults to null.

Comment by Philip Mundt [ 22/Feb/17 ]

Block-picker is not clickable when using a FieldSetBlock.

Generated at Mon Feb 12 00:16:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.