Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

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

  • 8 antwoorden
  • 1 heeft dit probleem
  • 28 weergaven
  • Laatste antwoord van David.Hudson1

more options

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.

Bewerkt door cor-el op

Alle antwoorden (8)

more options

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>

more options

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

more options

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.

Bewerkt door David.Hudson1 op

more options

Fx74, win 10.

more options

TyDraniu said

Fx74, win 10.

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

more options

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

more options

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.

more options

TyDraniu said

Fx74, win 10.

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