![]() ![]() Read this answer in context □ 4 All Replies (10)Įarlier today I read a Norton support forum thread where another Norton user posted a "how to" about how he "''bumped''" his Norton Password extension (the 4.0 version that was just released last week) to make it work in Firefox 4.0.1. I am starting to wonder if Norton had to do anything to their extension's for Firefox 4.0 or if that month wait you Norton user's just went thru was a "sun tan job" to extract more money from their user's for a "bump job" on those extensions. ![]() The snippet of the install.rdf file that he posted showed that extension as being compatible with Firefox 2.0 thru Firefox 4.0.* (meaning it won't be disabled by another 4.0.# security update, with that asterik after 4.0.). Should Norton be held to a different standard than any other extension developer? Should Mozilla be expected to hold the Norton developer's hands when they update their Firefox extensions so that Norton does the job correctly, and a minor version security update doesn't turn off that extension because the Norton developers didn't do a better job the first time?Įarlier today I read a Norton support forum thread where another Norton user posted a "how to" about how he " bumped" his Norton Password extension (the 4.0 version that was just released last week) to make it work in Firefox 4.0.1. Mozilla has specific rules for maxVersion compatibility for extensions that are made by everyone.
0 Comments
Leave a Reply. |