jQuery UI Widgets › Forums › Navigation › Tree › Chrome???
Tagged: chrome
This topic contains 6 replies, has 2 voices, and was last updated by Dimitar 11 years, 8 months ago.
-
AuthorChrome??? Posts
-
Hi,
I am totally new to jqWidgets, but I do like what I see, and would love to use them on my projects. The only problem is, in my tests, it works perfectly on Firefox 16 and IE10, but NOT on Chrome 26.0.1410.43. I am on version 2.7. After seeing it did not work in my MVC 4.0 project, I tested with the demos pages, and it’s the same. Is there anything that need to be done for Chrome?
I will not be able to use the widgets if there is a problem between them and Chrome.
Thanks,
Bernard.Hello Bernard,
Please provide us with more specific information. We have thoroughly tested all the widgets under Google Chrome and they work perfectly fine. What issues do you experience? Do you experience the same issues with jQWidgets 2.8?
We are looking forward to your reply.
Best Regards,
DimitarjQWidgets team
http://www.jqwidgets.com/Hi Dimitar, thanks for your quick answer. I have not downloaded jQWidgets 2.8 yet, will do tonight. What I experience is that it seems jQuery is not active at all with Chrome (I just checked with jsfiddle.net, it works otherwise… ).
For example, if I right clic on ajaxloading.htm, in demos\jqxtree from within Visual Studio, then clic on “View In Browser”, when I select and clic on the arrows in front of “Root Folder 1 or 2” nothing happens, while in Firefox and IE I see Ajax1.htm (and 2) being immediately displayed.I just took this as an example, but it’s the same with ALL demos for jqxtree.
In fact, I was working this morning on my project, and realized both jqxsplitter and jqxtree where not working, while I knew they were before! That’s where it hit me, it was not working in CHROME, but perfectly well with all the other browsers I had tried. I decided to check the demos, as they are much simpler, thinking I had done something wrong I needed to correct. Well, the demos are not working either, so I guess it has nothing to do with my code…..
regards,
Bernard.Hi Bernard,
1. In order to work with Ajax, you need to run the samples from a web server as Ajax uses HTTP protocol.
2. The current version is jQWidgets 2.8, not jQWidgets 2.7. Our online samples work fine with Chrome. Please, try them.Best Regards,
DimitarjQWidgets team
http://www.jqwidgets.com/1. In order to work with Ajax, you need to run the samples from a web server as Ajax uses HTTP protocol
OK, then, why would it work with Firefox and not Chrome??? Under the very same conditions?
Maybe, just maybe, instead of taking me for a fool, you should have a look at the example detailed above. You would see there is no use of a server in that particular demo. BTW, should I remind you that I said it was the same for ALL other exampls, not only the one with Ajax.
You insist on me loading and using your latest version. Would you be kind enough to point me to the change logs, where it says some bugs about Chrome have been solved?
I am sorry, my time is precious, and there are tons of JS widgets/plugins/whatever around. I better find one which actually works with all browsers, rather than loosing time with a customer support who is taking me for a dumb.
Bernard
OK, it DOES work with 2.8, WITHOUT a server. I’ll check and compare the 2, I bet a script needed by Chrome was not being included in 2.7. Where would I find a precise documentation about changes between versions? And how do I get to know when there is a new version? Do you have an email list for that?
Bernard
Hi Bernard,
1. The Tree’s Ajax sample works with Ajax and that is the reason why it should be started from a web server. Some browsers work with Ajax without a web server, some do not. Howerver, all browsers work with Ajax when Ajax calls are made through a web server.
2. You can get notification by subscribing to either Facebook or Twitter here: http://www.jqwidgets.com/Follow.
3. For information about recent changes, see: Release History. If you are using touch-screen PC or Laptop, then that could be the reason of the issue with 2.7.
Best Regards,
DimitarjQWidgets team
http://www.jqwidgets.com/ -
AuthorPosts
You must be logged in to reply to this topic.