Assigned
Status Update
No update yet.
Comments
pu...@google.com
ar...@google.com
ha...@thedott.io
I also have the same problem:
Project id: restaurant-phone-reservat-b9tt
Location: us-east1
Please have a look, this is a blocker for us.
Thank you!
Project id: restaurant-phone-reservat-b9tt
Location: us-east1
Please have a look, this is a blocker for us.
Thank you!
ar...@google.com
I also have the same problem when trying to update a webhook. Initially it says "Webhook saved successfully!" and shortly it appears "Internal error encountered" and if I refresh the page the changes are not saved.
Do we have an estimated time when these bugs will be solved, please?
Do we have an estimated time when these bugs will be solved, please?
ha...@thedott.io
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
Description
I hope this message finds you well. I would like to apologize for not providing the additional information required to proceed with my previous inquiry due to my busy schedule. Unfortunately, the case was closed before I could follow up. I kindly request your assistance in reopening and reinvestigating the issue detailed below.
Additionally, I understand that the following information is required to proceed with the investigation:
1. Your Google Cloud Project ID/Project Number.
2. Affected agent URL.
3. Exported agent file.
4. Confirmation of whether this issue has ever worked as expected in the same or similar setup.
I am now prepared to share these details; however, I would like to provide this information via a non-public method, as it cannot be shared directly on the issue tracker. Please let me know how to proceed with securely sharing this information.
Previous Inquiry Details:
Issue Tracker URL:
– Issue description (short summary) –
IME (Input Method Editor) for Japanese misinterprets the Enter key used for confirming text input as the submission Enter key, causing premature message submission in df-messenger.js.
– Steps to reproduce the issue (detailed description) –
1. Open a project using df-messenger.js and focus on the input field.
2. Use the IME to input Japanese text.
3. Press the Enter key to confirm the text input in the IME.
– Expected behavior –
The IME confirmation Enter key should be ignored to prevent the text from being prematurely sent. The system should differentiate between the IME Enter key and the submission Enter key.
– Actual behavior –
Pressing the Enter key to confirm Japanese text input via the IME sends the message prematurely, interrupting the input process and negatively affecting the user experience.
– Workarounds (if any) –
None identified. A potential solution might involve detecting the IME state via the keydown event and handling the IME Enter key separately.
– Documentation consulted –
Documentation for df-messenger.js and related resources, but no direct resolution found.
Reference Link
– Other information –
This issue has significant usability implications for projects targeting Japanese-speaking users. Community support or guidance would be greatly appreciated.
Thank you for your understanding, and I sincerely hope this issue can be revisited. Please let me know if additional information is needed to proceed with the investigation.
Best regards,
Takeshi Haga