Pressing <enter> produces <div> </div> instead of <br>

I asked this question two years ago and the chosen solution no longer works for newer versions of Firefox. (135 in my case) . setting editor.use_div_for_default_newlines … (read more)

I asked this question two years ago and the chosen solution no longer works for newer versions of Firefox. (135 in my case) . setting editor.use_div_for_default_newlines in about:config to FALSE does not work.

I am tired of pressing SHIFT <enter> to get < br > . Unnessessary < div >s make code harder to read.

Any new setting I could use to get
for pressing the enter key?

Asked by HeavenlyFox Duela egun bat

Last reply by HeavenlyFox Duela egun bat

Allowing Widows and Orphans

Changing Default Behavior (CSS) When I'm reading on a computer screen, I hatehatehatedespisehatehatehate "widow and orphan" control. This is especially annoying when rea… (read more)

Changing Default Behavior (CSS)

When I'm reading on a computer screen, I hatehatehatedespisehatehatehate "widow and orphan" control. This is especially annoying when reading a long narrative passage that reflows so that a break (often a blank paragraph) falls at the bottom or top of a column/page. There are two relevant CSS properties, each taking a nonzero positive integer as an argument:

    widows: [number of lines]
    orphans: [number of lines]

It appears that Firefox has (like most browsers) established a "default" value of 2 in each of these parameters, which seldom appear in site-specific stylesheets. Do Not Want.

Is there a way to change this default behavior to the equivalent of:

    body {
         widows: 1;
         orphans: 1;}

without either (a) breaking anything or (b) having to redo whatever change every time there's a Firefox update?

Asked by Jaws Duela 3 egun

Last reply by Jaws Duela 3 egun