Another new bug

I've had no formatting issues since I started using RTF formatting for submitted stories. I'm not fluent in HTML and don't want to be, don't have time to format my work, and as long as the system keeps doing it right, I won't be changing my ways. Then again, I'm not posting much these days.
 
Looks resolved on the first story I noticed it on. Things happen, I get it, but
@onehitwanda @iwatchus the way I stopped my italics problem from happening (no instances of it happening in 3 years) is by no longer doing my own html. I just submit the .docx and Laurel handles the conversion.
Unfortunately my pipeline is based on using a non-wysiwyg editor, and openoffice, libreoffice etc all irritate me far too much to adopt them. I'll just add one more asterisk to my list of things to be aware of for if I get around to publishing something else.
 
Hey, @ElectricBlue, AH-ers are attacking Lit! It's not me this time!

On the other hand, I don't know who I am anymore. I feel like Bart Simpson in that episode when the guru convinces everyone to do whatever they want... 🫤

Anyway, hurry up! That cheeky bugger, Simon, is trying to outfanboy you.
Guttenberg, your services are required in the lobby.

I learned not to use html years ago, after I thought I was being clever using lots of html, but fucked it up completely when a whole second page flipped to italics. My fault, but root cause: using html rather than a simpler format approach that serves the exact same purpose.

The issue being reported here seems unique to those folk who try to get too clever with their formatting, to sex up their bells and whistles. Sympathy value low (but not zero), because if it looked right the first time, there's a reasonable expectation for it to continue to work right, forever. However, software upgrades never do that, in my experience, something always goes pear shaped.

But to pull all your stories because the site, on one night, fucked something up and you lost your special shade of pale blue seems a bit extreme to me.

This too shall pass, and all will be good in the morning.

Carry on (but stop using elaborate html).
 
I don't think it's quite fair to describe losing your section breaks as a 'special shade of pale blue.' Nor is it unreasonable to expect a text-display platform to display text correctly.
 
Carry on (but stop using elaborate html).
You see that hill over there? The one with the stone circle and the neolithic hill fort ruins?

At the centre of that fort, aligned with the sunrise at Summer Solstice and moonrise at the Winter Solstice, is a stone. It's not much to look at - somewhat flat on top, mildly oblong, with odd indentations here and there.

If you were to wind time back seven thousand years, you'd find an altar stone where I used to pray to the Great Old Ones. The recesses held tallow candles, and the groove in the middle was to catch the blood of the first critics as we cut their hearts out in the dark of the moon.

It may not look like much of a hill in these modern times, but it is a site of old power, older than the bones of the Earth.

And I will die on it. So there!

Edit: PS: :p
 
They borked the CSS used by story pages. The styling for <blockquote> is completely gone, for example, so the indent you're seeing is just the default styling your browser does.
I had recently submitted an edit to a story (Her Turn) to use blockquote to distinguish a letter from the rest of the story and another (Contract Clash) where I used it to distinguish the original text of the story I wrote an alternate ending to, so you're comment made me panic. However, both of them appear fine when I just checked them. In fact, the story with the letter looks better than it did immediately after the edit was done, as the spacing between paragraphs was doubled originally.

I wonder if the How To article by @FrancesScott has increased the usage of blockquote to the point that they tried to fix the CSS to render it better, causing problems for those who tried to work around the extra spacing?
 
Some, but not all, section breaks, as given by center tags, are being clobbered. Looking at the rendered HTML, the site replaced the open < of both the open and close center tags with \x3C
I checked the story in both Firefox and Chrome, but they section breaks display and are properly centered in both. I used View Source to verify the \x3C replacement, but both browsers didn't seem phased by it.

For the record, I'm using a Windows 10 PC.

EDIT: I just pulled the entire story text section from View Source and confirmed that every "<" has been replaced with "\x3C" so it should be safe to rule that out as the issue.
 
Last edited:
It does seem to be a style sheets issue, my mothman story that uses blockquote extensively is definitely rendering differently than it used to, though honestly I'm in favor of using blockquote to only indent and not italicize!

It's just wild that it seems like Lit doesn't have a testing server, and Manu appears to be tweaking things live as we speak on prod 😱
 
I had recently submitted an edit to a story (Her Turn) to use blockquote to distinguish a letter from the rest of the story and another (Contract Clash) where I used it to distinguish the original text of the story I wrote an alternate ending to, so you're comment made me panic. However, both of them appear fine when I just checked them. In fact, the story with the letter looks better than it did immediately after the edit was done, as the spacing between paragraphs was doubled originally.
The removal of custom blockquote styling may very well be intended. By default, most browsers give it a little indent on the right (left in LTR scripts) and some small margin above and below. The italicization was Lit's custom CSS, and I agree with @PennyThompson that it's better now when it's gone.

If you used the tag to visually emphasize certain paragraphs, you should still be mostly fine. In fact, it should be less finicky to use now, since the previous styling added extra margin on top which you had to account for; now you don't have to.
 
It does seem to be a style sheets issue, my mothman story that uses blockquote extensively is definitely rendering differently than it used to, though honestly I'm in favor of using blockquote to only indent and not italicize!

It's just wild that it seems like Lit doesn't have a testing server, and Manu appears to be tweaking things live as we speak on prod 😱
FWIW, Laurel told me a few years ago that they work live. No sandbox for Manu, so some problems are inevitable.
 
Back
Top