On Mon, Feb 11, 2013 at 6:46 PM, Rob Weir <robw...@apache.org> wrote: > My impression was that even if we made no changes, from the user's > perspective, they would lose all extensions. This is due to the > change in base directory for the profile. So all extensions would be > lost and need to be reinstalled. So there will be no doubt in the > user's mind, even if they do not read the release notes, that the > extensions are gone.
Just copy the Firefox way.... A dialog reading something like "Oh, we´ve detected some extesions, checking for compatibility with 4.0..." followed by "the following extensions are not compatible with 4.0 and have been disabled, you might want to check [url] for newer versions compatible with 4.0". Of course, automated checking of each extension on a central database (like FF does) would be great, but the half-solution (informative message) above is better than nothing. Just my $0.02 FC -- During times of Universal Deceit, telling the truth becomes a revolutionary act Durante épocas de Engaño Universal, decir la verdad se convierte en un Acto Revolucionario - George Orwell
