WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2024 Poal.co

1.2K

When viewing this post: https://poal.co/s/Poaldev/330009

Sidebar is gone until I scroll down, then it appears as shown.

Don't see it on any other posts yet though.

Happens on both of my legacy Firefox based browsers (Icedragon while logged in, Waterfox while not logged in) but not Brave (tested both logged in and not logged in).

edit: https://files.catbox.moe/b9f46p.mp4

When viewing this post: https://poal.co/s/Poaldev/330009 Sidebar is gone until I scroll down, then it appears as shown. Don't see it on any other posts yet though. Happens on both of my legacy Firefox based browsers (Icedragon while logged in, Waterfox while not logged in) but not Brave (tested both logged in and not logged in). edit: https://files.catbox.moe/b9f46p.mp4

(post is archived)

[–] [Sticky] 1 pt

Should be fixed. Stupid Firefox based browsers don't support word-wrap and mess up the content of a div with a long ass sentence.

[–] 0 pt (edited )

It is now properly breaking that "REEEEEE" comment for me in Waterfox that was not breaking and wrapping correctly as @blumen4alles noted: https://files.catbox.moe/csch2o.jpg

However, it seems to be causing words within comments to break mid-word for me instead of moving the word to the next line or even hyphenating it to the next line; such as in this image with "especially' at the end of the line: https://files.catbox.moe/fmfb0y.jpg

On the ".comment p" element for the body of comments, changing "word-break" to "normal" for me causes the word to be moved to the next line, but it doesn't break that long "REEEEEE" from that thread and that issue becomes present again.

However, also adding "white-space" to be "pre-wrap" and overflow-wrap to be "anywhere" for the ".comment p" element allows the "REEEEE" to break mid-word to the next line as well.

I haven't noticed these attribute changes causing any issues for me anywhere else on the site and they properly move words to the next line and also long strings like that "REEE" to be broken to the next line.

.comment p { overflow-wrap: anywhere; word-break: normal; white-space: pre-wrap; }

With these attributes for that element the "especially" is moved to the next line and the "REEE" is wrapped to the next line.

As a nice bonus, I also found it fixes the issue I was having of needing to double return or add two spaces at the ends of sentences to keep sentences on separate lines instead of all running as one line. That got to be pretty irritating and time consuming to add after ever sentence in posts when formatting them. (Shame the fix is only a visual fix on my end to have single returns actually starting a new line and I still need to keep manually adding the double spaces or double returns or else everyone else will see one long sentence without returns while it would look proper for me.)

[–] 1 pt

I was also working on the code, so I'm not sure if your tried live or in a cached version.

[–] 1 pt

Everything is all looking and working perfectly for me now in Waterfox with what you have done. Single returns are also starting new lines as well! I don't think I'll need to do double returns or spaces at the ends of sentences anymore to start new lines.

Thank you very, very much for your efforts on all of these, AOU.

[–] 1 pt

Damn, you're always so busy and on top of these things.

I'll run through and clean cache, disable all adjustments and see if I'm still seeing the issue. Thank you.

[–] 0 pt

Nothing to do with the new Hide post feature.

Happens when you zoom or use custom fonts size.

Clear your cache to make sure it's not some obsolete css settings.

[–] [deleted] 1 pt (edited )

For what it's worth, I see the same thing, but only in that post.

I figured you were screwing with everyone.

It appears on the left side and only after you scroll a half page down, then randomly appears/disappears when you change scroll direction.

Other posts in poaldev are fine, seems to just be with the sticky.

[–] 0 pt

Nothing to do with the new Hide post feature.

I didn't think so, but I noticed it on that one first.

Happens when you zoom or use custom fonts size.

Zoom is default 100%, no custom font size.

Clear your cache to make sure it's not some obsolete css settings.

Happened on two different legacy Firefox browsers. Restarted Waterfox, same thing happens in both normal and in-private.

Cleared all data in Waterfox, restarted, still persists.