Make WordPress Core

#56697 closed defect (bug) (worksforme)

File editor: extra padding on sides

Reported by: muneeb09's profile muneeb09 Owned by:
Milestone: Priority: normal
Severity: normal Version: 6.0.2
Component: Administration Keywords: reporter-feedback needs-patch
Focuses: ui, accessibility, css, administration Cc:

Description

We are facing an issue where there is extra padding on right and bottom side of editor which is overlapping the button and file directory, making that area non-clickable.

Attachments (1)

Screenshot (13).png (535.7 KB) - added by muneeb09 22 months ago.
Here is the code and screenshot of extra padding of editor.

Download all attachments as: .zip

Change History (7)

@muneeb09
22 months ago

Here is the code and screenshot of extra padding of editor.

#1 @sabernhardt
21 months ago

  • Component changed from Editor to Administration
  • Focuses accessibility css administration added
  • Keywords reporter-feedback needs-patch added; extra-padding removed
  • Summary changed from Extra Padding on Sides of Editor. to File editor: extra padding on sides

Hi and thanks for the report!

Which browser(s) and operating system did not allow you to click the links? I did not have trouble clicking them in Firefox 105 or Chrome 106 (with Windows 10 Home).

The CodeMirror-scroll element has a 30-pixel bottom padding, and it extends about the same distance to the right (in both LTR and RTL language directions). However, the .CodeMirror container hides its overflow, which should prevent covering part of the links.

I would like to investigate switching sides so that the visual order matches the DOM order, though that could transfer any clicking problems faced in left-to-right languages to the right-to-left languages.

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


21 months ago

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


20 months ago

#4 @ryokuhi
20 months ago

Hello @muneeb09,

we reviewed this ticket again today during the Accessibility Team's weekly bug scrub. Probably you don't know how WordPress Trac works, but when the reporter-feedback keyword is added to a ticket, it means that we need extra information from the person who reported the bug.

Can you please provide us with the information on the environment you're experiencing this issue with?
All of the following will help us.

  • Operating System (and version)
  • Browser (and version)
  • WordPress version
  • Active theme
  • Active plugins

Also, when you disable all plugins, do you still experience the same bug as when all plugins are active? If disabling a plugin makes the bug disappear, then the bug is probably due to the plugin itself and should be reported to the plugin creator, and not with WordPress Core itself.

If you don't provide us with these pieces of information, that we will close this ticket, which can be reopened at any time if needed.

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


16 months ago

#6 @joedolson
16 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to worksforme
  • Status changed from assigned to closed

Thanks for reporting! With no additional information to explore, we're going to close this ticket. Feel free to reopen the ticket if you have more information to share.

Note: See TracTickets for help on using tickets.