DNewfield wrote: > Many browsers have issues with this--you'll have better luck if you > convert this to an (empty) container tag: Thanks but unfortunately that was already the case, and it doesn't work.
DNewfield wrote: > The server doesn't control how the browser interprets the code it > provides. If the browser isn't doing what you expect, make sure that > the browser is receiving the instructions you expect it to receive. > Look at the source of the page being displayed (which may differ from > the DOM model that firebug shows as the DOM can get substantially > changed from the original html code provided by the server). Make sure > that the document base isn't redefined somewhere, and make sure that the > paths you expect to be listed are what is being transmitted to the client. The DOM I get with Firebug looks very much like the (generated) source code I can view with the browser's inspector. Looks like Struts is "processing" the path information in a way I've never seen before (kind of relative to the page's context path), and the use of tiles probably brings in an additional level of complexity. Please check out the following: http://www.nabble.com/Loading-and-Calling-Java-Script-in-Struts-td20623678.html I'm not the only one having problems, but unfortunately my case is probably more complicated as the JS libraries I'm including are made up of many files arranged in a complex directory structure. Rewriting the script URL is fine for the master include file ("OpenLayers.js"), but does not work for all the others it contains. Regards Emmanuele -- View this message in context: http://www.nabble.com/Problems-with-javascript-files-in-Struts-based-webapp-tp22163997p22180963.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
