#23745 closed enhancement (wontfix)
Twenty Thirteen: Simplify responsive images
| Reported by: | obenland | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | Bundled Theme | Version: | 3.6 |
| Severity: | normal | Keywords: | has-patch |
| Cc: | Focuses: |
Description (last modified by )
I think we could lose a lot of code for responsive images by being less selective. Themes like Able have proven it's sufficiency.
Attachments (1)
Change History (5)
#3
@
13 years ago
The main reason we can't do this is because of user-generated markup in posts/pages. Users can change the width/height directly in their markup, and if we force height: auto; on those images their modifications won't work correctly.
That's why for height we target WP-generated class values specifically.
Also, a general selector would try to do this for all images in the site, like those added by a plugin. A "Like" button, for example, from Jetpack. That could lead to lots of unintended consequences.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
I prefer not to generalize this, we've tested the existing styles extensively in previous default themes and they work well.
I'd vote "wontfix".