Norton Family

[Matt_Boucher]

Just so you know our product works regardless of if they disable the plugin. The plugin helps us determine what the top level url is, that is the one your child typed in the address bar. If the plugin is disabled, you will see more urls as we can determine the difference between what is top level and what is embedded.

All policy's will still behave properly and pages will be blocked or warned based on category without the plugin being enabled.

We do claim support however if at every release they disable us (its unclear to me why they do this at this point) it puts all the burden on us.

[randomname]

Well then I must thank you for the good news - what really matters to me is not the claimed status of the components but the surfing protection.

The message I get is that the extension is not compatible (I'm sure you know NSM is not a plugin). As far as I know this comes when the extension manifest says "supporting Firefox up to 9". Are you positive it's not NSM disabling itself because of its own declaration?

[KatieQ]

Hi randomname,

We have just released Norton Safety Minder 2.3.0.17 via Automatic Liveupdate, which is compatible with Firefox 10.

Are you also positive the add-on for Norton Safety Minder is not disabled manually at Tools -> Manage Add-ons in IE browser(If IE is the browser being used)? 

If the add-on of NSM is disabled, please enable it and see if it happens again.

I'm very glad to know you have learned that NSM itself is not a plugin while using the NOF product. Both the add-on for NSM and NSM itself were developed by the NOF engineering team. If you are interested in learning more about the product, please let us know. 

Thanks,

Katie

[Solidac]

Well, Firefox 11 has been release and as usual, the current Norton Safety Minder will not work with this version. Will hold off on updating FF until the new NSM is out.

Solidac

[Matt_Boucher]

I hope you are lodging the same complaints in a Firefox forum for having a plugin solution that requires vendors to continue to update their solution.

We don't have the same problem with Chrome or IE, just Firefox, and frankly they are losing market share so its becoming less and less important.

[randomname]

Well it obviously was not important TO YOU until now either, so I can't see how that is going to change anything in your bad attitude.

[Matt_Boucher]

Sorry if it sounded like I had a bad attitude. It is important to us, in fact that is why we have been trying to update for each release. The problem comes with the fact that we have to continue to certify for each of these releases. This is costly, and I would imagine that it costs many companies time to recertify their products for each new release. FF may think its better to release quicker, but for us it makes it harder to track.

[randomname]

Ok now it sounds much better.

We users are already doing our job: delay Firefox updates until you get it up and working and, for what is worth, complaining in Firefox forums as well (I understand a solution for this is undergoing) But until then we'll have to let you know constantly that this add-on is very important to us.

[Matt_Boucher]

Go to know that FF is working on a solution.

Thanks.

[tetz]

Sorry, Matt, but I'm confused now. Are we waiting for Mozilla to make Firefox compatible to safety minder or will there we a new version of Safety Minder that's compatible with Firefox 11? Can you give us an indication as to when this will be, either way?

Btw, last time I checked, Firefox's market share was still larger than that of Chrome - so it's still relevant.