HTML tag problem with story submission

[HelenL]

I've never seen that. Just now I went to https://www.literotica.com/s/honeys-rizz-quest?page=2, clicked on page 1, and the separators were missing; opened the source (Ctrl+U), searched for "* ", and they were there as expected.

A (client-side JS) script cannot modify the initial HTTP response, only the rendered DOM (HTML elements) of the page as displayed in the browser.

I managed to see the bug again in the page I've been working with (it's way more random than I thought) and tried what I'd done before, ^U copy etc., and the separators were present this time. But now I think that's a red herring because ^U is causing a page reload.

If instead I save the page locally and look at the HTML the separators are missing again in the code.

I'm convinced that this is a server-side problem, but I think our testing is heisenberging our results...

 

[MrPixel]

I think our testing is heisenberging our results...

Uh huh. Red herrings abound.

 

[TheLobster]

If instead I save the page locally and look at the HTML the separators are missing again in the code.

This looks like a difference between browser behavior. If I do the same in Chrome -- save the page where separators are missing -- I do get the same result as if I right-clicked, picked View Source and copy-pasted the HTML into a file. Your browser might be dumping the DOM instead.

But now I think that's a red herring because ^U is causing a page reload.

You're right that viewing the source makes a new request to fetch the page from scratch, but I've never seen such newly fetched (i.e., server-side rendered) page contain story content w/o the separators.

By the way, it is very easy to tell whether you're looking at server-side or client-side rendered story content. The server-side render will have the data-hk attributes everywhere, on pretty much every single <p> element; whereas a client-side render will have very few.

 

[IWroteThis]

I've never seen that. Just now I went to https://www.literotica.com/s/honeys-rizz-quest?page=2, clicked on page 1, and the separators were missing; opened the source (Ctrl+U), searched for "* ", and they were there as expected.

A (client-side JS) script cannot modify the initial HTTP response, only the rendered DOM (HTML elements) of the page as displayed in the browser.

View source pulls a new copy of the HTML, so it works like refreshing the page. To view the actual code of the buggy page, you have to use the debugging tools to see it live.

I tested this by comparing the code from View Source to the code shown by the debugger on both original/buggy and refreshed versions of the page. View Source matched the refreshed version, not the original buggy one.