Bug report: My Tildes groups page isn't color coding my subscriptions properly
It's only showing ~test as orange even though I've unsubscribed to a couple of others
It's only showing ~test as orange even though I've unsubscribed to a couple of others
Any time I click a link to go to a comment I am linked to the top of the page.
I wanted to label a comment as Exemplary today and when I clicked "Label" the option wasn't present. I've given Exemplary labels before, but it's been a while. I do know there's a cooldown, but I don't think I've given any out lately, so I wouldn't think that would apply.
I'm on Firefox, but I checked on both Chrome and Edge and I don't have the option there either.
I do 99% of my browsing on Firefox mobile on iOS. Lately (possibly since I update to iOS 16.02), I’ve been logged out when I fully close out the app (swiping up).
On https://tildes.net/groups it looks like at least on Firefox 88 the normal link color:
a.link-user:visited, a.link-group:visited
is overriding the unsubscribed color:
.group-list-item-not-subscribed a.link-group
this has happened twice.
Edit: Wow just happened again, when commenting or making a post once it overflows the text area the browser forgets all the information that you have written above. I wrote that this has happened twice, but now it's three times as it happened when I was writing this post. Voting has also sporadically been broken.
Every once in awhile the voting mechanism has a truly long delay or requires a complete refresh of the page.
Browsers: Firefox for Android, Firefox for Ubuntu.
Pretty simple bug, documented as per title. The /groups page incorrectly indicates that I am subscribed to ~anime (I shouldn't be), whilst the ~anime group itself, and the subscriptions list on the homepage (along with the topics I see), correctly show me as unsubscribed from ~anime.
I could try toggling this? Which might fix the bug, but would also potentially erase the state of my subscriptions in the database and prevent debugging.
When I click on the "x comments" in the upper right to see responses to my previous posts, it lists out any unread comments to my posts. If I click on the "Parent" link to see my original comment and the reply, I can collapse the reply, but not the parent. This seems like a bug. I can collapse the grandparent, and it all goes away, but I'd expect to be able to collapse the parent as well.
The first two image links in the spoilerbox of my Timasomo update don't work (as in aren't clickable or turn the text into a link), but others do.
Bug?
To simplify the title:
(Formatted text, no space. (Behind the arrows.) While it's expected for quote blocks to not separate with one 'line' between them, it's definitely not expected for the block to be the same size, even w/o text.)
(Formatted text, with a space. Added this one in to contrast with Preformatted w/ space and because it separates the code blocks.)
>
>
>
(Preformatted/Codeblock text, no space. The "quote trigger" arrow in the middle is the bug, since if you look at the "view markdown" option of this post you'll realize that arrow shouldn't be there.)
>
>
(Preformatted/Codeblock text, with a space. This is how I personally fix the bug, if it is that. You can also fix it by typing space into the phantom arrow.)
Now with text inside the quote blocks, for comparison. (And because quoteblocks have to quote something.):
qwerty
asdf
(Formatted text, no space. Here the block expands normally for the text.)
qwerty
asdf
(Formatted text, with a space.)
>qwerty
>
>asdf
(Preformatted/Codeblock text, no space. The arrow in the middle I never typed in is still there.)
>qwerty
>asdf
(Preformatted/Codeblock text, with a space.)
The CSS selectors that determine whether or not to apply the display: none rule to comment text sections use the pseudo-class rule :not(:target). While this is great for keeping a comment in a non-collapsed state, it's a bit too effective as it prevents user-initiated collapsing of the comment. This can be problematic when you visit a direct link to a comment with an extensive reply tree beneath it and want to collapse it so that you can view the surrounding reply trees. As it stands, you can't do this without needing to either a) collapse the parent (prevents viewing sibling comments), b) collapse the children (requires collapsing potentially multiple child comments), or c) remove the fragment portion of the URL (requires reloading the page and possibly losing your place on the page).
Reproducing should be as simple as clicking Link in a comment's header, then trying to collapse the comment after being redirected.
The scraper usually works pretty well but as seen here it can sometimes fail pretty spectacularly, in which case it would be beneficial if we could edit the data it collects.
@b0rk: investigate bugs together
Usually bugs, glitches, and exploits degrade the experience of a game, but occasionally they can actually work to a game's benefit. In some cases, they can become significant enough to become part of a game's identity. In others, they make a broken game worth playing in the first place. Even without such legendary status, a given wrinkle in a game might simply make it more enjoyable or entertaining, or perhaps open up unexpected modes or paths of play.
What are some examples of these, and how did they improve their associated games?
I just noticed today that in ~music, the "topic-info-source" metadata isn't visible in listings; it shows the author name instead. Clicking through to the post it's clear that it's been scraped, it just doesn't get a site name or favicon.
eg: Youtube link on ~movies versus Youtube link on ~music
Is this intentional? It sorta makes it look like everything on ~music is a text post.
I might've missed something, but why did the Financials block disappear from the main page? And the numbers on the financials page are zero.
Also, while we're at it, there should probably be a “Financials” link in the footer.
I've been noticing a couple of weird formatting issues with tags on topics. For some posts, the first tag is shown before the metadata, then the rest of the tags are on a new line below. This isn't always the case, and so far I can't find any rhyme or reason for whether it does or not. It's not like some CSS float issue or anything, it's actually creating two <ul>'s. — example
The second issue I've noticed is sometimes the dangling part of a letter like lowercase "g" will be cut off by the footer. It seems like this is caused by .label {line-height: 1.2;}, but it's also inconsistent, and I haven't figured out why. In this example the "g" in "climate change" is not affected.
Maybe it's just me, I dunno. Firefox 70 on linux. I'd create a gitlab issue, except I am very lazy.