Repository navigation
[api-minor] Don't re-layout the textLayer on update (PR 20492 follow-up) - #22045
Conversation
|
This seems almost too easy, so I cannot escape the feeling that I've overlooked something trivial in my quick testing. |
|
/botio-linux preview |
From: Bot.io (Linux m4)ReceivedCommand cmd_preview from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.241.84.105:8877/1b97f7ac1922821/output.txt |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #22045 +/- ##
==========================================
- Coverage 90.30% 90.29% -0.01%
==========================================
Files 269 269
Lines 67371 67362 -9
==========================================
- Hits 60838 60825 -13
- Misses 6533 6537 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
From: Bot.io (Linux m4)SuccessFull output at http://54.241.84.105:8877/1b97f7ac1922821/output.txt Total script time: 1.39 mins Published |
Reference testsResults for 049f59a (run, references from mozilla/pdf.js.refs@7ac8f26399).
The report is kept for 30 days and replaced by the next run. |
…w-up) PR 20492 removed the special handling of marked content, which means that the viewer changing the `--scale-factor` should now be sufficient to update the `textLayer` and that it's no longer necessary to re-layout all of its elements.
053b60d to
049f59a
Compare
PR #20492 removed the special handling of marked content, which means that the viewer changing the
--scale-factorshould now be sufficient to update thetextLayerand that it's no longer necessary to re-layout all of its elements.