I'm trying to write a package for the Zen Maru Gothic font, which is available on Google's font repository on github. (https://github.com/google/fonts) It's a huge repo with thousands of fonts, so I'm trying to use sparseCheckout to grab only the part I need:

src = pkgs.fetchgit {
   url = "https://github.com/google/fonts.git";
   rev = "v0.4.9";
   sha256 = #snip long hash;
   sparseCheckout = [ "ofl/zenmarugothic" ];
};

I was originally using fetchFromGitHub pointed at the same repo. In both cases, what's actually being fetched into the store seems to be the root directory of the Google Fonts Axis Registry repository (https://github.com/googlefonts/axisregistry) which has a different url, name, and owner.

I feel like I'm going crazy.

Example of behavior: https://discuss.online/post/35408836

In a browser, the post body contains two spoiler tags, the first is some text, and the second is an additional image. In the app, the image gets combined into the gallery, but the text is nowhere to be found.

Also the "Combine markdown images to gallery" setting doesn't appear to do anything; even with it turned off, the image gets combined into a gallery and the text is still missing.

Bug Report

Describe the issue: The post in question:

https://discuss.tchncs.de/post/53330380

That's the url as connect copied it from my feed view in Connect, but I imagine my experience actually involved the federated copy on Beehaw. [Edit: the tchncs.de link crashes also.] A couple of attempts looked like the app was trying to throw up an error message of some sort, but it crashed back to the launcher so quickly I couldn't read it.

Device Information

• App Version: 1.0.372 (372)
• Platform: android
• OS Version: BP4A.260105.004.E1
• Notice: Using legacy Shared Preferences

Modified Settings

The following settings have been changed from defaults:

• isCommentActionsReversed: true (default: false)
• alwaysShowInstance: true (default: false)
• alwaysTrustDomains: true (default: false)
• commentTextStyle: bodyMedium (default: bodyLarge)
• enableCommentNavigator: true (default: false)
• shouldHighlightNewComments: false (default: true)
• isImageVerticalSwipeToClose: false (default: true)
• nsfwView: show (default: blur)
• applyNsfwInCommunities: false (default: true)
• cardType: list (default: card)
• shouldResolveOpenGraph: false (default: true)
• shouldDisplayCommunityBanner: false (default: true)

The old bug where spoiler text appears blank in light mode appears to be back. Probably it's rendering the text as white on white rather than respecting the theme settings.

Go to a thread with more than a screenful of comments. Collapse some comments. Scroll away and back. Comments no longer collapsed.