Double spacing between paragraphs in posts? New?

[ERD50]

Quote:

Originally Posted by target2019 Ok, discovered another thing you can do with Firefox, if you want to keep the WYSIWYG editor (meaning don't drop to the standard option in forum). - go to about:config - search for editor.use_div_for_default_newlines - double-click the line to change it to false Everything above is typed on a line, with enter key pressed at the end. Say it: No Extra Line Breaks.

That did it! Thanks!

Of course now, my 'warranty' on FireFox is void! Hah, I though that was pretty funny of them.

-ERD50

[JoeWras]

Quote:

Originally Posted by ERD50 One for the road (no longer politically correct, is it?).

Maybe 5 for the road?

I need to try the computer with 60.x later...

[Totoro]

Thanks for the discussion here - had the same issue with Firefox (60.0.1 as of now).

[Midpack]

Quote:

Originally Posted by easysurfer I've had double spacing after quoting articles and had to edit out the spaces. Regular posts seem fine.

I’ve noticed same for more than a year, but only when quoting. It doesn’t happen often for me, and when it does I can edit and remove the double spacing. I use Firefox and Safari, so it could be Firefox related in my case (hadn’t noticed).

[target2019]

In Firefox, you can select the posted article (click and drag through), and right click, then View Selected Source. You'll have a better idea of how things work behind any given post/page.
Since this extra <br> is handled by browser and forum editor, at any given time it can behave in ways you didn't expect. The extra line break is probably annoying to some, but not others.
There also can be unseen codes picked up when someone responds. Again, View Selected Source (after posting), and you can probably figure out what caused it. Maybe someone pasted from another source?

[easysurfer]

Quote:

Originally Posted by Midpack I’ve noticed same for more than a year, but only when quoting. It doesn’t happen often for me, and when it does I can edit and remove the double spacing. I use Firefox and Safari, so it could be Firefox related in my case (hadn’t noticed).

I got double space-itis now both when quoting and not . Yes, I am on Firefox.

[Midpack]

Quote:

Originally Posted by easysurfer I got double space-itis now both when quoting and not . Yes, I am on Firefox.

Whoops, just noticed I've been afflicted too, not just some quotes like before. The guidance in post #36 worked for me, thanks. That won't change how FF behaves with other apps/websites? In which case I'll just switch back to "true."
This is a test.
And another.
And another.

[easysurfer]

Quote:

Originally Posted by Midpack Whoops, just noticed I've been afflicted too, not just some quotes like before. The guidance in post #36 worked for me, thanks. That won't change how FF behaves with other apps/websites? In which case I'll just switch back to "true." This is a test. And another. And another.

Will this work?
Testing 1
Testing 2
Testing 3
Fingers crossed for good measure .

Looks good!! Thanks, as the double space-itis was driving me bonkers.

[WestUniversity]

Quote:

Originally Posted by JoeWras Help! Help us please! We are being double spaced into oblivion! :

[emoji23]

[Chuckanut]

OK, let's see if the Firefox change works

Does it?

Yes it does.
Yea!

[Sunset]

I noticed this suddenly as well.
Just made the change.
Testing it here

[JoeWras]

Quote:

Originally Posted by target2019 Ok, discovered another thing you can do with Firefox, if you want to keep the WYSIWYG editor (meaning don't drop to the standard option in forum). - go to about:config - search for editor.use_div_for_default_newlines - double-click the line to change it to false Everything above is typed on a line, with enter key pressed at the end. Say it: No Extra Line Breaks.

OK, trying again on the "broken computer" with 60.x.
How is this?
Sorry for the noise.
Does it work?

Should be one blank line above.

Edit: ahhh, that did it! Thank you target2019. If I could, I'd drop you a large bonus so you could join class of 2018.

[target2019]

Waiting for the day Firefox decides to modify the browser behavior, and we get an update that fixes this problem. How will our change to config manifest in future browser? Time will tell.
It is likely I will go part time early 2019. Just sayin'

[omni550]

Quote:

Originally Posted by target2019 Ok, discovered another thing you can do with Firefox, if you want to keep the WYSIWYG editor (meaning don't drop to the standard option in forum). - go to about:config - search for editor.use_div_for_default_newlines - double-click the line to change it to false Everything above is typed on a line, with enter key pressed at the end. Say it: No Extra Line Breaks.

Thanks, target2019.

This 'fix' works like a charm!

omni

[ERD50]

Quote:

Originally Posted by target2019 Waiting for the day Firefox decides to modify the browser behavior, and we get an update that fixes this problem. How will our change to config manifest in future browser? Time will tell. It is likely I will go part time early 2019. Just sayin'

Yes, and why isn't it in some sort of user-friendly preferences setting or something? This is easy once a guru like you show us, but even though I ain't afraid of no tech, I would have no idea to look for "editor.use_div_for_default_newlines". What the heck is that?

How is it you found the solution, my searches came up empty?

-ERD50

[Lsbcal]

Firstly, in Firefox I can see the extra newline when I use "Preview Post" before doing a "Submit Reply" in the advanced editor. I don't have to actually submit the post to see this. Using this method I do not see an additional newline when preparing a post on the Bogleheads forum. So maybe this forum's software is partly to blame?


Second, when I looked into that about:config setting I saw this:


I'm not sure I want to go this route since it's a workaround to a fairly minor problem. Will I remember this change if it causes other issues unrelated to this forum. What about security?

[ERD50]

I took the 'warranty' warning as joke. This is free-ware, there is no warranty.

I think you do have a valid point about remembering this change if it did affect something else. Not likely, but could happen.

I do try to log changes like this, it helps when/if you reinstall something.

-ERD50

Quote:

Originally Posted by Lsbcal Firstly, in Firefox I can see the extra newline when I use "Preview Post" before doing a "Submit Reply" in the advanced editor. I don't have to actually submit the post to see this. Using this method I do not see an additional newline when preparing a post on the Bogleheads forum. So maybe this forum's software is partly to blame? Second, when I looked into that about:config setting I saw this: I'm not sure I want to go this route since it's a workaround to a fairly minor problem. Will I remember this change if it causes other issues unrelated to this forum. What about security?

[JoeWras]

Right. Warranty? Really?

OK, if it doesn't work, I delete the old version and reinstall.

They just don't want people badgering them about this. It is fine.

[Lsbcal]

I didn't really think about the warranty wording. Probably is a bit of a joke but it did serve as a good warning.

[badatmath]

Oh you know I thought I was crazy!!! Also on FF.