-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Do the final text scaling correctly in flushTextContentItem
(issue 8276)
#10508
Conversation
…8276) It's necessary to take into account whether or not the text is vertical, to avoid either the textContent `width` or `height` becoming incorrect.
…nit-test This unit-test wasn't destroying the `loadingTask` when complete, as it should have done.
/botio test |
From: Bot.io (Windows)ReceivedCommand cmd_test from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.215.176.217:8877/882ce9dd476fc28/output.txt |
From: Bot.io (Linux m4)ReceivedCommand cmd_test from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.67.70.0:8877/c8bb1754454115d/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.67.70.0:8877/c8bb1754454115d/output.txt Total script time: 17.75 mins
|
From: Bot.io (Windows)SuccessFull output at http://54.215.176.217:8877/882ce9dd476fc28/output.txt Total script time: 25.68 mins
|
/botio-linux preview |
From: Bot.io (Linux m4)ReceivedCommand cmd_preview from @timvandermeij received. Current queue size: 0 Live output at: http://54.67.70.0:8877/083868a9fb2babe/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.67.70.0:8877/083868a9fb2babe/output.txt Total script time: 1.69 mins Published |
Thank you for doing this! |
It's necessary to take into account whether or not the text is vertical, to avoid either the textContent
width
orheight
becoming incorrect.Fixes #8276; and subsumes PR #10456.
The other PR caused regressions (as I feared based on looking at its code), which suggests that it wasn't properly tested during development. Furthermore, the PR didn't include any kind of test which is necessary to prevent this from regressing yet again (since the existing tests didn't catch it previously).
Finally, after the PR was opened there hasn't been any response from the author, regarding either the test failures or the other comments, for two weeks which is why I've now chosen to submit this patch.