Persistent Bitwarden UI and maintain unsaved data

@grb, @dflinn, @DenBesten, @Kevin_Harris, @Nail1684

Folks, I wish to apologize in advance for the next sentence, but it feels to me as if my suggestion is being pigeonholed into the silo of “We’ve had this report a million times” and not examined anew.

I WANT TO PROPOSE A NOVEL SOLUTION TO THE NONPERSISTENT UI PROBLEM (sorry for shouting)

Unless I am completely mistaken (and I would welcome a correction if I am wrong), Bitwarden already has all the UI components and machinery to solve what I perceive as the nonpersistent UI problem.

My Proposal: Whenever someone wants to add/edit a record, Bitwarden should immediately pop out the extension window. Once popped out, Bitwarden can work exactly as it already does.

  • The Bitwarden window has its own identity in the browser’s Windows menu (works today)

  • People can rummage around, click elsewhere, and ultimately come back to the popped-out Bitwarden window (works today)

  • Bitwarden can refuse to let the window close until they have used either Save or Cancel for the changes (works today)

The ONLY change is tying a click on Add or Edit to pop out the window. No further change to Bitwarden is required. This seems to solve the problems of:

  • Losing typing when clicking to another window (Bitwarden won’t close until they choose Save/Cancel)

  • Losing typing when popping out the window (it’s already popped out)

  • Whether to have the popout icon in other windows (any change should pop it out)

And now I request forgiveness - I expect that there is some deep reason that this won’t work. But it sure seems to solve my problem, and I would like to know why it wouldn’t work more broadly (or perhaps a link to that discussion.)

Thank you for listening.