If I was to take a guess, it would be the new usage of require.js in tapestry 5.4. Tapestry has defined a bootstrap module. You might need to define a module which depends on the bootstrap module to guarantee that yours is loaded after bootstrap.
As I said, this is a guess... I've not yet dug too far in this area yet myself. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-5-4-alpha-2-css-overriding-tp5719856p5719904.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
