# הסמן מתנהג מוזר במחבר - הוא נעלם כשאני מזיז אותו למעלה/למטה
**URL:** https://meta.discourse.org/t/cursor-behaves-weirdly-in-the-composer-it-disappears-as-i-move-it-up-down/210208
**Category:** UX
**Created:** [26 בנובמבר, 2021, 7:05am UTC](https://meta.discourse.org/t/cursor-behaves-weirdly-in-the-composer-it-disappears-as-i-move-it-up-down/210208 "2021-11-26T07:05:12Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@meglio](https://meta.discourse.org/u/meglio)
#### Post date: [26 בנובמבר, 2021, 7:05am UTC](https://meta.discourse.org/t/cursor-behaves-weirdly-in-the-composer-it-disappears-as-i-move-it-up-down/210208/1 "2021-11-26T07:05:12Z")
As you move cursor up/down by pressing on the up/down arrows, the cursor sometimes disappears for half a second and makes you wonder - where is the cursor? Have I moved it up/down enough? Am I on the right line?
The cursor does not actually disappear per se - it continues to blink with the correct interval. But the way it is currently implemented is not the way it is implemented everywhere else - in text editors, in the browser inputs, in IDEs, etc.
Compare.
Here’s the cursor in Discourse:
Note how I easily manage to quickly press up or down two times and make the cursor invisible while on an empty line. This makes me feel as the cursor disappears and I lose it from sight, and therefore cannot control it precisely.
Compare it to how the cursor works in JSFiddle, as an example:
Note: it doesn’t matter how fast I press on the up/down button, the cursor is always visible as it moves from one line to another. In other words, the blinking “resets” as the cursor moves to another line.
Hope the two videos explain the issue clearly and make it an easy consideration to fix the issue.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [29 בנובמבר, 2021, 6:10am UTC](https://meta.discourse.org/t/cursor-behaves-weirdly-in-the-composer-it-disappears-as-i-move-it-up-down/210208/2 "2021-11-29T06:10:56Z")
Yeah, Firefox bug.
Seen it on Linux, have not noticed it on Windows though.
See:
> [@Issue writing messages or topics in Firefox](https://meta.discourse.org/t/issue-writing-messages-or-topics-in-firefox/117440):
>
> I think this issue might be a little niche, but it’s something I’ve been experiencing for at least a week, first I thought it was just my forum, but I just happened to see it on Meta. I’m running Firefox 60.6.2esr on Debian 9. The issue is that every time I try to write a message in Discourse the pointer thingy doesn’t appears (the texts gets written), so I don’t get text correction, nor the ability to add Latin characters. Just clicking away anywhere and then clicking back to continue writing…
> [@Cursor does not appear in reply field with Waterfox browser](https://meta.discourse.org/t/cursor-does-not-appear-in-reply-field-with-waterfox-browser/120841):
>
> When I start a reply in the Waterfox browser even on this forum, the cursor does not appear when typing, making it difficult to reposition the cursor to edit text: [Cursor%20missing] The cursor displays fine when I start a new topic or private message, but does not appear when I reply to an existing topic or private message. This issue does not occur on Chrome or Edge. On the Discourse based forum I take care of, someone mentioned the cursor does not appear on their Firefox browser when repl…
> [@Arrow keys in Firefox](https://meta.discourse.org/t/arrow-keys-in-firefox/204172):
>
> Arrow keys in the editor started acting a little strange in Firefox a few versions ago. The up and down arrows sometimes require an extra press to get past paragraphs. To reproduce: Create a new default Firefox profile. I was using Ubuntu 20.04. firefox --new-instance --profile $(mktemp -d) & Start a new forum post. Make a few paragraphs. Push the up and down arrow keys and watch for keypresses that don’t move the cursor. Also, I’m not sure if this is a bug or if it was intended, but the ta…
See: [https://bugzilla.mozilla.org/show\_bug.cgi?id=226301](https://bugzilla.mozilla.org/show_bug.cgi?id=226301)
---
### Author:  [@meglio](https://meta.discourse.org/u/meglio)
#### Post date: [29 בנובמבר, 2021, 7:15am UTC](https://meta.discourse.org/t/cursor-behaves-weirdly-in-the-composer-it-disappears-as-i-move-it-up-down/210208/3 "2021-11-29T07:15:31Z")
But wait, my second video is recorded in Firefox too, and there is no such a problem. Also, I know the reproduction steps exactly, it does not disappear “sporadically” as in the report you linked to. Is this because jsfiddle uses their own rendering mechanism of the cursor while Discourse uses the default textarea and thus is affected by the default cursor Firefox behaviour?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [29 בנובמבר, 2021, 7:26am UTC](https://meta.discourse.org/t/cursor-behaves-weirdly-in-the-composer-it-disappears-as-i-move-it-up-down/210208/4 "2021-11-29T07:26:18Z")
> [@meglio](#):
>
> Is this because jsfiddle uses their own rendering mechanism of the cursor while Discourse uses the default textarea and thus is affected by the default cursor Firefox behaviour?
JSFiddle is not using a TEXTAREA it is using a contenteditable HTML element, TEXTAREA does not support all that highlighting.
Recommend you post on that Firefox bug I linked, looks exactly like what you are seeing.