The css position of the texteditor-popover is relative to the .framework7-root element, but it seems it is calculated relative to the html element.
Therefore, If the dev limit the size of the body element (for example on big screens), then the popover is incorrectly positioned
Observe that it is offset as much as the red padding
Expected behavior
Since the popover is relative to the .framework7-root element, the top and left position should be computed accordingly.
Note : even better (but more complex), the popover should be relative to the text-editor element, so it scrolls with it.
Actual Behavior
top and left are computed relative to html element.
Additional context
It's not really a bug since resizing the app is not part of Framework7.
But I believe it's a common need (on 21:9 screens, having the app fullwidth is not very elegant), and since it's not very hard (substract the position of the .framework7-root to the element coordinates), it could be a good improvement! :)
Describe the bug
The css position of the texteditor-popover is relative to the
.framework7-root
element, but it seems it is calculated relative to thehtml
element. Therefore, If the dev limit the size of thebody
element (for example on big screens), then the popover is incorrectly positionedTo Reproduce
Steps to reproduce the behavior:
Expected behavior
Since the popover is relative to the
.framework7-root
element, thetop
andleft
position should be computed accordingly. Note : even better (but more complex), the popover should be relative to the text-editor element, so it scrolls with it.Actual Behavior
top
andleft
are computed relative tohtml
element.Additional context
It's not really a bug since resizing the app is not part of Framework7. But I believe it's a common need (on 21:9 screens, having the app fullwidth is not very elegant), and since it's not very hard (substract the position of the .framework7-root to the element coordinates), it could be a good improvement! :)