It’s difficult for me to determine who is at fault here: Chromium or BitWarden.
I think that writing a letter to Chromium is futile.
For those interested. SideBar :
chrome-extension://nngceckbapebfimnlniiiahkandclblb/popup/index.html
It’s difficult for me to determine who is at fault here: Chromium or BitWarden.
I think that writing a letter to Chromium is futile.
For those interested. SideBar :
chrome-extension://nngceckbapebfimnlniiiahkandclblb/popup/index.html
@serega_da Hey, I changed the tag from app:desktop to app:browser as you mean the browser extension and not the desktop app.
Yes, this is a bug-report.
It could have been a single line: Off / On – don’t work.
It’s always better to see it once
.
Good to know it here as well - but GitHub is the place for official bug reports (“New issue”). ![]()
Yes, it is. And it seems that the developers even respond there. There is no need to duplicate
SideBar – Off/On Extension · Issue #16991 · bitwarden/clients · GitHub
What is the most valuable thing in the first message?
Title and last line !
I remember I lost it myself (direct addresses on index.html don’t work in SideBar) .
I dug through the entire BW forum until I found my old message. It’s from two years ago.
Congratulations! And if I don’t find something, I’ll ask you next time. ![]()
I will answer in 2 years ![]()
GitHub closed the Issue – “we have everything working” . They suggested to contact the forum
.
I have a few assumptions:
They were not impressed
cursor: pointer
(but this was already a gift from the browser, from the Chromium engine)
And it’s obvious that the answer is standard. . Соpy-Past . Nothing was checked there.
And the one who closed it is not a developer.. Nowadays, even in kindergartens, its young members have a GitHub repository