Parent Rem Bug During Queue

I believe this was part of one of the more recent updates. I think it was implemented because sometimes, the extra card detail is specific for a child of the card rather than the entire card itself.

Explanation: Using your screenshots as an example, Similar to and Useful descriptor rems are relevant extra details to the Definition rem rather than to the Oxidation Number rem itself. It makes sense to mention that the Similar to descriptor is related to the Definition rem.

This is happening with this card specifically because it is a backward card. If you look for the preview of the forward card, you will probably see that it appears the same as your second screenshot.
I hope this makes sense :sweat_smile:

Thank you for responding. I think your explanation makes sense. After previewing the forward card, I still get the same effect, though. (I guess it is still considered a child rem of the ~Definition descriptor? :thinking:.)

My apologies. I was mistaken about the forward-enabled cards, they also appear to show up the same way in the queue.
It was my understanding that this was to make it easier to understand any extra card detail of child rems (in case of multiline rems wherein a child rem(s) has a rem nested under it as extra card detail). It would help to know which child rem this detail is related to since it appears at the bottom of the entire multiline.

I have such a card in my KB:

Upon previewing the card generated by the parent rem, I noticed that the extra card detail that is nested under the Function descriptor does not appear, so my theory was probably incorrect.

Apparently, this is not the case. Sorry for the confusion, that’s my bad. I don’t think it used to happen before the update, so it could be a bug.

1 Like