Skip to main content
sberic
Legend
December 7, 2017
Answered

[Bug Report] <input> element triggers oninput callback more than it should (3x!)

  • December 7, 2017
  • 5 replies
  • 2885 views

[I'm not sure if I should post this here or in the  Extensions / Add-ons Development forum. Bruce Bullis​​: any direction here?]

Description

In CEP panels in Premiere Pro v12.0.0, <input> elements will trigger their oninput callbacks three times for every character input. What's more, the values sent to the callback are all different. A panel consisting entirely of the following HTML:

<!DOCTYPE html>

<html>

    <head>

        <script>

            function showInput(event)

            {

                console.log(event.target.value);

            }

        </script>

    </head>

    <body>

        <input oninput="showInput(event)">

    </body>

</html>

will show nothing but a single input field on an otherwise white canvas. Typing "abc" into that field results in the following output in the console:

.

a

a.

a

ab

ab.

ab

abc

Each character input to the field generates three calls to the showInput function, one each of the following form:

  • [prev_value].
  • [prev_value]
  • [new_value]

A bit more testing shows that the dot (.) that appears indicates the location at which the change will occur. The dot will appear mid-value if a character is added/removed from the middle of the previously existing value. Adding a 'd' character between the 'a' and 'b' of 'abc', therefore, results in the following output:

a.bc

abc

adbc

Versions Tested

This issue reproduces 100% of the time in v12.0.0. This does not occur in v11.1.2.

This topic has been closed for replies.
Correct answer Bruce Bullis

There is no fix currently scheduled, though the issue is still in consideration to be addressed during our next major release.

5 replies

sberic
sbericAuthor
Legend
September 26, 2019

This issue does not reproduce on Premiere Pro 13.1.4 (at least). Seems to be fixed.

 

Yay.

jans55190482
Participant
November 1, 2018

Premiere 12.1.2 still has the problem.

sberic
sbericAuthor
Legend
November 1, 2018

jans55190482  wrote

Premiere 12.1.2 still has the problem.

Does Premiere 13 (based on CEP 9)? I don't have a good test for it at present to run myself...

Participating Frequently
September 26, 2019
This issue is not present in 13.0 anymore.
jans55190482
Participant
May 7, 2018

Premiere 12.1.1 still has the problem.

Is there a schedule here to fix this bug?

Bruce Bullis
Community Manager
Bruce BullisCommunity ManagerCorrect answer
Community Manager
May 7, 2018

There is no fix currently scheduled, though the issue is still in consideration to be addressed during our next major release.

sberic
sbericAuthor
Legend
May 25, 2018

I hope this is scheduled to be fixed soon. A recent "bug fix" in the open source BootstrapVue UI component library adjusted the code such that BootstrapVue's input elements now trigger this bug.

I have written of the negative consequences of the change in a comment on the merge commit. That said, it's definitely not a problem on their end...

sberic
sbericAuthor
Legend
December 7, 2017

Also, perhaps related to this: deleting a selection of text in an <input> field will delete the selected text plus one additional character, if it exists.

Seems text <input> tags are pretty broken in v12.0.0...

Inspiring
December 8, 2017

Hi Eric,

While these forums are a good place to discuss bugs to trade notes and look for workarounds, generally it's not the place to report bugs.  I'll check to see where your bug report should be directed.

Zac

Inspiring
December 10, 2017

Just closing the loop.  Eric's bug is in the system as CEP-1058.

CEP issues can be raised here, especially while Bruce is out:

https://github.com/Adobe-CEP/CEP-Resources/issues

sberic
sbericAuthor
Legend
December 7, 2017

I should note that this causes severe headaches when attempting to validate user input for a given <input> field.