Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incontext Editor sometimes unfocusus text field. #83

Closed
MylesWardell opened this issue Dec 13, 2022 · 3 comments
Closed

Incontext Editor sometimes unfocusus text field. #83

MylesWardell opened this issue Dec 13, 2022 · 3 comments

Comments

@MylesWardell
Copy link

MylesWardell commented Dec 13, 2022

Issue

The in context editor on was unfocusing the translation textarea whenever a developer tried to click it.

Unsure what was causing this as the console was completely clear and other modals worked fine. I dont have the time to do recreate this issue in a codesandbox but thought I should post it somewhere to see if its something obvious.

Ie a dev would click the editor and then then couldn't type text because the input cursor was unfocusing. Our short term solution was adding the text via document.querySelector which isn't ideal but does successfully bypass the textarea field.

Attempts to fix

  • Reverted all code changes on modal
  • Empty Cache hard reload
  • Attempt to change text elsewhere using incontext (still working)
  • Here is a screenshot of the problem modal. As I mentioned previously it contains a bootstrap modal (using react-bootstrap) and several inputs and a dropdown.

image

@github-actions
Copy link

Hi MylesWardell,

Thanks for logging this issue.

In order to further troubleshoot and replicate your issue we require more information about the issue and the organisation you belong to. Please reach out to us separately using the contact form while being logged into your Phrase account or send us an email via [email protected].

Please sure to include the following information:

  • your Phrase username or email address
  • your account name or ID
  • your project name or ID
  • the affected feature and connected IDs
  • a description of the question or problem
  • steps to reproduce it
  • a screenshot, screencast or code snippet showing the issue

Thank you for your understanding.

Best,
Henning from the Phrase Technical Support Team

Comment by Henning

@itsahsiao
Copy link
Contributor

itsahsiao commented Jul 6, 2023

@MylesWardell Not sure if you reached out to our Tech Support Team as per the message above by Henning, but I'm just following up to see if this problem is still persisting?

@itsahsiao
Copy link
Contributor

Closing due to inactivity - please let us know if this is still happening and we can take another look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants