You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Don't minimize the source code. It is much easier to debug when not minimized. The source code is open source anyway, so nothing is being hidden. It also makes the download smaller as it would make source maps easier to distribute
I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/
Please sign up on our forums and search to see if this request already exists (https://community.bitwarden.com/signup). If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked.
This issue will now be closed. Note that the “Closed as not planned” status is for internal tracking purposes only, please do not hesitate to send us your suggestions to the forum.
Steps To Reproduce
Right-click and "Inspect popup"
Expected Result
Don't minimize the source code. It is much easier to debug when not minimized. The source code is open source anyway, so nothing is being hidden. It also makes the download smaller as it would make source maps easier to distribute
https://webpack.js.org/configuration/optimization/#optimizationminimize
Actual Result
The source code is minimized
Screenshots or Videos
No response
Additional Context
No response
Operating System
Linux
Operating System Version
No response
Web Browser
Chrome
Browser Version
No response
Build Version
2024.12.2
Issue Tracking Info
The text was updated successfully, but these errors were encountered: