-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IE11 - did someone get it to work? #46
Comments
Hi @ThomasSchoenbeck , I was trying to maintain a cross-browsers compatibility but I just verify that is not working anymore on IE11. I'm having a look, sorry about that. |
Same issue using Microsoft Edge and Firefox. No errors in console but the tour doesn't start. |
It should be fixed now. Check out the new version 2.2.9. |
In Edge now it works fine. In Firefox now ngx-joyride events are logged in console but still the tour doesn't start. No errors in console |
Hi @fabio-cometti, Which version of Firefox are you using?Since it was already working for me. |
That's weird!I'm using the same version and it works!Can you please share your dependency list? (also via mail if you prefer) |
Sure! Here: "dependencies": { |
Thanks a lot @tnicola . It's working in IE11 now/again. |
@fabio-cometti I've tried with your dependencies and everything seems working fine in Firefox 65.0.2 64 bit. Can you please try this in your Firefox browser?Does it work? |
Ok, I'have found the problem: I have a mat-icon with a (click) event that start the tour. In firefox seems that mat-icon doesn't fire the event, so I wrapped it in a button and now it works. Thanks for your support |
Glad you've found the problem. :) Thanks |
Hi there,
The tour i build into my app using this library is working in chrome as expected. My company still uses IE11 a lot, so we have to support this browser as well.
Strangely the tour is not working in IE11. There is no error message, everything seems fine. The function itself has a console.log, so i know it get's executed.
the tour just does not appear on screen.
The text was updated successfully, but these errors were encountered: