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

fix: devtool warning by adding parent view, closes #273 #654

Merged
merged 2 commits into from
Aug 9, 2022

Conversation

spwilson2
Copy link
Contributor

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Docs
  • New Binding issue #___
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change?

  • No

Checklist

  • When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
  • A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
  • I have added a convincing reason for adding this feature, if necessary

Other information

@spwilson2 spwilson2 requested a review from a team as a code owner August 6, 2022 04:02
Previously, we would just inject the webview into the contentView of the
NSWindow. When devtools would inject the subView into this top-level content
view, a warning would be displayed.
@keiya01
Copy link
Member

keiya01 commented Aug 6, 2022

Thank you for your contribution.
It looks working great to me!!

@wusyong
Copy link
Member

wusyong commented Aug 6, 2022

I think this will reintroduce the cursor bug.
Can you check if that happens again?

@spwilson2
Copy link
Contributor Author

spwilson2 commented Aug 6, 2022

It doesn't seem to reintroduce it. (And I am able to reproduce #220 when changing to a commit before d550b2f, so it doesn't seem like it's related to just my environment.)

It seems the actual fix for d550b2f is to avoid using the ns_view created by tao. So it seems there's likely a bug there in tao, and the workaround introduced here and in d550b2f should be reverted once that's fixed.

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

Successfully merging this pull request may close these issues.

4 participants