Side navigation
#8319 closed bug (duplicate)
Opened February 18, 2011 04:52PM UTC
Closed February 18, 2011 11:50PM UTC
Last modified March 14, 2012 07:51PM UTC
AJAX no longer working on Blackberry Widgets using 1.5
| Reported by: | sefigrossman@gmail.com | Owned by: | sefigrossman@gmail.com |
|---|---|---|---|
| Priority: | low | Milestone: | 1.next |
| Component: | ajax | Version: | 1.5 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Perhaps I need to configure the new AJAX module a certain way, and I'm not sure if you officially support Blackberry Widgets, but I created a barebones test with just a GET and it does not fire the callback. I replaced the jQuery file with 1.4.4 and it works fine.
Attachments (0)
Change History (5)
Changed February 18, 2011 04:56PM UTC by comment:1
| component: | unfiled → ajax |
|---|---|
| owner: | → sefigrossman@gmail.com |
| priority: | undecided → low |
| status: | new → pending |
Changed February 18, 2011 08:46PM UTC by comment:2
jQuery.support.cors = true worked... is that the way it's going to be or is it going to be added to happen automatically in the next update?
Changed February 18, 2011 11:10PM UTC by comment:3
Yes, this is the way to handle this kind of scenario for unsupported environments. We don't have any mean to feature-test if the environment accepts cross-domain requests while not supporting cors... save from making a request at load time which is clearly not an acceptable approach.
Changed February 18, 2011 11:50PM UTC by comment:4
| resolution: | → duplicate |
|---|---|
| status: | pending → closed |
Closing, as the suggested solution works and is the correct way to handle environments which support cross-domain requests but not cors.
Can you try setting
jQuery.support.cors = truejust after jQuery loaded and then report if the ajax calls work