Make WordPress Core

Opened 12 years ago

Closed 12 years ago

#20217 closed defect (bug) (fixed)

Webkit + Trunk = Publish immediately format Fugliness

Reported by: ipstenu's profile Ipstenu Owned by: azaozz's profile azaozz
Milestone: 3.4 Priority: normal
Severity: major Version: 3.4
Component: General Keywords:
Focuses: Cc:

Description

Chrome
http://f.cl.ly/items/0M3q1f3H1Z3q3H0Y0u1v/Screen%20Shot%202012-03-11%20at%20%2011%20Mar%20-%205.14.10%20PM.png

Safari
http://f.cl.ly/items/1P170J442V0v1E0c1i1x/Screen%20Shot%202012-03-11%20at%20%2011%20Mar%20-%205.33.59%20PM.png

Firefox
http://f.cl.ly/items/2T3b18230o2j2V3o260I/Screen%20Shot%202012-03-11%20at%20%2011%20Mar%20-%205.37.25%20PM.png

Looks fine on Firefox. Looks horrific on Chrome and Safari. Which makes this likely a webkit issue, if I'm not smoking crack. If I 'fix' it for chrome, it looks horrid on Firefox and it's not fixed really for Safari.

This was fine on Friday, which was the last time I remember checking. Still fine today on 3.3 on all three browsers.

Using a Mac.

Attachments (4)

20217.patch (1.1 KB) - added by azaozz 12 years ago.
chrome-17.jpg (16.3 KB) - added by azaozz 12 years ago.
firefox-10.jpg (15.9 KB) - added by azaozz 12 years ago.
opera-11.61.jpg (16.2 KB) - added by azaozz 12 years ago.

Download all attachments as: .zip

Change History (15)

#1 @nacin
12 years ago

Caused by #17863.

#2 @azaozz
12 years ago

Yes, seems like a webkit bug. The problem is that the fields aren't wide enough to accommodate webkit's up/down arrows that for some unknown reason are not placed outside of the field's "width" calculation.

#3 @azaozz
12 years ago

  • Component changed from Editor to General

#4 @ocean90
12 years ago

  • Milestone changed from Awaiting Review to 3.4

Opera

http://f.cl.ly/items/3J2c163j301O3J3B0p0v/Bildschirmfoto%202012-03-12%20um%2015.07.08.png

And Firefox hasn't implemented it yet, see https://bugzilla.mozilla.org/show_bug.cgi?id=344616

@azaozz
12 years ago

@azaozz
12 years ago

@azaozz
12 years ago

@azaozz
12 years ago

#5 @azaozz
12 years ago

Seems there are two options: either remove type="number" or make these fields wider. 20217.patch is an attempt at the second, it changes it to:




#6 follow-up: @nacin
12 years ago

When making these fields wider, we're forced to bump the time to the next line. This feels particularly lame. I'd rather we implement a date picker; this really isn't doing much to help things.

#7 @Ipstenu
12 years ago

A date (and time) picker would be a lot better. +1 nacin :)

#8 @ocean90
12 years ago

Date picker is #7665.

#9 in reply to: ↑ 6 @azaozz
12 years ago

Replying to nacin:

Yeah, agree it doesn't look well. The problem with date pickers is they all have inherently bad UX: picking a date in the same month is nice and fast, a date 3 months away adds 3 clicks, a date 10 months away ads 10 clicks... Also I haven't seen a nice date + time picker, meaning we will have to make one ourselves.

Perhaps for now it would be best to revert type="number" for these fields.

#10 @ryan
12 years ago

Revert sounds good.

#11 @azaozz
12 years ago

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

In [20217]:

Revert type="number" for the date/time fields as it introduces UI/styling issues, fixes #20217, see #17863

Note: See TracTickets for help on using tickets.