Opened 3 years ago
Closed 16 months ago
#55338 closed enhancement (wontfix)
Twenty Eleven: Invalid use of display and float together in style.css file
Reported by: | kajalgohel | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.2 |
Component: | Bundled Theme | Keywords: | has-patch needs-testing close |
Focuses: | css | Cc: |
Description
In the theme Twenty Eleven, there is an invalid use of float and display inline-block together in the CSS style sheet.
.indexed.format-image div.entry-meta { display: inline-block; float: left; width: 35%; }
Attachments (7)
Change History (22)
#2
@
3 years ago
- Component changed from Themes to Bundled Theme
- Milestone changed from Awaiting Review to 6.0
- Summary changed from Invalid use of display and float together in style.css file to Twenty Eleven: Invalid use of display and float together in style.css file
#3
@
3 years ago
Hello and thank you for opening this ticket and for the patch!
However, I reproduced the context (image post format and blog/archive page) and it looks like we shouldn't remove this since it applies to both .entry-meta
divs. Removing this CSS declaration breaks the design of the meta box on my side.
See the animated screenshot below
#5
@
3 years ago
- Use Twenty Eleven on your website
- Publish a post with the "Image" post format
- Go to front-end
- Inspect the
entry-meta
zone (see animated screenshot above)
#7
@
3 years ago
- Focuses css added
- Keywords needs-design-feedback removed
Browsers compute floated inline-block elements as block anyway, so I do not think a change is necessary. However, inline-block
only needs to apply to the un-floated second .entry-meta
div.
#9
@
3 years ago
- Keywords close added
I feel a bit hesitant about this change. Does it solves any known issue? Does it helps passing CSS validation? Does it brings more "quality" to the theme?
If we can't find any relevant answer to these question, I'd suggest to close the ticket as wontfix
.
I feel a bit concerned about breaking things for people who override the default behavior of this theme using a child theme, without solving any identified issue.
#10
@
3 years ago
I lean toward closing, or at least I recommend against committing my earlier patch.
The W3C CSS Validator only labels the negative padding (#46771) and the device-width
entries as errors, and the float/display combination does not appear in the warnings list either.
Both CSS Portal and Code Beautify alert about the floating under the message "Require properties appropriate for display" (one identifies it as an error, the other calls it a warning).
I took another look at 55338.2.patch. As long as the vertical alignment is set, removing the float and reducing the width might be worth considering. Without floating, the two inline-block
elements can have a slight space between them that is not always there on smaller screens (depending on content).
#11
@
3 years ago
Re the close
discussion, #55362 is very similar so it seems sensible to make the same decision for both.
This ticket was mentioned in Slack in #core-themes by peterwilsoncc. View the logs.
2 years ago
#13
@
2 years ago
- Milestone changed from 6.0 to 6.1
With 6.0 Beta 1 released yesterday, I'm moving this ticket, and #55362 to the 6.1 milestone pending further discussion on whether this change is desired.
#15
@
16 months ago
- Milestone Future Release deleted
- Resolution set to wontfix
- Status changed from new to closed
The proposal to retire old themes is not finalized yet, but I'll count that as the decision to close these two minor enhancement tickets.
display: inline-block property is removed.