Bug 12616 – dojo tree component fails to render

• Status: RESOLVED
• Resolution: INVALID
• Component: New Bugs

[Craig Daniels]

I've been testing a simple JSF page with the dojo tree2 control (dojo 0.4.1).  The tree control fails to load in the WebKit nightly builds (currently using 19399) but does load correctly in the current Safari and Firefox.  The URL has the HTML output from JSF along with a screenshot showing WebKit in the back, then Firefox, then Safari (419.3) in the foreground.  I can't find any error messages in the logs and Drosera shows there are some dojo components being created in the DOM.

[David Kilzer (:ddkilzer)]

Hi Craig, the tree component loads for me your sample URL using a local debug build of WebKit r19406 with Safari 2.0.4 (419.3) on Mac OS X 10.4.8 (8N1037).

I also see all the menu items (using the sample) with WebKit nightly r19399.

Do you have any Input Managers or haxies installed (like PithHelmet, SafariStand or Saft)?

[Craig Daniels]

(In reply to comment #1)

Hmm, the HTML version is loading for me now.  I put the HTML page on the same app server (Sun v9.0) and it works, but the JSF page does not.  Very strange since the HTML is identical.  Could it be something in the response headers or a load event that isn't being triggered correctly?

Aside from enabling the debug menu, I'm not running any Input Managers or haxies.  I'm running 10.4.8 (8L2127) on a MacBook Pro.

[David Kilzer (:ddkilzer)]

(In reply to comment #2)
> Hmm, the HTML version is loading for me now.  I put the HTML page on the same
> app server (Sun v9.0) and it works, but the JSF page does not.  Very strange
> since the HTML is identical.  Could it be something in the response headers or
> a load event that isn't being triggered correctly?

It may be that some resource is not being found.  The easiest way to check this is to look at the "Activity" window from the "Window" menu for any red items when you load the JSF page.  The "hard" way is to use a packet sniffer and identify any http connections that return a 404 (or non-success) status.

> Aside from enabling the debug menu, I'm not running any Input Managers or
> haxies.  I'm running 10.4.8 (8L2127) on a MacBook Pro.

The debug menu is a must for web development and won't harm anything.  :)

[Alexey Proskuryakov]

Closing as INVALID, as the bug doesn't seem to have enough information to proceed, and we couldn't get it in over half a year. Please feel free to re-open with more detail!