Centered scene breaks fixed.

[RejectReality]

I'm at least getting consistent results of the inconsistent results. LOL

On desktop, Firefox, Opera, and Edge have all been closed. I open them up, copy the link above to page 1, click either the number or the next button, and I get the scene break on page 2, plus all the scene breaks beyond.

On mobile and Ipad, with the browsers having been closed, doing the same thing results in no scene break on page 2, but scene breaks on pages 3+

 

[old_prof]

I'm at least getting consistent results of the inconsistent results. LOL

On desktop, Firefox, Opera, and Edge have all been closed. I open them up, copy the link above to page 1, click either the number or the next button, and I get the scene break on page 2, plus all the scene breaks beyond.

On mobile and Ipad, with the browsers having been closed, doing the same thing results in no scene break on page 2, but scene breaks on pages 3+

The section break is still missing for me on firefox (mac)

 

[BeechLeaf]

Recently I've been re-reading the back catalogue of Bastard Operator From Hell, and this is making me a bit paranoid: like someone's doing this deliberately and selectively to drive users mad.

But on the other hand, the actual error seems to be one of those nightmare things: a bug you could not imagine any way of causing if you wanted to do it deliberately.

 

[RejectReality]

Closed everything ( including chrome on desktop this time ) and still getting the same results. For me, PC desktop = working, Samsung mobile and Ipad = fail on the one scene break on page 2. Every other scene break is there regardless of platform or browser.

 

[FrancesScott]

The deeply annoying bug persists on mobile devices. Have tried an iPhone and iPad and with multiple browsers.

 

[TheLobster]

Perhaps at this point we can entertain the idea that it's not a bug, but a feature. Designed to torment certain users.
Incidentally, it's still intermittent for me, using a chromium-based desktop browser (Brave) in private mode.

Manu is simply edging us, as we wait for a proper fix, and cucking those who aren't seeing the fix yet.

He's just kinky like that.

 

[RejectReality]

Anybody else got one that they can't see on Desktop that they can link for me to check? ( Preferably with a few words of text immediately preceding or immediately following unless it's as simple as Old Prof's 3 paragraphs down example )

 

[Britva415]

I'm beginning to think we might be watching the first instance of staged feature rollout and we're in different buckets,

The comments thing could be evidence of this, too. A feature rather than a bug fix, that one, but people do seem to be in different buckets.

 

[BobbyBrandt]

All is well for me using Firefox on Windows 11.

 

[designatedvictim]

My two bits:

Windows 11
Chrome - Version 146.0.7680.178 (Official Build) (64-bit)
Edge - Version 146.0.3856.97 (Official build) (64-bit)

Both browsers had been closed, so no instances were running. Caches were cleared.

Both still do the missing centered scene breaks that appear when the page is refreshed.

IIRC, the last time I peeked into this about two months ago, it seemed that the page data gets processed through some ********** locally for display. The script gets the page text passed in as a parameter and that doesn't show the scene break data, either.

That suggests to me that it isn't being served to the local browser with the centered break text, which strikes me as being weird.

They should prepare the data once when saving it to the database, then they shouldn't need to do anything when serving it, later.

I could be wrong.

 

[RejectReality]

I'm still in the same boat as previously. Everything is fine in every browser on desktop. No scene break on page 2 of Old Prof's story on mobile, but the page 3+ scene breaks are all there. Tested with incognito mode on mobile to bypass the cache completely, and no love.

Something has obviously been tweaked, because I was getting no centered scene breaks previously, but it's also not completely fixed yet.

 

[designatedvictim]

I vaguely recall discussion of this not too long ago where it was suggested that it was potentially related to a late-loading asynchronous script download.

I do see that when the centered text is missing, the DOM shows an empty paragraph tag (highlighted) with the data hook (data-hk) attribute set just on the empty paragraph.



But when the page is manually reloaded, virtually all of the paragraph tags have the data-hk attribute set (with what looks like a paragraph counter) and the center tag appears (highlighted) in the DOM (and, oddly, followed with another empty paragraph with no data-hk attribute).