On Fri, Nov 8, 2013 at 2:31 AM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote:
> On Thu, 07 Nov 2013 19:27:11 -0200, Bård Magnus Kvalheim < > mag...@kvalheim.eu> wrote: > > ... On slightly different note while discussing 24 - the ordering of >> stack css have changed from 22->24 which I currently have no workaround for. >> > > Could you provide a concrete example? For another bug I fixed, I just made > sure the CSS stylesheets from stacks are always put before the @Import'ed > and the ones declared inside <head> directly. If any other ordering > changed, then a regression happend and I should fix it. Yes, so what I see in 24 is that core stack css is inserted after my own stack css. In 22 the core stack css was inserted before. In practice, bootstrap.css is now ordered after my own css so the 'overrides' don't work no more. Here's example screens: https://docs.google.com/presentation/d/12R7MmvtsG3XF6H5XY3fiUmh7oY-LJmWnihlZPP38RQw/edit?usp=sharing Let me know if more details is desired.. > > > True. Quite important to get rendered page as quick as possible. One >> sideeffect is that it may take a while for all javascript to actually >> execute and make all pieces work correctly. That could be ajax links for >> partial render - which instead will trigger another full page reload if >> not 'intercepted'. >> > > Yep. But, if the event handler is checking for AJAX vs non-AJAX > (Request.isXHR()), it will work in both ways. In most cases where it's an issue we actually want it to be ajax/javascript functionality only. Think I'll look into making an 'Event/bind' mixin that provides desired properties. I see Tapestry-JQuery have a similar one - http://tapestry5-jquery.com/mixins/docsbind .
