Mirrors bug mega-compilation (from Slack)

Jerud

Jay I'll have to trust you on the first one; I'm really buried right now.
For the second one, I went back to the original offender and it's repaired now -- since I couldn't get it to happen anywhere else I'll just have to watch for it happening again and maybe I can figure out the common thread.

My big lesson-learned here is to ALWAYS post a screenshot so I remember which items to test with when I come back to verify the bug fix...!!!

I got buried and will hopefully get a chance to catch up in a week or so... looking forward to testing some of these fixes from the original list and marking them off.

Jerud

Jay I'm not seeing any beta offering for Legend in TestFlight, just an old instance of Moo. Do you need to add me into the new app's TestFlight group or something?

Jay

Jerud There's no beta version in TestFlight right now, just the live Legend app. The iPhone app is a wrapper around the mobile web app that provides native features like notifications and the email functionality. When we do updates to the app functionality otherwise you just need to have "Use Beta Version" selected in the app's settings to get beta updates.

Jerud

Jay Oh snap, I can't believe I missed that. Now that you've said it, I'm sure you already said it before...my bad!

Jerud

Update to the "grandfather zoom" bug: I think the behavior is now (selectively) reversed. @Jay I'm not sure when this happened but maybe in the last week or two. I know I saw the particular affected items not long ago because I've been working in them.

I have two mirrors in particular that ONLY appear if I'm zoomed to its direct parent. When I'm at the next level up, they both go away. If I use "back" to toggle between these two states, I actually see these two items turn grey and disappear, along with the message "14 items were hidden because they do not match search"

https://www.screencast.com/t/FY7VNmA3Y5vn

Some interesting details to note about this situation:

The message says 14 items -- only two are actually removed from the view
All I'm doing is using 'back' once to 'undo the zoom'. No search/filter changes at all.
There is a third mirror in this same location that is not impacted by this bug

Jerud

Can't even report a bug without finding a new one in the process...

Now I'm seeing one mirror that is in 3 locations but only shows two in the "tally box".
It also happens to disappear from one of those locations (the one not shown in the expanded tally box) when the "hide completes" filter is active, even though it's not complete and not a parent.

What @Jeff says above is really true...mirrors should absolutely not be out in Stable at all. It just makes Legend /look bad/. I'm SO glad I didn't originally "find" while it was in a state like this or I'd have never given it a second look.

Jeff

There are several inconsistent/unexpected behaviours with the number boxes to the right of a mirror.

In some cases, if you click on the number box of a mirror, and click on the link to the original, the view is scrolled there and it's highlighted for a couple of seconds (though the cursor isn't moved). But if you're zoomed in to a parent or grandparent of the mirror, clicking on the link to the original just highlights the mirror itself. There's no way to go to the original; clicking on either link does the same thing. Except if the original is in another document, then it takes you there as expected, except then the cursor is at the top of that document, which I would not expect. Also, if the expansion state of the mirror doesn't match that of the original, the view may be scrolled to some random destination.

Jerud

I still haven't circled back on this post to verify all the fixes...Still need to (but man what an unpleasant task).

However I did just encounter the following issue, which already had a thread here documenting it:
#135

Jerud

New mirror BUG with repro @Jay , for a change : ) I've seen this before but couldn't reliably reproduce it.

What just happened was that I created a new mirror by drag/dropping it onto a child of a Mirror. The newly-created mirrors draw at an impossible indent. In this case the two top-level mirror-parents were in different documents. The left one was the original, and the ones that I dragged in to the right one are originally in the same document as the left Parent.

I WAS able to repro this. The key is that the Mirrored Parent has to itself be a child ("SPOT claim for leg xray" in the screenshot). It doesn't matter where the drag-in mirrors are coming from, although their indent level can cause the resulting 'offset' to be larger or smaller. The prefixes, tags, and email attachment don't impact the behavior.

Jay

Jerud Thanks! Fixed in #137166

Jeff

Jay In case you're working on mirroring bugs again, I updated the description of problems with mirrors from local files degrading into links: #33711

I might as well copy it here too:

Mirrors going from:

a cloud or local document to somewhere else in the same document - ok
a cloud document to another cloud document, or to a local document - ok
a local document to a cloud document - after quitting and restarting the app, turns into a link in the cloud document, permanently.
a local document to a local document - randomly: after quitting and restarting, turns into a link, but only sometimes. Other times it continues to work. When it does turn into a link, switching to another document in the pane and then back again makes it turn back into a mirror.

Fixing this, as well as the unable to move mirrors in mobile bug, would go a long way to making mirrors usable for me, thanks.

« Previous Page