Blog Entry
Feb 16

Facebook Dashboard 1.0.2

Posted in Chrome Extensions, Facebook Dashboard

Facebook DashboardThe latest version of the Facebook Dashboard stabilizes the previous update.

Changes
• Badge Counter tracking and rotation fixed.
• New friend activity should be new instead of showing older remixed posts as new.
• Notifications mark as read command is now working properly.
• Refresh calls are now asynchronous, this should make things a little faster.

Download at Google Gallery

If you run into any problems, have questions, concerns, or general comments, feel free to comment on the blog. We read and moderate every post here and will give as much help as we can to support our products. If you have any feedback at all, it is graciously appreciated. :)


This entry was posted on Tuesday, February 16th, 2010 at 9:35 pm
and is filed under Chrome Extensions, Facebook Dashboard.



You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.

Related Posts

2 Responses to “Facebook Dashboard 1.0.2”

  1. Mark L Says:
    February 17th, 2010 at 10:34 am

    I really dig this but you need to fix the “TypeError: Cannot read property ‘innerHTML’ of null” error that I and others have mentioned. And if you are serious about Chrome Extensions why don’t you have support for them on this website like you do for your other products?

  2. The Staff Says:
    February 17th, 2010 at 11:22 am

    Mark, we haven’t been able to recreate the error thus far. Where is it occurring or when, is it constant? There have been a couple of comments about it, but it’s basically an error with no traceable details. As for support, the extensions are a new addition to the site so we haven’t put up support articles yet because currently, there hasn’t been a need. In terms of a forum, we tend to use the blog for back and forth communication on topic. Makes things easier and we see every comment because it’s moderated (we even receive e-mails when comments are posted).

    Is this error occurring as a string in the extension or is it a popup? Are there line references or just the null message (it makes sense logically, but not in context, this could be the difference between a couple try/catch statements or a specific feed issue).

Do you need support for a product? Click here.
«
»