Make WordPress Core

Opened 20 years ago

Closed 20 years ago

Last modified 20 years ago

#3854 closed defect (bug) (fixed)

text formatting script shouldn't treat scripts as text blocks

Reported by: Denis-de-Bernardy Owned by: rob1n
Priority: low Milestone: 2.2
Component: General Version: 2.1.1
Severity: normal Keywords: has-patch commit
Cc: Focuses:

Description

Attachments (2)

3854.diff​ (962 bytes ) - added by Nazgul 20 years ago.
3854.2.diff​ (944 bytes ) - added by rob1n 20 years ago.
Take out script, object and param

Download all attachments as: .zip

Change History (13)

@Nazgul
20 years ago

#1 @Nazgul
20 years ago

  • Component Administration → General
  • Keywords has-patch added
  • Version → 2.1.1

#2 @foolswisdom
20 years ago

  • Milestone 2.1.3 → 2.2

#3 @rob1n
20 years ago

+1. <script> tags can be used inline or as a block, though if it's used inline the output has to be inline, too. But that's up to the user.

#4 @Otto42
20 years ago

The object element has the same problem. It shouldn't get extra spaces added around it because it can be inline or block too. Correct?

#5 @rob1n
20 years ago

Yes. Both <object> and <script> *can* be used as inline elements.

#6 @rob1n
20 years ago

  • Owner changed from anonymous to rob1n

#7 @rob1n
20 years ago

  • Keywords commit added

Patch looks good, too.

@rob1n
20 years ago

Take out script, object and param

#8 @rob1n
20 years ago

I'm just going to fix this for <script>.

#9 @rob1n
20 years ago

  • Resolution → fixed
  • Status new → closed

(In [5223]) Don't autop <script> blocks. Props Nazgul. fixes #3854

#10 @Otto42
20 years ago

This really needs to be fixed for objects too. The current editor has weirdness when you insert code from places like Youtube or google video or what have you.

#11 @rob1n
20 years ago

(In [5262]) Don't treat object and param as block elements in wpautop. fixes #3854

Note: See TracTickets for help on using tickets.