[wp-trac] Re: [WordPress Trac] #10269: wysiwyg bug with shortcodes
WordPress Trac
wp-trac at lists.automattic.com
Fri Jun 26 06:41:32 GMT 2009
#10269: wysiwyg bug with shortcodes
--------------------------------+-------------------------------------------
Reporter: Denis-de-Bernardy | Type: defect (bug)
Status: closed | Priority: low
Milestone: 2.9 | Component: Formatting
Version: 2.8 | Severity: minor
Resolution: wontfix | Keywords: has-patch wpautop
--------------------------------+-------------------------------------------
Changes (by azaozz):
* status: reopened => closed
* resolution: => wontfix
Comment:
Replying to [comment:6 dd32]:
> I'm not sure what the deal should be with this, I mean, Having 2
shortcodes after one another is a completely legit setup, and i'm not sure
if they should have to auto-wrap themselves in a {{{<p>}}}.. Afterall, the
user may want to use it inline.
Exactly, shortcodes shouldn't be force-wrapped in block elements. Think
there was a long discussion about a year ago whether to process shortcodes
before or after wpautop which is related to this.
It doesn't make any difference how they are displayed in the editor as
putting a shortcode on a new line wouldn't wrap it in <p> anyways and this
is the correct behavior.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/10269#comment:9>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list