Ticket #3638 (closed defect: fixed)

Opened 2 years ago

Last modified 6 months ago

img attributes ALL CAPS when using new 2.1 VRE w/ Opera

Reported by: HandySolo Assigned to: Andy
Priority: low Milestone: 2.5
Component: TinyMCE Version: 2.1
Severity: normal Keywords: opera image uploader
Cc:

Description

Just noticed this with a fresh install of 2.1. First time trying admin stuff with Opera 9.10/XP.

Added an image using the updated image uploader and all the attributes are displayed in the "Code" view as ALL CAPS. For example: 

<a TITLE="e" HREF="http://example.com/wp-content/uploads/2007/01/e7401.jpg">
<img ALT="e" SRC="http://example.com/wp-content/uploads/2007/01/e7401.thumbnail.jpg" />
</a>

Even the hyperlink attributes get capitalized. For what it is worth, doing a normal hyperlink is ok, just when it comes via the image uploader.

If I open the same post with Firefox, and then go to "Code" tab, the attributes are fine (lower-case).

TinyMCE issue? Opera issue?

Change History

01/25/07 19:51:47 changed by Znuff

  • owner changed from anonymous to Znuff.
  • status changed from new to assigned.

It's confirmed from several other users on irc://irc.freenode.net/wordpress

01/25/07 21:02:23 changed by markjaquith

  • owner changed from Znuff to Andy.
  • status changed from assigned to new.

Andy, your ticket. Sounds like a TinyMCE issue.

02/21/07 16:06:50 changed by Nazgul

  • milestone changed from 2.1.1 to 2.1.2.

02/22/07 07:09:00 changed by rob1n

  • component changed from Administration to TinyMCE.

I've verified this with SVN trunk. Identical actions on Firefox result in attributes with proper cases, while Opera has them all uppercase. I would believe this is an Opera issue, but either way TinyMCE should probably work around it.

03/16/07 09:13:05 changed by hakre

Attributes are made UPPERCASE while switching between the Code and Visual Pane as well. So this must be javascript related. I've checked TinyMCE Documentation Wiki but could not find any option that is defining this behaviour. Maybe someone else is better in seraching there.

According to their FAQ, TinyMCE should produce XHTML conform code. (http://wiki.moxiecode.com/index.php/TinyMCE:FAQ#Why_does_TinyMCE_strip_away_attributes_or_tags_from_my_source.3F) Taking this for granted means, that not TinyMCE is making the attributes uppcercase but WP is since uppercase attributes like HREF or TITLE aren't XHTML valid.

03/16/07 09:27:46 changed by hakre

Some more Infos:

Opera 9 Support with TinyMCE is named as (WinXP / MacOSX):

Opera 9 OK(1) OK(1)

Where (1) is for Partially working. (They do not have Linux Support in their chart, how lame). So let's assume these are k4ckn00bs and Opera 9 is just simply not supported well by TinyMCE. This does not answer the question completely wether this is a TinyMCE or WP Problem but I tend for TinyMCE and TinyMCE should fix this. Maybe someone should call their professional support and ask for fixing this forever?

Source: http://wiki.moxiecode.com/index.php/TinyMCE:Compatibility

03/16/07 18:32:29 changed by foolswisdom

  • milestone changed from 2.1.3 to 2.2.

03/27/07 17:00:01 changed by foolswisdom

  • milestone changed from 2.2 to 2.3.

05/18/07 04:06:12 changed by HandySolo

Some testing with 2.2 and Opera 9.20 has me cautiously optimistic. At first blush, the upper-casing issue is now gone.

05/18/07 04:11:39 changed by HandySolo

sorry,scratch that. All was cool until I actually uploaded an image (lost my mind for a moment there). The issue persists in that scenario.

Apologies.

05/26/07 09:15:56 changed by Gesu

Same issue here (Opera 9.21, Win XP, WP 2.2), and I would add that with Opera there're also some problems with word wrapping. Sometimes the editor just starts a new line, or it continues on the same one even if text goes over the limit, instead of starting a new line. I thought it could be reported here, instead of opening a new ticket (I still can create it, if someone thinks it's the case).

09/18/07 18:15:53 changed by foolswisdom

  • milestone changed from 2.3 to 2.4.

02/08/08 08:36:53 changed by hakre

Can confirm that the bug is still in with 2.3.3 and using opera. Shouldn't there be a tinymce option to tell tinymce to use lowercase attribute names?

02/08/08 16:29:14 changed by lloydbudd

hakre, thanks for confirming this. This issue is unlikely to be resolved in a maintenance release. Do you have the resources to test if the issue is still present on trunk?

03/06/08 11:59:37 changed by azaozz

  • status changed from new to closed.
  • resolution set to fixed.

Opera wasn't fully supported by TinyMCE 2.x, but works well in 3.0