• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

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

Enthusiast ,
Dec 07, 2017 Dec 07, 2017

Copy link to clipboard

Copied

[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.

TOPICS
SDK

Views

1.8K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , May 07, 2018 May 07, 2018

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

Votes

Translate

Translate
Enthusiast ,
Dec 07, 2017 Dec 07, 2017

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Dec 07, 2017 Dec 07, 2017

Copy link to clipboard

Copied

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...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Dec 08, 2017 Dec 08, 2017

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Dec 10, 2017 Dec 10, 2017

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Dec 11, 2017 Dec 11, 2017

Copy link to clipboard

Copied

Thanks for pointing out the location to file new issues/bugs, https://forums.adobe.com/people/Zac%20Lam. Two followup questions for you:

  1. I take it that CEP-1058 is a bug number assigned in an Adobe-internal bug tracking system, yes?
  2. Did the details you added to CEP-1058 include descriptions of the text field selection and deletion issue?

Thanks!

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Dec 11, 2017 Dec 11, 2017

Copy link to clipboard

Copied

1. Yes

2. Yes, and I linked to this forum post

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
May 07, 2018 May 07, 2018

Copy link to clipboard

Copied

Premiere 12.1.1 still has the problem.

Is there a schedule here to fix this bug?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
May 07, 2018 May 07, 2018

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
May 25, 2018 May 25, 2018

Copy link to clipboard

Copied

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...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 01, 2018 Nov 01, 2018

Copy link to clipboard

Copied

Premiere 12.1.2 still has the problem.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Nov 01, 2018 Nov 01, 2018

Copy link to clipboard

Copied

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...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Sep 26, 2019 Sep 26, 2019

Copy link to clipboard

Copied

This issue is not present in 13.0 anymore.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Sep 26, 2019 Sep 26, 2019

Copy link to clipboard

Copied

LATEST

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

 

Yay.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines