-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8256372: [macos] Unexpected symbol was displayed on JTextField with Monospaced font #4097
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
Conversation
|
👋 Welcome back prr! A progress list of the required criteria for merging this PR into |
erikj79
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Build changes look ok.
|
@prrace This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 52 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
| @@ -1,1196 +0,0 @@ | |||
| /* | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How we will track these files for the next HB update? Do we need to document it somehow? otherwise, I think it will be added again as a new files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, they won't. We already pull in only the files we need, not every file, so this is not a precedent.
|
/integrate |
|
@prrace Since your change was applied there have been 52 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 005d8a7. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
See the bug report for lots of explanation.
The short version (not that short) is that Swing adds a new line char to editable TextComponents
It used to work because harfbuzz asked CoreText which mapped it to an invisible glyph
Now harfbuzz does its own processing of AAT fonts it is different.
Harfbuzz looks up the mapping for this but there is none so it gets a missing glyph.
Solution: Since HB now does AAT processing we can dispense with all the special handling of that case
and core text and just treat AAT fonts like OT fonts.
This means its gets the same mapping we get when not using Layout.
And the test passes on all platforms .. not just macOS ..
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4097/head:pull/4097$ git checkout pull/4097Update a local copy of the PR:
$ git checkout pull/4097$ git pull https://git.openjdk.java.net/jdk pull/4097/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4097View PR using the GUI difftool:
$ git pr show -t 4097Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4097.diff