My HTML guide has been updated

Last edited:
Given the twattery that the current rendering system is causing for stories, I'd be hesitant to rely too much on formatting, especially anything centre-aligned. Chances are it won't display ≈ 50% of the time
 
Currently if a reader switches from one page to another in a story using either the page forward/back links or the direct page number links, then most (but not all) center aligned text completely vanishes. It's still present in the page source, but the Literotica display collapses the entire lines as well as any white space before or after.

My strong suggestion is to tell people that center aligned text is simply not supported on Literotica, because right now it isn't. Not really. It's been like this for over a month, and there's no evidence that Manu is even working on the problem, so it's probably going to remain broken for months and maybe permanently.
 
Currently if a reader switches from one page to another in a story using either the page forward/back links or the direct page number links, then most (but not all) center aligned text completely vanishes. It's still present in the page source, but the Literotica display collapses the entire lines as well as any white space before or after.

My strong suggestion is to tell people that center aligned text is simply not supported on Literotica, because right now it isn't. Not really. It's been like this for over a month, and there's no evidence that Manu is even working on the problem, so it's probably going to remain broken for months and maybe permanently.
It did work for me for a while again, but then it's broken again. :mad:
 
Yeah. A firefox update looked like it might have changed things, but it's still fucked.
I had a reproducible test in a story I didn't put an edit in for, somewhat because it is a good test case for me to watch and because no one reads that story anyways.

It was fixed and stayed fixed for a few days, so I stopped checking. Then someone on another thread complained abut a similar problem and I went back and checked and tts; back to broken again.

I use safari as my primary browser (the only one I checked on, so it wasn't a firefox change that helped or broke it again.

My first guess is that Manu fixed it in place, but not in the version that he was working on something else in. When he posted that fix, he lost this fix. Let's hear it for no source code control.
 
I had a reproducible test in a story I didn't put an edit in for, somewhat because it is a good test case for me to watch and because no one reads that story anyways.

It was fixed and stayed fixed for a few days, so I stopped checking. Then someone on another thread complained abut a similar problem and I went back and checked and tts; back to broken again.

I use safari as my primary browser (the only one I checked on, so it wasn't a firefox change that helped or broke it again.

My first guess is that Manu fixed it in place, but not in the version that he was working on something else in. When he posted that fix, he lost this fix. Let's hear it for no source code control.
Source control is for losers; everyone knows real programmers write their code using magnets, on the server, live in production.
 
Source control is for losers; everyone knows real programmers write their code using magnets, on the server, live in production.
I did some consulting for a major bank 40-some years ago. Of course it was a cobol system, but for the last few years they had given up on making changes in the cobol and were patching the built system using BAL assembler. We found a billion dollar mistake in their accounts. The person who worked for me and actually found the mistake, was hoping to get a finder's fee as a percentage, but they didn't oblige him.
 
Back
Top