#90 new
hanguofeng

Controls inPlaceCollectionEditor error in IE

Reported by hanguofeng | September 18th, 2008 @ 05:03 PM

Hi,I have a code just like:



        <li>Term: <p id="course_term">two</p></li>
        <li>Place: <span id="course_place">blabla</span></li>
        <script>
            new Ajax.InPlaceCollectionEditor('course_term', '__APP__/Course/PersonalData',{collection: [[0,'one'],[1,'two'],[2,'three']]});
            new Ajax.InPlaceEditor('course_place', '__APP__/Course/PersonalData');
        </script>

InPlaceEditor works well in both IE and FF,but InPlaceCollectionEditor doesn't work well in IE.

When I click the "two" text ,IE reports the object doesn't have such a method,I found it's the falut of :


this._controls.editor.update('');

in line 839 in controls.js

I fixed this by:



    try {
        this._controls.editor.update('');
    }
    catch (ex) {
    }

and then it works.

Comments and changes to this ticket

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.

Referenced by

Pages