-
Notifications
You must be signed in to change notification settings - Fork 493
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
8342565: [TestBug] StubTextLayout #1667
base: master
Are you sure you want to change the base?
8342565: [TestBug] StubTextLayout #1667
Conversation
👋 Welcome back angorya! A progress list of the required criteria for merging this PR into |
❗ This change is not yet ready to be integrated. |
Webrevs
|
@andy-goryachev-oracle This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
This seems like a Skara bug to me. This PR was just taken out of Draft and has several recent commits pushed to it. |
I doubt that. |
Since this touches product code (in a minor way), I'd like two reviewers. /reviewers 2 |
@kevinrushforth |
|
||
private static double toViewPortLength(double prefHeight) { | ||
// it would be better to calculate this from listView but there is no API for this | ||
return prefHeight - 2; |
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.
I think after this node is inside the scene tree and has a skin, you can just calculate that with:
prefHeight(-1) - snappedTopInset() - snappedBottomInset()
.
Something like that I already used.
Also, Viewport
is one word, so should not be camel case.
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.
using prefHeight(-1) - snappedTopInset() - snappedBottomInset()
breaks the original test, I'd rather avoid that (all I did was minor refactoring to move the logic and the comment into one place).
thanks for -> toViewportLength()
I think this is a good change, completely utilizing that the text layout code is abstracted away for good. |
the meaning should be obvious from the context (small, medium, large) and I don't want code like this to take two pages:
|
Changed the StubTextLayout to use product PrismTextLayout with much simplified glyph layout (via stubbed fonts). The new layout assumes all the glyphs are squares of font size, while the bold type face produces wider glyphs (by 1 pixel). The default font size has changed from 10 to 12 to make it closer to win/linux.
This brings the test environment closer to the product configuration and expands the capabilities of our headless testing pipeline, which will be useful for upcoming behavior tests.
Existing tests have been adjusted/reworked mainly due to default font size change.
Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jfx.git pull/1667/head:pull/1667
$ git checkout pull/1667
Update a local copy of the PR:
$ git checkout pull/1667
$ git pull https://git.openjdk.org/jfx.git pull/1667/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1667
View PR using the GUI difftool:
$ git pr show -t 1667
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jfx/pull/1667.diff
Using Webrev
Link to Webrev Comment