Thanks Dan, I asked QA, and it turns out that due to the muddled lineage of this project, they can't say for sure if it was tested in the past. I'll have access to the machine in question tomorrow, when I can try this in a non-sandboxed environment.
I did see a thread that seemed to be talking about the same problem: http://groups.google.com/group/Google_Web_Search_Help-Personalizing/browse_thread/thread/9cefb66f3d77dfa/d3b455b1bbca73d6?lnk=gst&q= So apparently this may have started in late May, early June? If so, is this platform perhaps simply not supported? Also, another way to narrow down the issue would be for me to try basic hello-world type gadgets that use Oauth, if you know of any. Thanks a lot, /Adam -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Dan (Google Employee) Sent: Tuesday, October 21, 2008 1:15 PM To: iGoogle Developer Forum Subject: [Google-Gadgets-API] Re: Problem with OAuth support on Mac/Safari 10.4.10? Hi Adam, Did the gadget pass QA in this configuration previously, or has this been a persistent problem? I'm curious if it was a recent change (perhaps on our end) that caused the strange behavior. Also, is this behavior the same across production and the sandbox? Thanks, Dan On Oct 20, 1:52 pm, "Wise, Adam" <[EMAIL PROTECTED]> wrote: > I have a strange issue that is only showing up on Mac OS 10.4.10, > Safari version 2.0.4. It's preventing my OAuth iGoogle gadget from working. > After much trial and error, I narrowed it down apparently to the > following... > > 1) If I have an OAuth element in the main xml file, then my scripting > finds the 'gadgets' object to be undefined. > 2). If I remove the OAuth tags, the gadgets object is there, but is > missing most sub-objects, such as 'utils'. (e.g. gadgets.utils is > undefined). And of course, without the OAuth element, the gadget > wouldn't be able to log in anyway. > > Oddly, this seems specific to the Mac OS and Safar version 2.0.4. Our > gadget has been verified on a wide variety of OS/browser combination, > and this is the only one with this problem. (Newer versions of Safari > work fine on the Mac OS). We have also confirmed it is not specific > to one bad test machine -- it was first discovered by our QA in > California, and verified on one lonely Mac/Safari 2.0.4 box running > here in Dulles, VA. > > Any ideas? > > Thanks, > /Adam > > [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en -~----------~----~----~----~------~----~------~--~---
