[ http://issues.apache.org/jira/browse/TAPESTRY-1099?page=comments#action_12438634 ] Greg Woolsey commented on TAPESTRY-1099: ----------------------------------------
I don't see anything in AjaxShellDelegate that would need modification for me - am I missing something? Unless I radically change (or use a snapshot of a major update to) the dojo API I don't think I need a new delegate. I just need to watch for behavioral changes like the base URL handling one. As for the asset URL notation, that shouldn't be a big deal to people as long as it is noted somewhere prominent. I like the deprecation warnings the new Tapestry code generates to help me see what I need to update to migrate to 4.1. I wouldn't have embarked on a 4.1.1 migration if I didn't think I could hack it as needed. Overall, I think it's well-crafted and a welcome replacement for the (closure leaking) JavaScript in T4. > Current snapshot of 4.1 has HTTPS DoJo problem, having trouble updating DoJo > ---------------------------------------------------------------------------- > > Key: TAPESTRY-1099 > URL: http://issues.apache.org/jira/browse/TAPESTRY-1099 > Project: Tapestry > Issue Type: Bug > Components: JavaScript > Affects Versions: 4.1 > Environment: Internet Explorer 6 > Reporter: Greg Woolsey > Assigned To: Jesse Kuhnert > > The development version of DoJo included with the current packaged 4.1 > release contains DoJo bug #550 (http://trac.dojotoolkit.org/ticket/550). IE > shows a mixed-content warning loading DoJo from a page accessed via HTTPS. > DoJo 3.1 has this problem fixed, even though the above issue doesn't indicate > it. > However, when I tried pointing my @Shell component to a DoJo source directory > containing the dojo-0.3.1-widget package (and modifying the dojo.js to > require packages not packaged in the T4.1 dojo.js), I get no widget prompt > with validation errors on form submit. Form submit fails, and the dojo and > tapestry JS objects appear to be defined and complete, but I get no feedback. > When I leave the Shell component to it's default parameters, I get the IE > warning, but if I OK the operation, then I see the validation errors prompt. > If the packaged T4.1 build contains an updated DoJo, that should work with > HTTPS, but I'm still trying to figure out what's up with my configuration to > use a custom DoJo source and path with @Shell. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
