[wp-trac] [WordPress Trac] #11394: Image shortcode
WordPress Trac
wp-trac at lists.automattic.com
Fri Apr 9 16:33:30 UTC 2010
#11394: Image shortcode
-----------------------------+----------------------------------------------
Reporter: caesarsgrunt | Owner:
Type: feature request | Status: new
Priority: normal | Milestone: 3.1
Component: Media | Version: 2.9
Severity: normal | Keywords: needs-patch dev-feedback
-----------------------------+----------------------------------------------
Comment(by Otto42):
Replying to [comment:36 caesarsgrunt]:
> There are already attributes duplicated between the {{{[caption]}}}
shortcode and the {{{<img>}}} tag. If we kept the {{{[caption]}}}
shortcode separate, then these would still have to be duplicated. On the
other hand, if we were to give the {{{[image]}}} shortcode a {{{caption}}}
attribute, then we needn't wrap it in the {{{[caption]}}} shortcode and
the attributes wouldn't need to be duplicated.
>
> In my mind the current system is very messy, and an {{{[image]}}} or
{{{[media]}}} shortcode would allow us to tidy it up immensely.
Ugh, absolutely not. Caption is separate from the image for a reason, and
it should stay that way.
Look, the image is just the image. But the caption is the box surrounding
the image. They are separate in style and display and everything else. The
caption shortcode surrounds the image because that's the way it works on
the page itself.
If I was to simply delete all shortcodes, then I would still want my img
html to be in there. Remember, post content is not confined to being
displayed on the website. It's also in feeds, it can be seen in Google
Reader, it could be pulled into other things... Shortcodes violate this
principle of one-content-multiple-displays, but they tend to do so in a
minor and manageable way. If we expand shortcodes to actually *being*
content, then we change that dynamic.
I'm -1 to this ticket now, if we're talking about making the media handled
by a shortcode. I want my content to be at least mostly free of being
generated by the WordPress core code. I'd rather not have to process it
through WordPress just to make it capable of being displayed elsewhere.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/11394#comment:37>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list