-
Notifications
You must be signed in to change notification settings - Fork 563
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[iOS-Android-Web][ImageSet Rendering] [No parity in rendering of images in imageSet for various imageSizes] #4043
Comments
@paulcam206 this seems related to the investigation you did for #4035 no? @jwoo-msft FYI. |
Hi @adumrewal. We have acknowledged this issue report. Please continue to follow this issue for updates/progress/questions. @matthidinger / @dclaux / @RebeccaAnne / @paulcam206 / @jwoo-msft / @almedina-ms FYI. |
no -- #4035 is UWP-specific |
@almedina-ms & @golddove can you check if Android does the right thing as specified in here. @dclaux could you please update JS renderer as was discussed here |
@jwoo-msft are we actually targeting this for 20.06 release ? This one will include a behavior change that will need to be documented as well and the behavior needing to be vetted for UWP/.NET to ensure it's consistent. Also am assuming iOS' behavior is consistent and the baseline behavior we want to go with? |
Reopening to track remaining platforms |
Hi @adumrewal. We have acknowledged this issue report. Please continue to follow this issue for updates/progress/questions. |
🎉 Handy links: |
Platform
What platform is your issue or question related to? (Delete other platforms).
Author or host
Host - Teams
What version are you using? Ex: NuGet 1.0.2, or latest master, etc...
1.2.7 on iOS
Details
When using imageSize for imageSet, there is no parity between the rendering experience on the three clients ( iOS, Android and Web). Sample JSON and screenshots are attached.
Card JSON:
Json for card with Large images:
imageSetLarge.txt
Json for card with Small images:
imageSetSmall.txt
The text was updated successfully, but these errors were encountered: