On Wednesday, March 30, 2016 at 11:49:11 PM UTC+2, alfonsoml wrote: > > Wouldn't it make sense to freeze Firebug for the people that don't want to > upgrade Firefox, so there's no need to worry about compatibility with old > versions and this kind of unexpected breakage? > They are happy with their setup as is, so unless there's an important > reason, set the minimum compatibility with Firefox 40 for example and > they'll keep on working exactly the same way as long as they want. > This is even more important taking into account all the upcoming changes, > instead of pushing versions to fix compatibility with new firefox and at > the same time add the code to avoid breaking old versions, release the new > firebug only for those that have a firefox recent enough and everybody will > be happy > Yes, agree. I'll do that as soon as support for multiprocess (aka e10s) lands in Firefox. It'll be breaking change and good opportunity to freeze Firebug.
Honza -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/36613956-0ecb-407b-83e6-1bd892c5ed48%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
