Silder in v0.12 breaks with smartphone turning about cometvisu HOT 5 OPEN

@peuter right now my analysis of the issue is in a dead end. Could this be a timing issue where the changePageSizeInvalid is sent before the reading of the available space with window.getComputedStyle() is giving the correct number?

from cometvisu.

Seems like a timing issue, if I just defer the __invalidateScreensize call (in Slide.js constructur) it works for me:

this.__pageSizeListener = cv.ui.layout.ResizeHandler.states.addListener('changePageSizeInvalid', () => {
   (new qx.util.DeferredCall(this.__invalidateScreensize, this)).schedule();
});

(only tested in chrome with device emulation).

Maybe we need another event that is sent when the page size is valid again and you have to listen to that one?

from cometvisu.

Documentation is very sparse about browser generated events during and after a page turn and validation.

In the meantime, and as I'm currently suspecting that only 0.12 is affected I created a hotfix that should suffice as a band aid.

from cometvisu.

In the meantime, and as I'm currently suspecting that only 0.12 is affected I created a hotfix that should suffice as a band aid.

That suspection is wrong, I can easily reproduce the same behaviour with the current development-branch. But my fix also works there, so I assume yours will too. So I suggest to cherry-pick it into the development branch. But there is one additional problem in the dev-branch: Inititialy the slider knob is way too far left (initial value is 100%), the fix does not change that.

from cometvisu.

This issue actually caused multiple troubles on my side as the android browser behaved differently than the desktop chrome - and remote debugging of the android browser stopped the input events from working there 😲

So it's more a hot fix than a clean fix that solves the underlying timing issue. But it should be easy to cherry pick until there's a real fix.

from cometvisu.