Make WordPress Core

Opened 5 years ago

Last modified 5 years ago

#46943 new defect (bug)

Settings ->Discussion bad view dropdown in mobile version

Reported by: ketanumretiya030's profile ketanumretiya030 Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Comments Keywords: settings-api needs-design
Focuses: ui, administration Cc:

Description

Settings ->Discussion all dropdown are bigger on the responsive view. so need to make it size small same as desktop view and content align proper same as desktop view.

Attachments (2)

on_mobile_view_badview.png (71.1 KB) - added by ketanumretiya030 5 years ago.
Mobile dropdown view
on_desktop_view_proper.png (86.2 KB) - added by ketanumretiya030 5 years ago.
Desktop view

Download all attachments as: .zip

Change History (7)

@ketanumretiya030
5 years ago

Mobile dropdown view

@ketanumretiya030
5 years ago

Desktop view

#1 @SergeyBiryukov
5 years ago

  • Component changed from General to Comments
  • Focuses ui administration added

#2 @desrosj
5 years ago

  • Keywords needs-design-feedback added

#3 @afercia
5 years ago

  • Keywords settings-api added

Related: #31354 and #31356.

In the Discussion Settings page, form controls inline with text are not ideal for many reasons, including accessibility. See also the tickets above.

Ideally, this page should be refactored to be more like a standard form. A "linearized" form would help both the responsive design and accessibility, as many assistive technologies users perceive the content in a linearized fashion.

Instead, I'm not sure the responsive styles should be changed. All the form controls in WordPress become bigger on small screens, for good reasons.

This ticket was mentioned in Slack in #design by karmatosed. View the logs.


5 years ago

#5 @karmatosed
5 years ago

  • Keywords needs-design added; needs-design-feedback removed

I am going to put a needs design on this, however, this needs leading from a11y team as to what could be the best approach here first, working with a designer.

Note: See TracTickets for help on using tickets.