TrackChanges: fast replacing selected content triggers debugger statement

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • None
    • Affects Version/s: None
    • Component/s: TrackChanges
    • Environment:

      Google Chrome Version 63.0.3239.132 (Offizieller Build) (64-Bit)

      problem

      • Start F12 developer tools
      • Edit a segment
      • Double click on a word
      • type very fast a new word to replace the selected one
      • This triggers the debugger at UtilRange.js:405
        debugger; // if we get here, I missed something
      • Only the first character of the new word was inserted before the debugger comes up

      solution

      This issue has no affect if F12 development toolbar is disabled so that debugger is not triggered. This is the case for chrome, but can be different for other browsers. So probably nothing is missed there, but the debugging /debugger invocation should be improved so that no normal user runs into the debugger statement.

      Found that issue on testing TRANSLATE-1113

            Assignee:
            Ines-Paul Baumann (Inactive)
            Reporter:
            Thomas Lauria
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: