another conflict with Jordan's input field plugin

[mamezito-zz]

i need to use both modules and input fields in a project (using your to have keyboard events)
and using Jordans to have camera input
and seems if i am using one, the second becomes broken
try clicking on photo, then type something in ioskit field
https://www.dropbox.com/s/hy6yvv6n7tzjp4z/Screenshot%202016-08-19%2023.48.58.png?dl=0

try select image first, then click on the field
http://share.framerjs.com/zabjogtdnijm/

input module
http://framerco.de/post/136846506048/module-inputfield-class-update-this-module-has

[k-vyn]

Wow, this is toughy. I'm familiar with the error in your screenshot. That's typically from the layout engine trying to access a layer that doesn't have a constraint declared, similar to the other issue where I just said to write .constraints ={}. I'm working on a fix for that, which I'll try to finish & push tonight.

What's weird is when I tested it I got -

InputField.coffee:240 Uncaught InvalidStateError: Failed to set the 'value' property on 'HTMLInputElement': This input element accepts a filename, which may only be programmatically set to the empty string.

This error message I'm not at all familiar with.

[jordandobson]

Can you set me up with an example and I can take a look too and make sure
it's not me.

I wonder if you're trying to set a value which it can't accept? Being that
it's a file input!?
On Sun, Aug 28, 2016 at 6:31 PM Kevyn Arnott [email protected]
wrote:

Wow, this is toughy. I'm familiar with the error in your screenshot.
That's typically from the layout engine trying to access a layer that
doesn't have a constraint declared, similar to the other issue where I just
said to write .constraints ={}. I'm working on a fix for that, which I'll
try to finish & push tonight.

What's weird is when I tested it I got -

InputField.coffee:240 Uncaught InvalidStateError: Failed to set the 'value' property on 'HTMLInputElement': This input element accepts a filename, which may only be programmatically set to the empty string.

This error message I'm not at all familiar with.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#12 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACbYtiGb_xjjWX-58bufGmMJJ-7Mfniks5qkjaBgaJpZM4Jo2S7
.

[mamezito-zz]

ok guys , I played with the thing, guess something is messing on JS DOM leve, i thinkts its event listener
something is thinking both fields are same element.
how to test
http://share.framerjs.com/9hx918bt3gl2/
in browser - upload image, then click input text field

[k-vyn]

Ok, I think I've isolated the problem. Jordan's module is calling the changeinputvalue function from events in the iOS Keyboard. I'm not 100%, but it feels like the event has something to do with HTML changes because it's firing from both keypress events & touch events. It's also gets called a bunch if you do the dialog and then click the field for the first time. This is because there are a bunch of HTML changes when the keyboard is created.

Jordan, I'm not sure how to get these to live harmoniously. Can you think of a good fix for this?

Here's an example where I replaced changeinputvalue function with a print statement, and that removed the errors - > http://share.framerjs.com/qm3s023wqqs9/

Edit - to be clear, the changeinputvalue function is only called after the upload dialog.