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

Make JX Browser the fallback and remove settings option #7232

Merged
merged 2 commits into from
Feb 21, 2024

Conversation

helin24
Copy link
Member

@helin24 helin24 commented Feb 20, 2024

This removes the option to select JCEF or JX Browser in settings for simplicity. We will instead check if JCEF is available first, and if not, download and use JX Browser. Embedded browser failures in IJ (where JCEF is included by default) were very low, so I think it's unlikely users will benefit from having a choice here.

I still need to build this to check whether this is detecting the presence of JCEF accurately.

@helin24
Copy link
Member Author

helin24 commented Feb 21, 2024

This works in my testing. However, I also don't recall what JDK with JCEF I was using in the past - in my current install of Android Studio, when I select this JDK:
Screenshot 2024-02-20 at 4 02 45 PM

I get this error: https://youtrack.jetbrains.com/issue/IDEA-317401

And the browser doesn't even appear:
Screenshot 2024-02-20 at 4 03 10 PM

I think this is largely a non-issue since we won't be recommending Android Studio users try to use a JCEF JDK for now. If people hit this issue we can recommend changing back to their default JDK.

@helin24 helin24 merged commit d5a941c into flutter:master Feb 21, 2024
8 checks passed
@helin24 helin24 deleted the jcef-default branch February 21, 2024 00:27
jwren added a commit to jwren/flutter-intellij that referenced this pull request Mar 6, 2024
jwren added a commit to jwren/flutter-intellij that referenced this pull request Mar 6, 2024
jwren added a commit that referenced this pull request Mar 6, 2024
…" (#7256)

This reverts commit d5a941c.

*Replace this paragraph with a description of what this PR is changing
or adding, and why. Consider including before/after screenshots.*

*List which issues are fixed by this PR. You must list at least one
issue.*

*If you had to change anything in the [flutter/tests] repo, include a
link to the migration guide as per the [breaking change policy].*

## Pre-launch Checklist

- [ ] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [ ] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [ ] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [ ] I signed the [CLA].
- [ ] I listed at least one issue that this PR fixes in the description
above.
- [ ] I updated/added relevant documentation (doc comments with `///`).
- [ ] I added new tests to check the change I am making, or this PR is
[test-exempt].
- [ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel
on [Discord].

<!-- Links -->
[Contributor Guide]:
https://github.com/flutter/flutter/wiki/Tree-hygiene#overview
[Tree Hygiene]: https://github.com/flutter/flutter/wiki/Tree-hygiene
[test-exempt]:
https://github.com/flutter/flutter/wiki/Tree-hygiene#tests
[Flutter Style Guide]:
https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo
[CLA]: https://cla.developers.google.com/
[flutter/tests]: https://github.com/flutter/tests
[breaking change policy]:
https://github.com/flutter/flutter/wiki/Tree-hygiene#handling-breaking-changes
[Discord]: https://github.com/flutter/flutter/wiki/Chat
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.

2 participants