WordPress.org

Make WordPress Core

Opened 9 months ago

Last modified 12 days ago

#39793 new defect (bug)

Scrolling up in the sticky post text editor does not scroll the page up to top

Reported by: elmo5 Owned by:
Milestone: 5.0 Priority: normal
Severity: normal Version:
Component: Editor Keywords: needs-patch
Focuses: accessibility Cc:

Description

In the sticky post editor, if I use arrow keys to navigate in the text mode tab (textarea#content), the page does not scroll up to the very top of the page, leaving part of the text hidden. I have to use mouse to again reveal the text. In the TinyMCE mode the scrolling works perfectly.

I attached a screenshot where I created lines of text to get the page scroll. At the bottom of the page, cursor can be seen all the time. Then, when I go and use arrow keys to scroll to the first line of the text, it only scrolls almost to the top, leaving about 6.5 lines above the scroll.

Additionally, using Ctrl+Home or Ctrl+End (on Windows) to navigate to the top or bottom of the textarea does not scroll the page.

Attachments (1)

Capture.PNG (83.8 KB) - added by elmo5 9 months ago.

Download all attachments as: .zip

Change History (20)

@elmo5
9 months ago

#1 @bhargavbhandari90
9 months ago

  • Focuses accessibility administration added
  • Keywords needs-patch added

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


8 months ago

#3 @afercia
8 months ago

  • Focuses ui administration removed
  • Milestone changed from Awaiting Review to 4.8
  • Version 4.7.2 deleted

I was able to reproduce this on Firefox and Chrome, when activating the option Enable full-height editor and distraction-free functionality. and with a very long post. From an accessibility perspective, something that needs to be fixed since there's no way to move the cursor back to the top of the post when using keyboard only.

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


6 months ago

This ticket was mentioned in Slack in #core-editor by afercia. View the logs.


6 months ago

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


5 months ago

This ticket was mentioned in Slack in #core by jeffpaul. View the logs.


5 months ago

#8 @jbpaul17
5 months ago

  • Milestone changed from 4.8 to 4.8.1

Punting to 4.8.1 per discussion in today's 4.8 rc1 bug scrub in #core.

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


4 months ago

#10 @afercia
4 months ago

Not sure if it's worth fixing this, now that all the focus is on the new editor Gutenberg, /cc @azaozz @iseulde

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


4 months ago

This ticket was mentioned in Slack in #core-editor by afercia. View the logs.


4 months ago

This ticket was mentioned in Slack in #core by jeffpaul. View the logs.


3 months ago

#14 @jbpaul17
3 months ago

  • Milestone changed from 4.8.1 to 4.9

Punting per today's bug scrub.

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


3 months ago

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


2 weeks ago

This ticket was mentioned in Slack in #core-editor by afercia. View the logs.


2 weeks ago

This ticket was mentioned in Slack in #core by melchoyce. View the logs.


12 days ago

#19 @melchoyce
12 days ago

  • Milestone changed from 4.9 to 5.0
Note: See TracTickets for help on using tickets.