![]() At that point, there's quite literally almost nothing we can really do. In this case the issue was first reported, as best I can tell, 4 weeks after the release (I'm assuming this was broken in 33.0 from the start, not just in 33.1, which would be highly surprising considering the changes in that release). We depend on users reporting issues and/or vendors keeping up-to-date with updates such as the above. We're too small an organization for that considering our scale (hundreds of millions of users, a significant proportion of whom use add-ons), and the number of external vendors that interface with us. We're literally unable to contact every single add-on author privately if their stuff breaks. We make appropriate amounts of noise for big changes, too, on. Nightly will have anywhere between 18 and 12 weeks to go to being released, aurora 6 weeks less, and beta 6 weeks less than that (meaning that, right now for instance, it's just under 2 weeks from being released as Firefox 34). We provide public versions of our pre-release software to *everyone*. ![]() ![]() > Also, is it an option for folks like me to regress to prior version of FF > integrated with things like security? If not, then I think you own some > various add-on/extension vendors? At least the ones that need to be tightly ![]() > I assume you provide pre-release version with technical notes to the > that I (and likely others) have switched our default browser from FF to > you should continue to work/pressure Dashlane to fix but you should know > needs to act to fix the 'victim' or the 'changer'. fyi - I worked in this field for many years.
0 Comments
Leave a Reply. |