PRO USERS, to ensure 'PRIORITY SUPPORT' make sure that your ASAP account is "tagged" when you file the request.
Click here for instructions on how to tag your account.
returns null, but the expected behavior is to receive an object of style properties.
The attached file demonstrates the bug. You can uncomment out the commented lines to see how it would work in a browser (Firefox) instead of a runat=server section.
In a runat=server script in a onserverload callback, asking for:
node.ownerDocument.defaultView.getComputedStyle(node, null);
returns null, but the expected behavior is to receive an object of style properties.
The attached file demonstrates the bug. You can uncomment out the commented lines to see how it would work in a browser (Firefox) instead of a runat=server section.
This bug currently prevents the Dojo Toolkit from working in Aptana:
http://www.dojotoolkit.org/forum/dojo-core-dojo-0-9/dojo-core-support/running-dojo-1-2-aptana-jaxer
As things are now, we don't do any rendering within Jaxer, which in turns means we won't have style information, unfortunately. I'm moving this to 1.x since we're about to release 1.0. Aptana can revisit this ticket after that release to determine the feasibility and extend of supporting this feature.
Kevin Lindsey - 02/Oct/08 01:34 PM Hi James,
As things are now, we don't do any rendering within Jaxer, which in turns means we won't have style information, unfortunately. I'm moving this to 1.x since we're about to release 1.0. Aptana can revisit this ticket after that release to determine the feasibility and extend of supporting this feature.
Thanks,
Kevin
Bug
Reviewed
Unprioritized
getComputedStyle does not work in runat=server onserverload callback
As things are now, we don't do any rendering within Jaxer, which in turns means we won't have style information, unfortunately. I'm moving this to 1.x since we're about to release 1.0. Aptana can revisit this ticket after that release to determine the feasibility and extend of supporting this feature.
Thanks,
Kevin