Inline output (show, nested, etc.) does not display in Chrome 18.0.1010.1 dev-m

[clst]

Apparently something was changed in the latest chrome and now nothing happens when you click a link. Other browsers (tested Opera) are fine. Can someone please confirm this?

EDIT:
I just tested with the stable Chrome Windows build and it's not working there either. I have tried active_scaffold 3.1.15 and git master.

EDIT: I forgot to mention that I am using jquery-rails (1.0.19)

[scambra]

Please, test with latest version.

[clst]

apparently it was fixed by Chrome/WebKit Team, as the exact same test I tried this with works perfectly fine today. I did not update active_scaffold, only had Chrome auto-updates enabled.

[scambra]

Ok, then I will close this issue

[clst]

Apparently I have some configuration problem.
Working / not working weirdness was due to browser caching.

[IGNORE]
Can you try it with the current Chrome release? It appears to be broken again.
Apparently it is also not working on Firefox.

With a new test rails setup it seems to be working though.

My old upgraded setup shows WARN Could not determine content-length of response body. Set content-length of the response or set Response#chunked = true

only in Opera it seems to work. Any clue what might cause this?

[/IGNORE]

[scambra]

It's working here in firefox 11 and chrome 18.0.1025.162

[clst]

If I clear browser cache and use my simple test setup it's working fine.

In my upgraded app (from rails 3.1.3 to 3.2.3) it does not. I could not find out what the difference is. Do you have any pointers where I should look? I think something must be wrong with jQuery listeners I just couldn't find anything.

It doesn't seem to be browser specific (see edit above)

[clst]

When debugging I can see the rendered response on the Browser Network screen it's just not displayed in the DOM.

[scambra]

Look at content-type response header

Are you using latest active_scaffold?

[clst]

Whatever it was it's fixed now.

I did "rake assets:clean" and browser clear cache now it seems good. Apparently there was some compiled application.js left over that broke the development environment.
Thanks for bearing with me.