Links stopped being clickable

[kushcat]

Relative positioning is used here to move the topic icon above the background of the read/unread icon (wich is positioned in absolute).
This is not immediately obvious because the background of the read state uses transparency, which is not the case for the unread state.

To fix this, the inaccessible elements also need to be positioned in relative:

Code: Select all

dd.lastpost > span > :not(dfn) {
	position: relative;
}

Too complicated. Just use this:

Code: Select all

.lastpost {
	position: relative;
}

Works the same. Less stuff. Less stuff is good.

Although, TBH, the best fix is to ditch the default Prosilver CSS and just flex the lot. That's what I did years ago, when I first took a look at the default code, thought "No effing way", and promptly threw it all in the bin. Never looked back. It makes responsive and RTL a hell of a lot easier too.

his worked, yours made actual forums not clickable xD

[Gumboots]

Now that is odd. I didn't think to check that, because it's not something I would ever have expected.

It doesn't actually make them not clickable, but what it does do is make the clickable area much smaller in height. If you hit the very bottom of the .forumtitle links it works, but only on the very bottom. Why? At the moment I have no idea. There's no obvious reason for it.

However, this works:

Code: Select all

.lastpost a {
  position: relative;
}

That makes the links in .lastpost clickable without screwing anything else, and it's still less code.

And that default CSS is still utterly bonkers.

[kushcat]

yes but i wasnt able to click these links after using your code

Screenshot 2025-04-12 220020.png

[Gumboots]

Like I said, it made the clickable area of the link much smaller in height, so that only the very bottom was clickable.

[kushcat]

yup that works thanks where do you suggest i look for more custom skins?

[Gumboots]

Honestly? Dunno. I ever look for them anywhere else.

[kushcat]

what do you mean

And that default CSS is still utterly bonkers

[kushcat]

what do you mean

And that default CSS is still utterly bonkers

[Gumboots]

I mean these days there are much simpler and more versatile ways of doing it. It's very old code, from a period when not as many things were possible, and whoever coded it was trying to be extremely clever for that period, so they made it extremely complicated to deal with. You can get the same result with less code and far less hassle.

[LukeWCS]

because in the default Prosilver CSS someone had the idea that they wanted the dt to extend the full width of the parent li, so they gave the dt a massive negative right margin.

That was the missing piece of the puzzle, thanks! After reading that, I experimented with the mentioned value. This logically disrupted the layout, but the links were usable again as such.

And good catch.

Well, 10% inspiration, 90% perspiration. ^^