Wouldn't you know it—I wasn't following instructions. In the INSTALL file there is a part at the end about setting up a config file with a jslibdir parameter. Doing that properly fixed the problem.
What was happening was that the webserver was getting a request for the Javascript library, /lib/jslib.js, but was serving up the same results as for the application (so the results were an HTML file). This was the cause of the Javascript errors, and of course none of the Javascript on the page was working. As a feature request: It might be good to print an error in the case where the webserver gets a request for a file it doesn't know anything about. Or maybe such logging is already available through an option somewhere? Thanks for your patience, Ezra On Mon, Jul 15, 2019, at 11:55 PM, Ezra e. k. Cooper wrote: > Hello, > > I've been away from Links for some years, so I may well be forgetting > something commonplace. > > I was working on a program that is browser-only and was doing grandly until I > tried to add an event handler to an XML element, using the l:onmouseup > syntax. It didn't work: first, the HTML elements appear in the page without > an onmouseup attribute, and the browser's DOM inspector shows just an > "onload" handler for the elements. > > The same problem existed for the draggable.links example, as shown in one of > the accompanying screenshots. The other screenshot shows some JavaScript > errors in the console, and indeed maybe these are near the root of the > problem. > > I'm using a Mac on macOS 10.14 and Chrome "Version 75.0.3770.100 (Official > Build) (64-bit)" > > Any help would be appreciated! > Ezra > > > *Attachments:* > * Screen Shot 2019-07-15 at 11.52.33 PM.png > * Screen Shot 2019-07-15 at 11.42.25 PM.png -- Ezra e. k. Cooper [email protected]
_______________________________________________ links-users mailing list [email protected] http://lists.inf.ed.ac.uk/mailman/listinfo/links-users
