Current situation could do with some work:

| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 2488464-shiny-date-contrib.patch | 1.14 KB | sam152 |
| #1 | Screen Shot 2015-05-14 at 3.42.14 pm.png | 13.26 KB | sam152 |
| Screen Shot 2015-05-14 at 3.33.36 pm.png | 20.54 KB | sam152 |
Current situation could do with some work:

| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 2488464-shiny-date-contrib.patch | 1.14 KB | sam152 |
| #1 | Screen Shot 2015-05-14 at 3.42.14 pm.png | 13.26 KB | sam152 |
| Screen Shot 2015-05-14 at 3.33.36 pm.png | 20.54 KB | sam152 |
Comments
Comment #1
sam152 commentedAfter:
Comment #2
dudenhofer commentedFirst off, thanks for the patch. But there are a few things that I'm not sure of about this one. This is overriding classes like "date-no-float" from the date module... maybe this should be applied to the date module itself? Or figure out why there are no-float classes before we override them? Also, this only applies to the default date field type - do we want it to apply to the Unix timestamp and the ISO format? Also if the "Show end date" checkbox is enabled, it doesn't look so nice.
I'm not against this, just want to make sure it's not going to mess something else up, and we keep it consistent.