On Oct 9, 3:29 pm, "Dan (Google Employee)" <[EMAIL PROTECTED]> wrote:
> Hi David,
>
> Sorry about that, I'm not sure why I typed your last name. I've
> probably done it a few times now in this and the other thread, so
> consider the apology to extend to all of the times I did it.

Apology accepted.  No worries.

>
> Anyway, with regards to your search methodology, you haven't chosen
> the first relevant forum with regards to your particular issues. I've

Okay.

> pointed out what would be the correct forum for your suggestions. It's

Thanks.

> up to you whether or not you wish to share them in a place where they
> are received by the appropriate parties. I can, and do, share product
> feedback with the product team that I receive in this group. However,

Good deal.

> you are far more likely to see the changes that you desire if you
> share them in the appropriate group, because many other active iGoogle
> consumers can discuss and contribute to your feedback. The primary
> purpose of this forum is for developer discussion as it relates to
> development of gadgets. If you have development-related questions, as
> you've stated you will, feel free to share them here.
>
> I'm unsure what you're referencing on the competency of my answers. If
> you can be more specific, that would be helpful.

I wasn't referencing your answers at all.  I don't know you from any
of the other Google employees (who have been less than competent in
the past when answering my questions.)  I was a bit put off that
nobody commented on the FF3 bug.  Perhaps they fixed it in lieu of
commenting, which is fine by me.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to