The recent Gmail API change--presumably the same one that broke
Favicon alerts--is throwing this error. More information is in the
comments of this page:
http://code.google.com/p/gmail-greasemonkey/wiki/GmailGreasemonkey10API
It appears that this is an unintended bug with the API change, so
hopefully Google will fix and it will resolve itself. In the meantime,
I checked my JavaScript console with Better Gmail 2 installed and
wasn't getting this error--I can't tell if I'm doing it wrong or if
it's stopped happening or if I don't have any of the problematic
scripts enabled.
Can anyone who is getting these errors confirm? If you are getting the
errors, if you enable Better Gmail 2, but uncheck all of its options,
does the error still happen? I assume it only happens when the scripts
that use that particular broken API call are enabled.
Sorry for this inconvenience.
On Nov 18, 8:40 am, Gina Trapani <
ginatrap...@gmail.com> wrote:
> Thanks for letting me know about this, all--I'm tied up today but
> promise to take a look at this tonight or tomorrow, and issue a new
> build of the extension with the updated Favicon scripts.
>
> Thanks for your patience!
>
>
>
> On Tue, Nov 17, 2009 at 9:07 PM, Ben <
b...@plessinger.us> wrote:
> > Started today. I get a repeating error in firebug. Disabling the
> > better gmail addon stops this error from occurring.
> > CustomError: Service for "H" is not registered
>
> > I believe this is related to a change in gmail
>
> >
http://www.google.com/support/forum/p/gmail/thread?tid=6986eb30d71ec3...
>
> > and
>
> >
http://getsatisfaction.com/mozilla/topics/repeating_java_script_conso...