float-container width is not matching with table width
flexkiran opened this issue · 4 comments
flexkiran commented
I am using latest floatThead version 2.1.2
https://jsfiddle.net/k4kiran/Luayektz/2/
while zooming from 100% to 200% head does not resize to match table width.
It works for initial zoom levels.
mkoryak commented
On mobile, so I haven't looked at it in depth, but I can already tell you
that zooming is not supported because there is no zoom event I can listen
to.
Correct me if I'm wrong
On Jul 11, 2018 4:31 AM, "Kiran Patil" <notifications@github.com> wrote:
I am using latest floatThead version 2.1.2
https://jsfiddle.net/k4kiran/Luayektz/2/
while zooming from 100% to 200% head does not resize to match table width.
[image: screen shot 2018-07-11 at 4 26 27 pm]
<https://user-images.githubusercontent.com/3242418/42559843-dcd54f4e-8527-11e8-9691-4da97a7f9d2a.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#423>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAXbSe1_EMPyN3tWG3wGYtzmHv5r68jKks5uFbfugaJpZM4VKtT4>
.
flexkiran commented
Thanks Misha for quick reply.
Yes I am aware about zoom event not supported.
But it is also not working when I destroy and redraw float header on zoom/resize.
mkoryak commented
Ok this is true, but since I cannot detect that zoom is happening, there is
no way I can support it. Things get weird when the page is zoomed. Sorry.
…On Wed, Jul 11, 2018 at 8:35 AM, Kiran Patil ***@***.***> wrote:
Thanks Misha for quick reply.
Yes I am aware about zoom event not supported.
But it is also not working when I destroy and redraw float header on
zoom/resize.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#423 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAXbSajFxhSvpTtZWG8Y5iYn-CofiCaWks5uFfEYgaJpZM4VKtT4>
.
lock commented
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.