Skip to content

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

clst opened this Issue Jan 23, 2012 · 9 comments

2 participants

clst commented Jan 23, 2012

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?

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 commented Jan 30, 2012

Please, test with latest version.

clst commented Jan 31, 2012

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 commented Jan 31, 2012

Ok, then I will close this issue

@scambra scambra closed this Jan 31, 2012
clst commented Apr 20, 2012

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

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?


scambra commented Apr 20, 2012

It's working here in firefox 11 and chrome 18.0.1025.162

clst commented Apr 20, 2012

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 commented Apr 20, 2012

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

scambra commented Apr 20, 2012

Look at content-type response header

Are you using latest active_scaffold?

clst commented Apr 20, 2012

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.