You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When switching from FlipbookViewer to SeparateFramesViewer the scale attribute is not being set correctly. Specifically, in the SeparateFrame.js the scale value is not being calculated correctly due to incorrect values from the subjectImage.current?.getBoundingClientRect() calculation.
Add console.log() statements for the zoom and scale variables right before the component is returned (line 207)
Switch to separate frames view from the UI. Note the zoom and scale values
Click to zoom in & then zoom out. Note that the zoom is the same (1) and the scale is vastly different (.214 to .792) for myself
The calculation for the scale is dependent upon the subjectImage.current?.getBoundingClientRect() to be correct and for some reason it's not when we switch viewers. Zoom in + out correctly recalculates, but the initial render does not.
Screenshots
Expected behavior
The scale should be correctly calculated when switching the view.
The text was updated successfully, but these errors were encountered:
Package
Describe the bug
When switching from FlipbookViewer to SeparateFramesViewer the
scale
attribute is not being set correctly. Specifically, in the SeparateFrame.js thescale
value is not being calculated correctly due to incorrect values from thesubjectImage.current?.getBoundingClientRect()
calculation.To Reproduce
Steps to reproduce the behavior:
lib-classifier
locally.console.log()
statements for thezoom
andscale
variables right before the component is returned (line 207)zoom
andscale
valuesThe calculation for the scale is dependent upon the
subjectImage.current?.getBoundingClientRect()
to be correct and for some reason it's not when we switch viewers. Zoom in + out correctly recalculates, but the initial render does not.Screenshots
Expected behavior
The scale should be correctly calculated when switching the view.
The text was updated successfully, but these errors were encountered: