On Firefox Snap for Ubuntu v131.0.2 started in in "Troubleshoot Mode":
I can open trello and open boards and cards.
I can´t:
Hi @Victor, we're aware of an issue with Firefox 132 that has caused issues with Trello's usability, due to the way it handles cookies internally. The Mozilla team is tracking the bug and we're hoping that the next release of Firefox will include a fix. In the meantime, can you try using Trello on a different browser, or with the desktop app? Sorry for the inconvenience — we're hoping this gets resolved soon, but it's out of our hands at the moment. Here's the public ticket you can follow along with: https://jira.atlassian.com/browse/TRELLO-721
@Victor if it works on safe mode/disabling extensions, then it sounds like there may be an extension that is conflicting with it? hard to say which one, you'd have to install one by one I guess to test
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Victor
The only thing that comes to my mind is that in Trello, there is a role called "observers." They only have view-only permissions and cannot modify the project. However, I see that you are on the "free" plan, which does not offer this feature.
Perhaps you could try using a different browser and see what happens? It is also common for browser extensions to interfere with web apps, preventing them from functioning correctly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, that works in other browsers, this is why I was specific about the browser used to reproduce the bug.
I'm talking about boards and cards where I am the only user.
As I mentioned initially, I tried the "Troubleshoot Mode" in Firefox, which is also called "safe mode" in others. It deactivates all the extensions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your feedback, @Victor
I understand that the problem you mentioned is related to the setup you are using.
In that case, you can report this as a bug in the public issue tracker (if it hasn't been mentioned before). However, I am unsure if it will be reviewed soon, as you indicated that this only occurs in a very specific combination of elements.
I saw a similar issue to yours on the tracker. Here is the link in case you want to follow it: click here
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.