#221 new

BUG: IE7 and 8 reports error on inPlaceEditor when highlightcolor specified to transparent

Reported by Tibee | July 15th, 2009 @ 02:36 PM

Browser: Internet Explorer 7 or 8
ProtoType: 1.6.1 RC3
Script.aculo.us version: 1.8.1
Control: inPlaceEditor


line: 914:

onEnterHover: function(ipe) {
  ipe.element.style.backgroundColor = ipe.options.highlightColor;
  if (ipe._effect)

If highlightcolor is set to 'transparent', IE reports error: 'Invalid property value backgroundColor'.
If highlightcolor is set to any certain color, i.e. '#f0f0f0', there is no error.

If I modify the source to use element.bgColor instead of element.style.backgroundColor, IE reports no errors.

IE reports the error on the ProtoType setStyle function, when it tries to set element.style['backgroundColor'] property.

For IE JavaScript debugging I use Microsoft Visual Web Developer 2008 Express.

Comments and changes to this ticket

  • Krish

    Krish September 6th, 2009 @ 06:36 PM

    Hi Tibee,
    Do you have a patch for this? I just discovered setting the highlight color to none breaks the inplace editor on IE and is the root cause of a major problem for me. It completely holds up my application since IE cannot continue with background changes once this occurs.

    A workaround would be greatly appreciated.

    "If I modify the source to use element.bgColor instead of element.style.backgroundColor, IE reports no errors."

    Tibee, Could you post this fix?

    Thanks in advance

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

script.aculo.us is an open-source JavaScript framework for visual effects and interface behaviours.
<br/><b>Source available from github</b>
The Git repository resides at:
<a href="http://github.com/madrobby/scriptaculous">http://github.com/madrobby/scriptaculous</a>
<br/>Check out the current development trunk with:
<code>git clone git://github.com/madrobby/scriptaculous.git</code>
<br/>As <b>script.aculo.us 1.xx is feature-frozen</b>, this development trunk is for <b>bugfixes only</b>.
<br/>New development should happen only for
<b>script.aculo.us 2</b>.
<br/><b>Creating a bug report</b>
When creating a bug report, be sure to include as much relevant information as possible. Post a an example that shows off the problem. Preferably, <b>alter the unit tests</b> and show through either changed or added tests how the expected behavior is not occuring.

People watching this ticket