#60 √ resolved
aek

parent option bug in 3.1, Critical

Reported by aek | November 21st, 2011 @ 05:27 PM | in 3.1 (closed)

I found a bug in Jxlib 3.1b2 introduced by a change in mootools-core Class.
The parent option is used in Jxlib widgets to get the domObj added to the parent if there is an option parent specified. The parent option is only check for exist and now mootools add this option for us when calling to initialize method of the Class.

This is the line that do the trick at line 3224 of mootools-core.js version: 1.4.1
var value = (this.initialize) ? this.initialize.apply(this, arguments) : this;

The parent option get added as a function because it' is part of the prototype of the class. It's defined as part of the prototype of the class at line 3231 of mootools-core.js version: 1.4.1 and the function parent is defined at line 3236

I think that Jxlib need to change the option property used to identify the parent to be added to. Could be 'idParent' or 'parentId' or whatever name that do not enter in conflict with mootools.

I discover this using a grid example, the options of the grid had a property parent that I don't put in there

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 »

Shared Ticket Bins

People watching this ticket