Same here as well. Version 1.16.2. Chrome and Edge freezing up. Wasn't happening prior to 1.16.2 for me.

Chrome Version 101.0.4951.64 (Official Build) (64-bit)

santiagi Yep I experience 100% the same issue. This is definitely a bug in OSticket 1.16.2. Glad to know it's not just me.

    Same issue here

    • Chrome 101.0.4951.64
    • osTicket (v1.12)

    Everyone,

    We don’t develop the text editor so seeing it replicated isn't necessary. We have opened a ticket with the developers of the text editor. We are now awaiting an update from them.

    Cheers.

    Here is a workaround for 1.16.2 file: support/include/staff/ticket-view.inc.php starting at line 1044:
    Add a <br> after the input line.
    No idea why it works or if this is the best workaround, but it works for me 😉

    <input type="hidden" name="draft_id" value=""/>
    <br>
    <textarea name="response" id="response" cols="50"
    data-signature-field="signature" data-dept-id="<?php echo $dept->getId(); ?>"
    data-signature="<?php
    echo Format::htmlchars(Format::viewableImages($signature)); ?>"
    placeholder="<?php echo __(
    'Start writing your response here. Use canned responses from the drop-down above'
    ); ?>"
    rows="9" wrap="soft"
    class="<?php if ($cfg->isRichTextEnabled()) echo 'richtext';
    ?> draft draft-delete fullscreen" <?php
    list($draft, $attrs) = Draft::getDraftAndDataAttrs('ticket.response', $ticket->getId(), $info['response']);
    echo $attrs; ?>><?php echo ThreadEntryBody::clean($_POST ? $info['response'] : $draft);
    ?></textarea>

      emmanuelsf My favorite coding technique trial-and-error. . And a little prayer 😉

      And I looked at the code for the Note Details tab and saw it did not have a <input just before so I tried adding a <br> and that worked.

          jarnott

          I will test this out and make a pull if it works. We will still await an update from the developers for a permanent solution.

          Cheers.

            5 days later

            I created an account just to say thank you to @jarnott and @KevinTheJedi for this fix.

            I've been playing around setting up and testing OSTicket for about 3 weeks without seeing this issue, one day after I put it into semi-production I start seeing this problem in Chrome. Bizarre! I guess I never deleted back to the beginning of the reply form in my testing...

            12 days later
            3 months later
            Write a Reply...