I bring up Manifest v3 because with the way Bitwarden was originally designed, it requires a substantial refactor across the board of our browser extension.
ROBOFORM EXTENSION FIREFOX PASSWORD
Secondly, the note in regards to Manifest v3 is absolutely pertinent to this conversation given that we, like other password managers, will need to support this model, and like other password manager browser extensions, will need to work around certain issues. We're actively hiring for a platform and community product manager who will be helping us focus on providing more transparency and communication on issues exactly like this one to keep our community informed and engaged. From the outside looking in I could understand that being a rather frustrating situation especially given our understanding of the issue originally.įor 2022, community engagement and communication will be coming to the forefront of our engineering and product teams. So first, I take personal responsibility for not updating this thread as we discussed or made progress on various avenues on this very topic. I do see now, however, after re-reading through the myriad posts and comments on this thread a recurring theme that we could certainly have done a better job keeping everyone updated on what we're working on and where we're focused here. We also don't generally apologize for how we understand a given situation at any given point in time. Admittedly we don't exactly go back in Github history and revise comments or delete history. This has been a pretty contentious issue for some time. Hello everyone! Chad here with the Bitwarden team. So, at the very longest, this issue should only persist for one more (painful) year. However, from the Google timeline, it would seem that they have a hard deadline for this of January 2023. However, again no timeline or priority has been stated on this matter by their team in this thread. In good news, it does now seem that with the impending implementation of Chrome Manifest V3 that they will be forced to act. People understand that business decisions need to be made and some won't be popular, just don't lie about them. It doesn't have to be particularly smooth (we're mostly developers here after all), but an honest attempt to communicate really does go a long way. To me it's quite sad that effective, truthful engagement with the community is not one of the top priorities for any company. We understand that this decision will not be popular with those users whom it affects, but please try to understand why we are taking this stance." Instead we would rather focus our limited resources on efforts that will bring great features to the most possible users. Because the Firefox extension is used by a relatively small portion of our users, and private mode by even fewer, we have made the decision not to refactor our entire codebase only to fix this issue. Sadly the refactoring process to restore previous functionality would require a fundamental rewrite of our core system and would represent a huge time-cost from our core team. "Unfortunately the Mozilla team have made a change to Firefox to increase their users' privacy and this has prevented our current extension from working. I'll even provide them with a starting point for the future. It really wouldn't have taken much time to write a clear and understandable (perhaps even acceptable?) comment on the matter at some point during the last 5 years. comparable competitor apps working in private FF windows). On this issue the BitWarden team have basically lied and passed blame repeatedly, despite evidence that a solution was possible being presented repeatedly (i.e. However, the way that the BitWarden team has communicated their stance on this topic to their users (to whom it is important) is dire and very disappointing - in fact bad enough to get a lurker like me to crawl out from under my rock to comment. For me this is only a minor inconvenience.
0 kommentar(er)
