Opened 16 years ago

Closed 16 years ago

Last modified 15 years ago

#1951 closed defect (fixed)

Error if no widgetId is defined

Reported by: [email protected] Owned by: bill
Priority: high Milestone:
Component: General Version: 0.4.1rc1
Keywords: Cc:
Blocked By: Blocking:


Checking out the nightly tests ( there appears the debug output:

DEBUG: dojo.widget.Parse: error: [TypeError: page has no properties, file:, line: 315]
DEBUG: widget ID collision on ID: ttab1
DEBUG: widget ID collision on ID: ttab2

The ids are unique. With another application I could produce the same error although the parse error occurred in dojo.js.

The above is the output of FF2.0; IE6 produces some other message: 'widgetId' is null or not an object. Obviously both error messages have the same effect though the message itself differs greatly. I would guess the IE message is nearer to the truth although it may be difficult to get hold of the widget with the missing widgetId. So there is still room for improvement. This is similar to #1866 it occurs also with pages not loaded remotely

Attachments (1)

TabContainerStrict.patch (656 bytes) - added by [email protected] 16 years ago.
Patch fixes the issue in test_TabStrict.html

Download all attachments as: .zip

Change History (5)

comment:1 Changed 16 years ago by [email protected]

This effect dissapiers when you declare on of the tabs selected with the attribute selectedChild (selectedTab doesn't work - quite naturaly so).

<div id="ttabs" dojoType="TabContainer" labelPosition="top" selectedChild="ttab2"
 style="width: 100%; height: 10em;" >

The basic problem is still there. This also works when no tab is selected, though I have no idea why that is or what produced this peculiar error when the depricated attribute was used.

Changed 16 years ago by [email protected]

Attachment: TabContainerStrict.patch added

Patch fixes the issue in test_TabStrict.html

comment:2 Changed 16 years ago by bill

Milestone: 0.4.1
Owner: changed from anonymous to bill
Status: newassigned

Ah, it's just because selectedChild has an illegal value ("tab2" rather than "ttab2"). Confusing error message though.

comment:3 Changed 16 years ago by bill

Resolution: fixed
Status: assignedclosed

(In [6662]) Fixes #1951

comment:4 Changed 15 years ago by (none)

Milestone: 0.4.1

Milestone 0.4.1 deleted

Note: See TracTickets for help on using tickets.