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

Support for DOM events is broken in IE11 on Windows 10 #2332

Closed
pmmf85 opened this Issue Apr 30, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@pmmf85

pmmf85 commented Apr 30, 2017

Help us to manage our issues by answering the following:

  1. Describe your issue:
    DOM Events connected to HTML tags are broken in IE11 (Windows 10).

<input ref="input" onkeyup={ edit }>

Triggering keyup will provide error:

edit is undefined
function onkeyup(event)
{
{edit}
}

3.4.0 March 26, 2017 - works well
3.4.1 April 9, 2017 - does not work

  1. Can you reproduce the issue?
    Visit and play with it for a bit and you should notice errors
    http://riotjs.com/examples/plunker/?app=todo-app

  2. On which browser/OS does the issue appear?
    Windows 10, IE 11, Compatibility mode: IE 11 (Default) - not touched
    Note that on windows 8.1 Compatibility mode for IE 11 is not present. I can only choose IE 10 and Edge (Default). Error is not present on Win8.1

  3. Which version of Riot does it affect?
    3.4.1 and above

  4. How would you tag this issue?

  • Question
  • Bug
  • Discussion
  • Feature request
  • Tip
  • Enhancement
  • Performance

GianlucaGuarini added a commit that referenced this issue Apr 30, 2017

@GianlucaGuarini

This comment has been minimized.

Show comment
Hide comment
@GianlucaGuarini

GianlucaGuarini Apr 30, 2017

Member

I guess this patch should solve the problem even if i am not able to reproduce it

Member

GianlucaGuarini commented Apr 30, 2017

I guess this patch should solve the problem even if i am not able to reproduce it

@perkastman

This comment has been minimized.

Show comment
Hide comment
@perkastman

perkastman May 15, 2017

We had the same problem, but upgrading to 3.5.0 solved it, so I can verify that the fix worked.

We had the same problem, but upgrading to 3.5.0 solved it, so I can verify that the fix worked.

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