WordPress.org

Make WordPress Core

Opened 9 years ago

Closed 9 years ago

#20247 closed defect (bug) (fixed)

In paging inputs, account for browsers rendering native type="number" UI

Reported by: koopersmith Owned by: nacin
Milestone: 3.4 Priority: normal
Severity: minor Version: 3.4
Component: UI Keywords: needs-patch
Focuses: Cc:

Description

Chrome has begun rendering input[type="number"] separately from input[type="text]. This results in the paging inputs being stretched wider than intended. See screenshot.

Attachments (1)

Screen Shot 2012-03-15 at 2.01.48 PM.png (10.1 KB) - added by koopersmith 9 years ago.

Download all attachments as: .zip

Change History (5)

#1 @ocean90
9 years ago

Related/Duplicate: #20217

#2 @helenyhou
9 years ago

And ryan posted almost the exact same screenshot on #17863

#3 @nacin
9 years ago

While I think the type="number" here is clever (we could even add a max using total_pages), it isn't very good UX, as you still have to hit enter to actually trigger the refresh. There's no button to click. Introducing this will only confuse people on how, after clicking things, to get to the page they chose. More at http://core.trac.wordpress.org/ticket/17863#comment:31.

I'm reverting the type="number" here for now.

#4 @nacin
9 years ago

  • Owner set to nacin
  • Resolution set to fixed
  • Status changed from new to closed

In [20198]:

Remove type='number' from list table page inputs out of a concern for UX, as well as styling issues. fixes #20247. see #17863 for further discussion.

Note: See TracTickets for help on using tickets.