Don't we already largely have shell parity? Most of these interactions and controls exist. Some of them, like button and slate, have bugs that make them not as good as the shell, but it may be more effective to track those bugs individually.
I think this issue is designed to be a parent issue (i.e. tracking the larger area). I don't think that there's any specific action to be taken on this specific issue itself.
Yes, this is the parent to other issues in ZenHub. Still experimenting...
I have updated the list with detailed items.
Also is the Loss of Tracking message.
Currently applications need to build their own or use the Unity default behavior (which is a static non-localized image).
I'm building something with parity currently.
@cre8ivepark this was marked as to be completed in May 2019 milestone but there are items in here like #4332 that I do not think we will get to even in June, because of other higher priority items. I've removed the 1905 milestone for now. Since this feels more like a running list of items I'm not sure we want to put a milestone for this issue, just because we will probabably always have things that are not quite matching shell parity, and will need to add to this list.
@julenka Sounds good. I have updated the page with RC2 and RC3 section.
Hi @cre8ivepark I really like the splitting of GA and Future. There are a couple bugs that are in future which I actually think are bugs in functionality and therefore should be in for GA. I've updated this.
Closing out GA epics
Most helpful comment
Also is the Loss of Tracking message.
Currently applications need to build their own or use the Unity default behavior (which is a static non-localized image).
I'm building something with parity currently.