-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Input helper shows unwanted behaviour in firefox with jquery 2.2.1 #13112
Comments
@crudo1f please create a code example, e.g. jsbin or ember-twiddle so others can quickly reproduce the "unwanted behavior". This may also be useful for discussion on the embercommunity.slack.com chat rooms to see if anyone has found a work around. This does sound like an edge case, only new jQuery v2.2, Ember v2.4 and Firefox (mac & pc?) |
I am experiencing this too, but in very limited circumstances. Seems to be FireFox, not Chrome or IE Edge. Happens with ember 2.4.3 but not 2.3.2. Does not happen, at least for me, in a standalone In some cases the insertion point is missing. In others, it is as described in the report above: fixed, blinking insertion point positioned at text offset 0, but too low. Unfortunately, there must be some other contributing factors. I took the branch of ember-paper that I'm using ( Let me know what experiments I can try to help narrow this down and I'll perform them. Thanks much. |
Ding, ding, ding. Forcing jQuery from 2.1.4 to 2.2.1 reproduces the issue. To reproduce:
"ember": "~2.4.3",
"jquery": "2.2.1",
|
@pixelhandler here is an ember twiddle example: In this case the cursor is not misplaced but it is missing. Just in FF! |
So this is likely to be a jQuery bug? Has anyone searched there issue tracker for something like this? |
I found nothing before I opened this issue. But I was not sure if it is a jQuery issue or an ember issue about jQuery integration. Maybe I have some time to look into this, later. |
I don't see anything in the jQuery issue tracker. Version 2.2.x is not even in the list of issues you can search for, and "insertion point" returned nothing related. |
@crudo1f please confirm whether this should be filed in the jQuery tracker instead, and if so close this one. Appreciated! |
I have the same problem in my project and have to use jquery 2.1.4 to fix it. Would be great, if this could be filed in the jQuery tracker or the jquery integration checked. |
I'm not too sure that it's a JQuery issue. First, using Second, returning
but the input box behaves / looks as expected. |
@avdv the error message tries to be very clear, what do you feel is nasty about it? Doing |
It's nasty in the sense that it's bad (the warning itself, not the message). Do nasty things and you get nasty warnings. No pun intended. |
I'll close this for now, it doesn't seem to be an Ember.js bug. |
Got the same issue but I figured out a different workaround by just adding https://ember-twiddle.com/f37ebd8634908049f45594bdc93cf8a4?openFiles=application.template.hbs |
To the extent that Ember recommends a version of jQuery that contains a bug that is incompatible with Ember, I personally think this is an Ember configuration bug. Ember should not accept 2.2.1 if it doesn't work with it, even if it isn't Ember's fault. |
Returning false from a Firefox does not have support for Thank you! |
I have a component which uses the input helper like this:
{{input value=model.value focus-in='focusInAction'}}
Since the upgrade to Ember 2.4.x these inputs show a strange behaviour. The cursor is misplaced on a fixed spot (left side and shifted down) in the text input or in some cases it is not visible. Beside this the input and all actions work as expected. The error does only appear on inputs with the focus-in action handled and just in Firefox.
Till now I could narrow this down to the new jquery version (2.2.1) which comes with the latest Ember version. If I use jquery 2.1.4 with Ember 2.4.x everything works as expected.
Example with missing cursor in FF:
https://ember-twiddle.com/50fdee3aee87c09c7fd8
Any ideas about that?
The text was updated successfully, but these errors were encountered: