Remove redundant type attributes from script and style tags

[solarissmoke]

Now that the admin is using the HTML5 doctype everywhere, the type="text/javascript" and type="text/css" attributes on script and style tags are unnecessary (if they weren't anyway), and I think they can be safely removed to trim a few hundred bytes from core. Should be a simple search and replace exercise.

[azaozz]

We have to confirm that first for older mobile browsers. They still might be needed for some. Also the //<![CDATA[ bits inside of <script> are not needed.

[tw2113]

removed script CDATA tags. Left script types on though.

[tw2113]

forgot wp-includes

[tw2113]

I did my best to stick to just <script></script> blocks. I didn't edit any of them in RSS/XML based feed files.

[SergeyBiryukov]

HTML comment tags in wp-admin/includes/file.php can also be removed:
​http://core.trac.wordpress.org/browser/tags/3.5.1/wp-admin/includes/file.php#L969

[SergeyBiryukov]

Fixing the keyword for reference.

[SergeyBiryukov]

Related: #25637

[wonderboymusic]

In 31034:

Inline <script>s that are only printed in the admin for pages that are served with the HTML5 doctype absolutely do not need CDATA comments.

Props tw2113 for the initial patch.
See #18788.

[wonderboymusic]

type is optional in HTML5, not required. I don't think it hurts to keep it.

[retlehs]

Replying to wonderboymusic:

type is optional in HTML5, not required. I don't think it hurts to keep it.

Since it's optional, why keep it?

[AramZS]

Replying to retlehs:

Replying to wonderboymusic:

type is optional in HTML5, not required. I don't think it hurts to keep it.

Since it's optional, why keep it?

Always better to be more specific than less, right?

[solarissmoke]

Replying to AramZS:

Always better to be more specific than less, right?

The HTML5 specification is explicitly clear about what a missing type attribute means, so specificity isn't an issue. Removing it means less bloat and easier code to read.

[retlehs]

Reopening because type still isn't removed.

[DrewAPicture]

@wonderboymusic: Any idea what's left here? Letting this ride into Beta 1, see [31034].

[helen]

Replying to retlehs:

Reopening because type still isn't removed.

Curious if anybody tried checking into that on older browsers, per the first comment from azaozz.

[retlehs]

Replying to helen:

Curious if anybody tried checking into that on older browsers, per the first comment from azaozz.

Is there a list of supported browsers that need to be tested? It's fine in IE8. It's probably fine in IE7, but I don't have a VM with it up and running yet.

(Not sure if any of this even matters considering a HTML5 doctype is used)

[DrewAPicture]

Per consensus in the above-linked Slack discussion, punting this to a future release.

[wonderboymusic]

comment:13

[sephr]

This change breaks XHTML support in many areas. CDATA sections are not redundant for people emitting strict XHTML5 served as application/xhtml+xml, like myself.

I've been emitting an XHTML5 theme ever since 2009, so I depend on the continued support of valid syntax.

[sephr]

Replying to wonderboymusic:

In 31034:

Inline <script>s that are only printed in the admin for pages that are served with the HTML5 doctype absolutely do not need CDATA comments.

Props tw2113 for the initial patch.
See #18788.

CDATA has nothing to do with the HTML5 doctype in the first place... It has to do with content type. Using the HTML5 doctype does not magically force an XHTML document into allowing invalid XHTML syntax.

[sephr]

To clarify, all of the wp-admin/ changes are fine. This only broke XHTML support when @solarissmoke added wp-includes/.

wp-includes is not limited to the admin interface, and throughout this issue it seems like the intention was only to remove CDATA in the admin interface.

Issue description: "Now that the admin is..."

@wonderboymusic's comment "Inline <script>s that are only printed in the admin for pages..."

The first patch should have been accepted, but not the second one.

[airathalitov]

Issue is still actual.

Can you delete type='text/javascript' and type='text/css' tags by default?

[SergeyBiryukov]

Replying to airathalitov:

Can you delete type='text/javascript' and type='text/css' tags by default?

Follow-up: #42804