Subtle changes, bugs and feedback

using microsoft edge and am getting more and more blank posts
for example on the memes thread after the it's an nft meme i get esemans response and fredtc's post but then blanks for h20 fox and spindrift.

see below .................

Thing is, they’ll want to restrict everyone else’s ability to layer up, instead of just freezing to death by their miserable selves.

Reply
21 hours ago • #92579
Avatar for h2oh2o

Reply
20 hours ago • #92580
Avatar for fredtcfredtc in reply to @itsbruce
lol

(it's a nft)

Reply
19 hours ago • #92581
Avatar for FoxFox

Reply
18 hours ago • #92582
Avatar for spindriftspindrift

above h20 spindrift and fox's posts are not visible ? do i need an upgrade somewhere ?

Edge is rendering them fine here.

The comments are just images.

Perhaps the image destination is blocked for you... these images are from Twitter.

images are from Twitter

Which Firefox regards as a privacy threat. I'm guessing Edge does too, so dicki will need to permit some or all trackers

ok so it's only twitter
thanks

Is there a a spoiler tag so I could hide something till it gets clicked on?

Is there a a spoiler tag

Although it's not completely obvious that you have to click on it to reveal the spoiler

Thanks.

Tried other versions of spoiler tags but couldn't find the right one and search didn't come up with anything.

<details>
  <summary>Spoiler warning</summary>
  
 Yes, and you could have just googled markdown spoiler tag

</details>

That's what tester wrote.

But it's not markdown, it's just HTML. In HTML5 there is the details element: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details

And clicking on the summary element within a details element will expand it.

This is HTML and browser functionality and nothing to do with Markdown, BBCode or what LFGSS offers. It's just part of the web.

Agree that it's weird that it's not highlighted / underlined or otherwise obvious. You should petition your browser vendor.

I see in the example on the Mozilla developer page they explicitly added CSS to make it obvious. Standard HTML shouldn't need that. Sane defaults that can be overridden are the usual way (i.e. a H3 element looks like a header by default and you'd use CSS to modify it to look like normal text if that's what you wanted - that's the norm for all standard HTML, so this one looks like an exception and a bug... that the standard isn't obvious and needs styling).

Classifieds has gained a "Miscellany" section.
"Clothing and components" has now had miscellany removed from the title.

Will you move stuff? Can the thread owner move?

I will move some things :)

I am still in meetings.

I'm not going to move the full history as there's no simple way to define what should be moved... i.e. a computer cannot decide, a human will have to.

If you see things that should be moved... post them here and either @hippy or I can move them.

Miscellany

Miscellany or Miscellaneous ?

#summonSchick

I still miss classified prefixes

Wanted:
FS:

I've moved things from the last 7 days.

'Miscellany' means 'miscellaneous items', so is right here. 'Miscellaneous' on its own is short for 'the miscellaneous'/'all that's miscellaneous', i.e. more like an indeterminate amount described using the adjective, which is right for the M&M forum.

and I didn't even have to tag you :)

You're visible from space, so quite easy to put under surveillance. :)

Noticed a bug, seems like column breaks are automatically added to text copied out of a code block, with a hyphen or bullet point inserted mid-string.

Example -- https://www.lfgss.com/comments/16327748/incontext/

Comes out like the following when copied -

W10 Firefox here.

A soft hyphen is added to all text that is more than 40 chars long by design.

Why?

Because if we didn't then the mobile view would never be able to fit width on pages where there was long text. The soft hyphen is a unicode hint that this is a good place to wrap text.

An example:
1234567890123456789012345678901234567890ABCDEFGHIJ

Between the last zero and the letter A a soft hyphen should be inserted.

If you could view that (view source won't show it, you'd need to copy the above into something like Sublime Text and view non-printable chars) then it would look like this:

1234567890123456789012345678901234567890<0xad>ABCDEFGHIJ

Where <0xad> is the soft-hyphen that says to a browser "if you're going to try and wrap but find that you cannot, you can do so here".

https://en.wikipedia.org/wiki/Soft_hyphen

The default styling for <summary> has a disclosure triangle, per https://developer.mozilla.org/en-US/docs/Web/HTML/Element/summary#default_style. The extra CSS in the demo at https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details just adds a border and tweaks the font - if you delete all the CSS in the CSS tab on that page, you'll still see the triangle.

I think what's happening here is that Bootstrap is setting display: block on the <summary>, which has the effect of removing the triangle.

Also, thanks for all the work you put into this site <3.

I understand your point, but given that code blocks are specifically used for situations where every character matters, introducing new ones seems like a bad behaviour.

Context: https://www.lfgss.com/comments/16327731/

Fwiw the code block text reflows fine on my phone at a different point in the string. Your example string of numbers weirdly doesn't, it's one character too wide for the screen.

Fair enough, and I accept PRs.

The code in question is here: https://github.com/microcosm-cc/microcosm/blob/master/models/markdown.go#L193

It's a simple regex text replace on textual data within HTML. It is a fast, forward-only parser that is provided by the core Go team and this does not have context of the parent node merely the current node and type.

To fully achieve what you need we'd probably need a full DOM tree here to ensure we don't perform the replace text where an ancestor is a code or preformatted element.

Once done, you'd need to also ensure the CSS works cross-browser to ensure that the layout isn't broken for all comments... only for the comment that exceeds the standard width (as it won't now wrap). This is harder, as the version of Bootstrap is 6 years old, and the version of Django is 6 years old, and neither build any more. So you'd need to start by resolving all dependencies needed by Django and node so that you could build both again... then you could make the adjustments to Bootstrap and push them into the Django build which I could merge, build and then ship.

PRs happily accepted.

Or it's good enough as what you describe is an edge-case we can live with.

Well, I won't be doing that, but thank you for the detailed explanation of the obstacles involved. Hope you have a good evening.

No worries.

And yeah, that's why I haven't fixed it either.

Similar to a few other small quirks I know about which 6 years ago made sense and were the right amount of effort. But now the browsers are doing things better and there are better Go libraries for me to do things.

In time I'll get around to these... but I'm not really putting in the evening and weekend work I should to make that soon.

How much work would be involved in a dark mode theme? Similar level in terms of setting up a build environment or whatever? Used to mess around a lot with userstyles and the Stylish plugin but that was just a layer on top of everything.