replies adding extra line breaks when posted

[Jon]

Unless someone can diagnose the cause of the issue, what can I do about it? I do not have any control over anyone else's computer, how it is configured etc.

 

[Deleted member 147267]

Interesting. I put it down to the UI here that makes the html for a post. With same laptop and same FF version, it happens to me here all the time, but not at AccessForums.net, which is why I figured it was a forum UI thing. So I will return once, then type abc, then return 2x and type, then shift+return 2x:
abc


def

ghi
Whenever I want 2 blank lines, I just shift+return+return here.
EDIT - I said 2 but I meant 1.

 

[Jon]

@Micron @vba_php, try toggling this option:

editor.use_div_for_default_newlines

 

[vba_php]

@Micron @vba_php, try toggling this option:

editor.use_div_for_default_newlines

Jon,

I'm kind of a moron when it comes to configuration...where in the world do I put that spec line?

 

[Deleted member 147267]

typing + return
equals this + return+return


equals this.

This is shift+return+return. No different, but then again I didn't restart FF because I have to go out for a while. Will restart and try again later, just out of curiosity.

 

[Jon]

Open a new tab
In the URL type about:config
Agree that you will be careful
Copy and paste
editor.use_div_for_default_newlines
Into search
when entry appears is should indicate default boolean true
Double click to toggle to false
Close about:config

 

[vba_php]

Jon,

I can get to the about:config in FF, but chrome threw an error....

<edit>
I got there I think with "chrome://about/"

 

[vba_php]

Copy and paste
editor.use_div_for_default_newlines
Into search

that is not an option under all the hyperlinks on the about page Jon. I tried to go to "chrome//about:config" as well but i got redirected back to "chrome//about". am I just stupid?

this is after 2 return presses.
this is after 1 press.

this quote is after 2 return presses

the /quote tag was typed after 1 return press.

Looks like it works for FF Jon!

 

[Gasman]

If you google

editor.use_div_for_default_newlines

that produces a wealth of posts on this issue.?

 

[The_Doc_Man]

Adam, I have to thank you.

Before you came along, folks thought I was the only one to brutally beat dead horses. Now, at least they have a comparison.

 

[vba_php]

gasman,

i'm going to use FF. I really don't have time to research a marginal issue like this. But apparently Jon fixed it for me in FF where I was about to bring up the page he showed me, as my test indicates.

Adam, I have to thank you.

Before you came along, folks thought I was the only one to brutally beat dead horses. Now, at least they have a comparison.

what does that mean mr. grandpa!? this is not a dead horse! why not fix problems that users are having? If Jon cares, he would at least TRY. and he did that. now it seems it's fixed, at least for me!

 

[Jon]

Problem solved. Happiness resumes.

 

[vba_php]

Jon,

as an added bonus to this whole thing, it looks like other people are having the same issue:

https://www.access-programmers.co.uk/forums/showpost.php?p=1656734&postcount=1

I hope they stumble across this solution!

 

[Gasman]

Adam, I have to thank you.

Before you came along, folks thought I was the only one to brutally beat dead horses. Now, at least they have a comparison.

Doc,

We say 'flog a dead horse' over here.