Skip to content
This repository has been archived by the owner on Jun 9, 2022. It is now read-only.

IE 11 support #68

Open
patriklund opened this issue Jan 8, 2014 · 5 comments
Open

IE 11 support #68

patriklund opened this issue Jan 8, 2014 · 5 comments

Comments

@patriklund
Copy link

Thanks for a great product.

Everybody knows how IE sucks but i still have to pull the question. Do you have any plans to get the scroller to work proper in IE 11?

rowanbeentje added a commit that referenced this issue Jan 16, 2014
…to ensure the inputidentifier is still valid
@rowanbeentje
Copy link
Contributor

@patriklund Could you give v0.3.1 a go? That seems to work with some quick testing for me... sorry it took so long after t'release of IE 11.

(This doesn't address the move to new unprefixed pointer events, which will still need to come later)

@msdevweb
Copy link

I was facing also some issues, not sure if they are related to the very specific configuration of my device or is a common issue.

I have a Asus vivo tab smart, with an Windows 8, (not the RT one) + IE 11. While on <0.3.1 versions the scroller worked with many limitations (many gaps, almost unusable) with the latest version it simply does not work most of the times.

The console seems to point an issue on ftscroller.js, line 2241, column 5, InvalidPointerId

So I went ahead and commented out the two lines:
if (_trackPointerEvents) {
//_containerNode.removeEventListener('MSLostPointerCapture', _onPointerCaptureEnd, false);
//_containerNode.msReleasePointerCapture(_inputIdentifier);
}

And it started working great, only with small inconsistencies when taping on screen for scrolling (stop position seems to be incorrect). So, the question is if this will be a safe solution or will represent an issue on some browsers?

Kind Regards

@rowanbeentje
Copy link
Contributor

@msdevweb Could you give 0.3.5 a go? I spent some time pinning down input capture issues on IE 11 after @georgecrawford sent through some videos.

The error you were getting was a little different (IE11 enforces release must use the same id as that captured, and on the same element, but the calls look balanced to me...) but I think there might be bugs around pointer release.

@patriklund
Copy link
Author

Sorry for late reply. Yes the scrolling works now on IE 11 in my Lumia 2520 with the latest update 0.3.5. Great!

@georgecrawford
Copy link
Contributor

Good news; thanks Patrik!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants