Hi String, My disappearance and these problems was an unfortunate coinciding of events. We'd been doing a trial of about 10% of renders on the new code for a few weeks and saw few issues. This was increased to 50% some time around the 10th, right as I was leaving for a long-planned vacation. I came back last week (but with a cold) so I haven't really had a chance to look at all of this until today, my apologies.
With that said, I don't think all of these issues are related to the new rendering code. API incompatibilities such as _toggle surely are, but I'd have to go through the list one by one to be sure. I'll attempt to do this today, internally reporting anything that hasn't been subsequently resolved while I was absent. With that said, the way to test for compatibility with the new rendering code is to test in the sandbox. If you see a problem that manifests in production, but not in the sandbox, it is unrelated to the new rendering code (or it's been subsequently fixed and not yet pushed to prod). For instance, the issues with _toggle would have been discoverable, for many months before gadgets.* was in prod for any gadgets, by testing a gadget that used _toggle in the developer sandbox. I believe I've said before, but in case I haven't, test your gadgets in the sandbox: we're aiming for compatibility with the legacy API, so report things if they break. Thanks, Dan On Jun 11, 12:55 am, String <[email protected]> wrote: > On Jun 5, 6:08 pm, "Dan (Google)" <[email protected]> wrote: > > > Gadgets.* is not fully rolled-out into production. However, we're > > currently doing experiments with gadgets.* in production (as you > > noticed) by displaying some gadgets with the new rendering code that > > also supports gadgets.*. This is to ensure compatibility when we do > > roll out gadgets.* at 100%. > > Hi Dan, > > It doesn't look like you've been around the iGoogle Developer Forum in > nearly a week, but I'm hoping you can find the time to drop back in > soon. There seem to be lots of scattered issues appearing in the last > few days, and I'm guessing that they're related to the experiments > with the new rendering code described above. > > The problems summarized below are all discussed in recent threads. I > have no way of knowing if they're related to your staged rollout, but > they have all appeared in the last week to previously-working gadgets. > - Issues with feeds and remote content: content-type problems, HTTP > errors, and more. > - Some gadgets not rendering at all, instead just showing a Google- > generated 404 message. > - AdjustFrameHeight problems. > > There's a real feeling of abandonment on the forum, that Google has > broken our gadgets in the production environment - with no warning > before the fact, and next-to-no feedback from official channels after > the fact. > > I also have to ask, was the "new rendering code" trialled in either > sandbox before this limited live rollout? My own gadget problems are > certainly things that I would have seen in my own sandbox testing, and > while I can't speak for other developers, I'd think some of them would > have too. > > One last, related question: is there any way for us developers to > force the new environment for our own testing? As you said yourself, > the experiments are not active for all users... and that's not a good > situation for tracking down problems. > > Thanks for your attention, > > String --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
