Closed GoogleCodeExporter closed 9 years ago
Thank you for reporting this issue and pointing to a solution.
We'll take it up immediately :-)
FWieP
Original comment by fwp...@gmail.com
on 10 Apr 2012 at 7:33
The issue has been fixed in r430.
I built in the HTTP(S) switch at the time, but never doubted that the file was
actually there via HTTPS. Well, it apparently was not :-)
@Developers: Should we include the jQuery js-file statically, as opposed to
fetching it via HTTP(s)? Since Google does not offer a 'latest' version, we
might as well. What do you think?
Kind regards,
FWieP
Original comment by fwp...@gmail.com
on 10 Apr 2012 at 7:59
Depending on how often the jquery is updated we could just download and link it
like you did
Original comment by mranimos...@gmail.com
on 10 Apr 2012 at 8:16
Fetching it via http(s) will cause issues at any rate.... https doesn't work,
and if using http, you get errors that part of the page is 'not https', so I
would say to include it statically. Besides that. It's not a 100% necessity to
have the latest version at all times right?
If it works.. It works?
Original comment by lenna...@gmail.com
on 11 Apr 2012 at 2:49
Original issue reported on code.google.com by
lenna...@gmail.com
on 10 Apr 2012 at 7:27