Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen
Archiviert

Firefox Quantum 68.4.2esr (64-bit) control-delete deletes span after whitespace

David.Hudson1

The following HTML is inside a text area div:

<wbr><span dir="ltr" class="code" data-id="3" data-ref="0" data-type="SC" data-isolated="false" draggable="false" data-text="span1" contenteditable="false">span1</span>a <span dir="ltr" class="code" data-id="0" data-ref="3" data-type="EC" data-isolated="false" draggable="false" data-text="span2" contenteditable="false">span2</span> b<span dir="ltr" class="code" data-id="2" data-ref="0" data-type="PH" data-isolated="true" draggable="false" data-text="span3" contenteditable="false">span3</span><wbr>

(The WBR elements shouldn't make a difference, but I need them in my test setup.)

Placing the cursor before the "a " and pressing control-delete causes not only the "a " to be deleted, but also span2 and the following space character. Similarly, placing it before "b" and pressing control-delete also deletes span3.

It is as if control-delete treated spans as whitespace, rather than as non-whitespace.

The following HTML is inside a text area div: <pre><nowiki><wbr><span dir="ltr" class="code" data-id="3" data-ref="0" data-type="SC" data-isolated="false" draggable="false" data-text="span1" contenteditable="false">span1</span>a <span dir="ltr" class="code" data-id="0" data-ref="3" data-type="EC" data-isolated="false" draggable="false" data-text="span2" contenteditable="false">span2</span> b<span dir="ltr" class="code" data-id="2" data-ref="0" data-type="PH" data-isolated="true" draggable="false" data-text="span3" contenteditable="false">span3</span><wbr></nowiki></pre> (The WBR elements shouldn't make a difference, but I need them in my test setup.) Placing the cursor before the "a " and pressing control-delete causes not only the "a " to be deleted, but also span2 and the following space character. Similarly, placing it before "b" and pressing control-delete also deletes span3. It is as if control-delete treated spans as whitespace, rather than as non-whitespace.

Geändert am von cor-el

Alle Antworten (8)

The HTML didn't get escaped, and I don't see a way to edit the description. Here is what I hope to be the correctly-escaped version:

<wbr><span dir="ltr" class="code" data-id="3" data-ref="0" data-type="SC" data-isolated="false" data-text="span1" draggable="false" contenteditable="false">span1</span>a <span dir="ltr" class="code" data-id="0" data-ref="3" data-type="EC" data-isolated="false" data-text="span2" draggable="false" contenteditable="false">span2</span> b<span dir="ltr" class="code" data-id="2" data-ref="0" data-type="PH" data-isolated="true" data-text="span3" draggable="false" contenteditable="false">span3</span><wbr>

Can't reproduce it. For me ctrl+del works as advertised: Deletes word to the right.

TyDraniu said

Can't reproduce it. For me ctrl+del works as advertised: Deletes word to the right.

Control-delete should be deleting whitespace following the word to the right, in addition to the word to the right.

This bug does not occur in Firefox 60.7.0esr (64-bit) on CentOS 7. Perhaps it is Windows-specific. However, in that CentOS-7 environment, Firefox does fail to delete the whitespace following the word to the right.

Geändert am von David.Hudson1

TyDraniu said

Fx74, win 10.

I just tried this in the Nightly build, and the bug is still there. Is there a setting required?

See also the layout.word_select prefs on the about:config page.

cor-el said

See also the layout.word_select prefs on the about:config page.

Setting layout.word_select.eat_space_to_next_word does work around the bug. But Firefox shouldn't be treating a span as whitespace.

TyDraniu said

Fx74, win 10.

Do you happen to have layout.word_select.eat_space_to_next_word in about:config set to false?