Erin Casali

Yes that's a workaround. Still, it's a pretty bad hack considering that we'd like to avoid "injecting" stuff from Baker as much as possible into the HTML page. :/

I guess that "scroll" will require javascript... However, I'm not sure that is what work, because the point where the scrolling is might not match where the current page is...

It might still be worth posting on the other tracker, just with a line of introduction, so others could check that. :)

Unfortunately it seems a classic case of memory management. Retina is more than 4x intensive on the graphic side of things, thus using more memory. Once the app touches the...

It might be either on Baker's side or WebKit side, difficult to tell. We'll probably have to check what exactly is leaking. Thanks for the test and the report :)

We checked but we weren't able to find such a huge difference unfortunately. At launch the `master` version of Baker uses about 1.7Mb, and stays around 2Mb after each _open...

Yep, because it's the app consuming that memory, so it's app's consumption. It's a bit weird.

I dug into that a bit and it might be a problem, but not a technical one, but a logical one. The reason is that right now the index code...

It adds a _lot_ of overload of configuration that way. Consider that right now all you need to do (if you don't want to do anything too fancy) is to...

I mean for the author, yes. The reason everyone is using Baker is also because we do a very hard work in making the things as simple as possible, so...