I thought DHTML would only give a fatal error for referencing a non- existent property. Maybe you just need to spiff up the class to actually declare all its properties (and initialize them to `null`)?
On 2006-08-08, at 21:23 EDT, Henry Minsky wrote: > I am in the process of merging some swf and DHTML code in the LFC, > and have > a question about the following > > > The lztest package is actually starting to work in DHTML, but some > of the > tests on data elements are failing. The usual > failure mode is an error in a data API method with an unbound slot > such as > "parentNode", which is an artifact of the test case which constructs > orphan nodes for test purposes, so they generally don't have all > their slots > bound. This silently fails in swf, but causes hard errors > in DHTML interpreters. > > The question is whether I should modify the tests to create more fully > instantiated nodes, or whether I should put more error > checking into all the API method to check for null values on slots > before > referencing properties on them or sending events. The > error checking could have 'if ($debug)' clauses to warn about > uninitialized > slots, or it could silently proceed in the way that > swf code does now. Anyone have an opinion on this? The only reason > not to > put checks in would be that it could cause > some performance penalty, and will also bloat the code some more. > > > -- > Henry Minsky > Software Architect > [EMAIL PROTECTED] > _______________________________________________ > Laszlo-dev mailing list > [email protected] > http://www.openlaszlo.org/mailman/listinfo/laszlo-dev _______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
