Ajax not working in Google Chrome
caugmar - October 1, 2009 - 17:17
| Project: | Hierarchical Select |
| Version: | 6.x-3.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | minor |
| Assigned: | Wim Leers |
| Status: | closed |
Jump to:
Description
Hierarchical select ajax interface don't seems to be working in Google Chrome. It is only displaying the static interface, with the update buttons. I have tested it in Windows XP and Windows Vista.
#1
http://wimleers.com/demo/hierarchical-select works fine for me in Google Chrome.
Please confirm that that also doesn't work for you.
#2
Crap. Misunderstood last comment. Ignore me.
#3
#4
I'm using the latest dev (10/2/2009) with Google Chrome (WinXP). Firefox works fine, but Chrome doesn't.
I only tested it with "Content Taxonomy" (taxonomy CCK-fields) and for each field I get:
"Javascript is not Enabled", and it shows the downgraded version. It kinda works (only with single-selects+page refresh) but I guess the "is-javascript-on" detection doesn't work for Chrome. At least not when using the Content Taxonomy fields, for which support was added to the D6 dev version just recently.
The demo-site (which indeed works with chrome) is probably not using content_taxonomy fields.
#5
Well, you should give using HS with normal Taxonomy a try too then, so we can narrow down the cause. Or Menu.
CNW is an incorrect status because no patch is attached so there is no code that needs work.
#6
I finally got time to test this. Turns out the Ajax problem on Chrome is caused by the "Cache in a HTML 5 client-side database"-setting. Turning that setting "Off" (in /admin/settings/hierarchical_select ) results in working Ajax for Chrome :).
I don't know if there's any noticiable impact on performance, but I guess I'll keep that setting off (until chrome gets support for that stuff). Or maybe I'll turn it back on later anyway. I'm developing my sites partially with Chrome, mainly because of it's speed with JS.
#7
Aha, good catch! It's more likely that I've got a bug in my code than Chrome having a buggy implementation though :)
#8
Automatically closed -- issue fixed for 2 weeks with no activity.