Opened 3 years ago

Closed 14 months ago

#1487073 closed Bug Patches (fixed)

Invisible cursor when replying to a message with html editor (Firefox)

Reported by: JohnDoh Owned by:
Priority: 5 Milestone: 0.8-rc
Component: User Interface Version: git-master
Severity: normal Keywords:
Cc:

Description

Using FF3.6.11 when replying to a message using the HTML editor as default the focus is in the editor and typing appears in the correct place but the cursor is invisible. Delaying the focus by just a short while seems to solve the issue. Also there is a similar issue when you have the sig above the quote, without a short delay the cursor is placed at the start of the last line of the sig, not at the top of the box.

Attachments (2)

rc_html_editor_focus.r4118.patch (906 bytes) - added by JohnDoh 3 years ago.
fix bug that caused focus to jump to editor when composing new message
tinymce_focus.r5959.patch (785 bytes) - added by JohnDoh 15 months ago.
better fix

Download all attachments as: .zip

Change History (10)

comment:1 Changed 3 years ago by alec

  • Milestone changed from later to 0.5-beta

I'm unable to reproduce the issue.

comment:2 Changed 3 years ago by JohnDoh

tbh i found it trickey to repoduce too but then when i connected over a slower connection it became much clearer. i think its something to do with the page loading slower and so not being quiet ready when the JS tries to set the focus, making it wait just half a second seems to get around this.

comment:3 Changed 3 years ago by SKaero

I have seen this problem, it happens more often when nothing was cached but I am also on a slower connection (1.5mb/sec).

Changed 3 years ago by JohnDoh

fix bug that caused focus to jump to editor when composing new message

comment:4 Changed 2 years ago by alec

  • Summary changed from Invisible cursor when replying to a message with html editor to Invisible cursor when replying to a message with html editor (Firefox)

I've found this is Firefox-only issue. The problem is in the moment when editor scripts are downloaded (they are not in browser's cache). I don't like to do this with setTimeout() because this produces visible delay. Also 500ms will be most likely not sufficient for every usecase (connection speed).

comment:5 Changed 2 years ago by alec

Better that setTimeout() would be $(window).load(), but this requires some changes in identity change function.

comment:6 Changed 2 years ago by JohnDoh

the problem still exists in ff4, do you have any suggestions what needs to change in change_identity? I can't figure that out

comment:7 Changed 18 months ago by Enrico204

I can't reproduce the issue with FF 8

Changed 15 months ago by JohnDoh

better fix

comment:8 Changed 14 months ago by thomasb

  • Resolution set to fixed
  • Status changed from new to closed

Applied patch by JohnDoh? in [59c404de].

Note: See TracTickets for help on using tickets.