Position bug #43

Closed
kudesa opened this Issue Feb 10, 2014 · 4 comments

Projects

None yet

2 participants

@kudesa
kudesa commented Feb 10, 2014

Hi. I have a problem with timepicker. After first click timepicker shifted to the left by -9px.
I recorded a video http://youtu.be/OG2np1fdnfg
This problem occurs only when you first click after the page loads

Update. If page has vertical scrollbar, all is well

@wvega wvega added this to the 1.3.2 milestone Feb 15, 2014
@wvega wvega added the bug label Aug 30, 2014
@wvega
Owner
wvega commented Aug 30, 2014

@kudesa I'm sorry it took me so long to answer to this issue.

I'm having problems reproducing your issue, although the video was really helpful and gave me an idea of what could be the problem.

Is there any chance you are still using the plugin and have an online version of your example, where I can see the issue happening?

I made a few modifications today, that improved the way the plugin size is calculated. That yielded better results in my tests. I would like to reproduce your problem as accurately as possible to see the modifications are of any help.

@kudesa
kudesa commented Aug 31, 2014

Hello, …

@wvega
Owner
wvega commented Aug 31, 2014

Thank you @kudesa, that is really helpful.

I was able to reproduce the bug in Windows against the latest development version of the plugin, using the following browsers:

  • Chrome 35.0.1916.153 m.
  • Firefox 29.0.1.
  • Chrome 37.0.2062.102 m.
  • Firefox 31.

The problem with the latest version of plugin gets worse, because now it shows style problems, probably more disturbing than the one time incorrect position described in this issue.

The good news is that I'm close to having a solution. I'll update the issue again next week.

@wvega wvega added a commit that referenced this issue Sep 14, 2014
@wvega Add visual test from issue #43. beb30e9
@wvega wvega added a commit that closed this issue Sep 14, 2014
@wvega Fix position bug (Fixes #43). fde2195
@wvega wvega closed this in fde2195 Sep 14, 2014
@wvega
Owner
wvega commented Sep 14, 2014

The new version includes a fix for this problem. I tested the modifications using your example, @kudesa; your code was really helpful to debug this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment