Compositionend event is unexpectedly followed by input event

Fixed Issue #11930283

Details

Author
Kagami R.
Created
May 7, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
  • Firefox
Standard affected
UI Events

Found in build #
15.16188
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

With Korean keyboard:

  1. Go https://dvcs.w3.org/hg/d4e/raw-file/tip/key-event-test.html

  2. Type ‘tkt’ on Korean keyboard so that the resulting character be ‘삿’

  3. Check the latest event fired when value ‘삿’

  4. Without focus move, type ‘i’ so that the resulting word be ‘사샤’

  5. Expected: one compositionend event with ‘사’ and one input event with '사샤’, actual: one compositoinend+input event with ‘사’ and another input event with ‘사샤’)

  6. Press right arrow button

  7. Expected: one compositionend event and zero input event, actual: one compositionend+input event


With Japanese keyboard:

  1. Go https://dvcs.w3.org/hg/d4e/raw-file/tip/key-event-test.html
  2. Type ‘maki’ so that the resulting word be まき
  3. Press enter
  4. Expected: one compositionend event and zero input event after pressing enter, actual: one compositionend+input event

Mozilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1305387
Please see other feedbacks in userfeedback VSO for feedbacks that are tracked by this work item.

h3 {
color:#2f5496;
font-family:Segoe UI;
font-size:small;
padding-left:3%;
}

table {
font-size:small;
width:95%;
}

th, td {
font-size:small;
padding:5px;
}

td {
border:0.5px solid white;
}

th {
background-color:#8B8989;
color:white;
}

.feedback-leftcell {
width:20%;
color:#004d8b;
}

.feedback-row:hover {
background-color:#C4C4C4;
}

#feedback-banner, #feedback-footer {
background-color:#0078D7;
color:white;
width:100%;
}

#feedback-banner td, #feedback-footer td {
border:0;
font-size:larger;
padding:10px;
}

#feedbacksection-v5 {
font-family:Segoe UI;
border:5px solid #0078D7;
border-collapse:collapse;
}

#feedbackdetails-table, #feedbackanalysis-table, #feedbacklinks-table {
font-family:Calibri Light;
background-color:#f5f5f5;
}

            
        

        This Bug was created from feedback triage by Atsushi Koyatsu

    



Report Details



    
        Feedback Details

        Description

    

    
        Title

        GIP: JPN IME: Edge: TOYOTA:  The first character is finalized automatically.


    

    
        Description

        Enable GIP.
  1. Launch Edge.
  2. Open TOYOTA(http://toyota.jp/)
  3. Select the search box.
  4. Japanese IME On.
  5. Type “kyouha”

Actual:
“きょ” is finalized automatically.

Expected:
The composition containing "きょうは” should appear on the search box and it should not be finalized.

Note:
This happens only on Edge on TOYOTA combination.

Not reproduced in RS3 (TSF1 IME).

Not repro with 3rd party IME (e.g. Google IME).

Not repro with IE,Chrome, Firefox.

The input in STEP5 is reproduced with a hardware keyboard and a touch keyboard.

[Original language] Enable GIP.

  1. Launch Edge.
  2. Open TOYOTA(http://toyota.jp/)
  3. Select the search box.
  4. Japanese IME On.
  5. Type “kyouha”

Actual:
“きょ” is finalized automatically.

Expected:
The composition containing "きょうは” should appear on the search box and it should not be finalized.

Note:
This happens only on Edge on TOYOTA combination.

Not reproduced in RS3 (TSF1 IME).

Not repro with 3rd party IME (e.g. Google IME).

Not repro with IE,Chrome, Firefox.

The input in STEP5 is reproduced with a hardware keyboard and a touch keyboard.

        Area Path

        UIF\Input and Language\Text Input

    

    
        [Feedback Hub](https://aka.ms/feedbackhuburi/?ContextId=330&feedbackId=31044a11-63d6-4e45-ace6-881ecd4d8dbb&form=1&src=1)

        View this Customer Feedback details and comments in the Feedback Hub app.

    

    
        [Feedback VSO](../7056411/)

        View this Customer Feedback in Feedback VSO.

    

    
        [Upvoted By](https://aka.ms/feedbackinternalupvoters?vsoId=7056411)

        Contact selfhosters that upvoted this issue.

    

    


Analysis and Diagnostics


    
        Tool

        Description

    

    
        [Feedback Cabs](http://aka.ms/FeedbackViewer/?txtUifId=31044a11-63d6-4e45-ace6-881ecd4d8dbb&section=Cabs)

        
            
                Looking For CAB files related to feedback?

All CABs for
this feedback can be accessed in the Feedback Viewer.

                Note:

CABs may take up to 12 hours
to process through the
telemetry pipeline. CABs age out and are removed after 60 days
due
to Watson retention policies.

        [Feedback Analysis](http://aka.ms/FeedbackViewer/?txtUifId=31044a11-63d6-4e45-ace6-881ecd4d8dbb)

        
            
                Want to understand how this feedback is trending across various pivots?

                With the Feedback Viewer, you can view trending information for this feedback,
                including upvotes by build, region, time, device, and more. Try out the prototype
                version of our [WAAS Lightspeed](https://aka.ms/waaslightspeed/?txtUifId=31044a11-63d6-4e45-ace6-881ecd4d8dbb)

that includes intelligent auto analyzed
insights, dimensional, detailed diagnostic and telemetry analysis

        [Related Watson Crashes](http://watson/User?Identifier=g:6896140125269178&Expand=true&StartDate=28-May-2018&EndDate=28-May-2018&DateTimeFormat=UTC&EventCategory=All)

        
            
                
                    Want to view Watson crashes that occurred on the same day from the user who
                    filed feedback?

The Watson Viewer will let you dive into crash data.

        [Device Drill](http://devicedrill/EventBrowser?dataSet=ALL&deviceId=g:6896140125269178&focusTimeStamp=2018-05-28T03:57:20&durationAfterMin=10)

        
            
                Want to view telemetry events from this customer's device?

Device Drill lets
you dive into the telemetry of the device this from which this feedback was filed.

Other Links


    
        Link

        Description

    

    
        [Feedback FAQ](http://aka.ms/FeedbackFaq)

        
            
                See the Feedback FAQ for more information about subjective user feedback.
            

        

    

    
        [Where's my CAB? Wiki](http://aka.ms/whereismycabwiki)

        
            
                If you were expecting a CAB but it does not appear in the viewer, please
                see the wiki for more information.
            

        

    

    
        [Translation Volunteers](https://aka.ms/feedbacktranslationvolunteers)

        
            
                For translation assistance, please see the translation volunteers wiki.
            

        

    

    
        [Reporting child pornography](http://aka.ms/FeedbackReportAbuseAndChildPornographyWiki)

        
            
                If attached screenshot(s) is child pornography you must report it using
                instructions listed at the link.
            

        

    






    
        
            Be Heard.
        

        
            [
                //aka.ms/feedback
            ](https://aka.ms/feedback)

Attachments

0 attachments

    Comments and activity

    • Changed Steps to Reproduce

      Changed Steps to Reproduce

      Changed Title from “One keypress fires double input events with Korean keyboard” to “Compositionend event always be followed by input event even without DOM changes”

      Changed Title from “Compositionend event always be followed by input event even without DOM changes” to “Compositionend event is unexpectedly followed by input event”

      Changed Steps to Reproduce

      Changed Steps to Reproduce

      Changed Steps to Reproduce

      Changed Steps to Reproduce

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

      Changed Assigned To to “Grisha L.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Grisha L.” to “Vladimir S.”

      Changed Status from “Confirmed” to “Fixed”

      Changed Steps to Reproduce

    You need to sign in to your Microsoft account to add a comment.

    Sign in