-
Remember to address to the Bug Tracking guidelines and to follow the instructions in the post ticket template.
-
Welcome to the Chevereto user community!
Here users from all over the world gather around to learn the latest about Chevereto and contribute with ideas to improve the software.
Please keep in mind:
- This community is user driven. Be polite with other users.
- Is required to purchase a Chevereto license to participate in this community (doesn't apply to Pre-sales and RFC).
- Purchase a Pro Community Subscription to get faster ticket response times.
-
Chevereto Support CLST
Support response
- Extra Support is delivered within 24-hours.
- Pro Subscription ticket response time is within 7 days on Software Support, Bug Tracking and RFC.
- Bug Tracking requires an active Chevereto self-hosted subscription.
- Community Help is user driven. Be polite with other users and do not expect official support.
Support checklist
- Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
- Confirm that the server meets the System Requirements
- Check for any available Hotfix - your issue could be already reported/fixed
- Read documentation - It will be required to Debug and understand Errors for a faster support response
PUP Auto Close doesn't work on Firefox
- Thread starter TomaGo
- Start date
Hello @TomaGo ,
Thank you for reaching out and for your support subscription. We understand your concern and are here to assist you as much as possible.
Regarding the issue with Firefox, some browser-specific behaviors may require additional troubleshooting and testing, which can take more time than expected.
Your subscription contributes to maintaining our services, but it's essential to note that certain issues might extend beyond the immediate scope of what can be resolved quickly. We'll do our best to assist you with the BBCode and auto-close functionality and follow up as soon as we have more information or potential solutions.
Thank you for your understanding and patience.
Best regards,
Rodolfo
Thank you for reaching out and for your support subscription. We understand your concern and are here to assist you as much as possible.
Regarding the issue with Firefox, some browser-specific behaviors may require additional troubleshooting and testing, which can take more time than expected.
Your subscription contributes to maintaining our services, but it's essential to note that certain issues might extend beyond the immediate scope of what can be resolved quickly. We'll do our best to assist you with the BBCode and auto-close functionality and follow up as soon as we have more information or potential solutions.
Thank you for your understanding and patience.
Best regards,
Rodolfo
Oakley
💖 Chevereto Fan
FYI
I don't normally use Firefox but I've tried this on a clean/default up to date copy of FF (v.133.0) and I can confirm the window does not auto close on version 4.2.3. User has to copy the BBCode and close the window manually.
Out of interest I tried it on another site running 3.20.20 and it did work.
I'm sure I've seen similar issues before many years ago with other scripts (not Chevereto) having the same problem with FF.
I don't normally use Firefox but I've tried this on a clean/default up to date copy of FF (v.133.0) and I can confirm the window does not auto close on version 4.2.3. User has to copy the BBCode and close the window manually.
Out of interest I tried it on another site running 3.20.20 and it did work.
I'm sure I've seen similar issues before many years ago with other scripts (not Chevereto) having the same problem with FF.
We’ve identified an unusual issue with the postMessage API and popup functionality that only occurs when Firefox's developer console is closed. Oddly, the issue resolves itself when the console is open, which complicates direct debugging.
We're actively investigating this behavior, and in the meantime, if you encounter this problem, opening the dev tools (F12) might temporarily mitigate it.
Thank you for your understanding as we work towards a solution!
We're actively investigating this behavior, and in the meantime, if you encounter this problem, opening the dev tools (F12) might temporarily mitigate it.
Thank you for your understanding as we work towards a solution!
@TomaGo It’s a strange situation where the issue stops occurring when I open the developer tools, making it difficult to debug. I searched for known issues with the postMessage API but haven’t found anything helpful so far. My next step is to try alternative Firefox-based browsers in the hopes that the bug will be visible for inspection there.