On 10/03/2012 10:19 AM, Simo Sorce wrote: > On Wed, 2012-10-03 at 15:50 +0200, Petr Vobornik wrote: >> As Alexander proposed in other channel. I will remove the removal of >> configure.jar and offer the old configuration method if user is using FF >> < 4 so we don't have to make the extension compatible with this ancient >> version. It will be done this way: >> >> If FF < 4 is detected: >> * in browserconfig.html steps 2 and 3 will be grayed-out and replaced >> with step 2a with a link to ssbrowser.html and a description explaining >> the problem >> * ssbrowser.html will be enhanced by steps for autoconfiguration of FF >> < 4. >> >> We can also show the steps in browserconfig, but I want to have it >> somehow available even if user is not using FF<4 to keep general >> awareness about the problem and also to be usable if version detection >> fails. Other possible problem with steps in browserconfig is different >> styles of buttons (to keep the same styles we would have to include same >> css files and jquery.js to configure.jar, which I don't want to do). > Excellent plan, we should try to reduce the amount of work, and letting > old browsers use the old method is perfectly fine. > If FF15 is the only browser that fails with the old method I would even > go as far as testing exclusively with FF15 and have anything < FF15 use > the old method. +1
> Simo. > -- Thank you, Dmitri Pal Sr. Engineering Manager for IdM portfolio Red Hat Inc. ------------------------------- Looking to carve out IT costs? www.redhat.com/carveoutcosts/ _______________________________________________ Freeipa-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/freeipa-devel
