-
Notifications
You must be signed in to change notification settings - Fork 11
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
[Story] View expanded map #1678
Comments
@julioromano in the review today we've found that the pin is too big in the expanded map and you said this might already be fixed. Could you verify that and if it is fix, set the Android status of this story to "Reviewed"? |
It is fixed. But we're still missing on android this too element-hq/element-x-android#916 |
If the location permission is granted: - Shows the user's own location - Shows a button to center the map on it Part of: - element-hq/element-meta#1678
It's now been merged but technically it's not been reviewed. |
Ok, thanks. I'll put this on the agenda for review again in the next weekly. |
…923) This will help in catching alignment regressions. Related to: - element-hq/element-meta#1678
As per newer design specs. Related to: - element-hq/element-meta#1678
1. On devices less than xhdpi request a 1x image from MapTiler (such devices are generally old, slower and with little memory so avoiding to get the 2x image only to have to shrink it later could help). 2. Coerce too big width/height combos within the API limits keeping the aspect ratio (this will allow requests on big horizontal displays to succeed). 3. Don't crash when given weird width/height combos (i.e. zero or negative). 4. Introduce interfaces to hide this whole logic and make it easier for forks to implement their own. Related to: - element-hq/element-meta#1678
Size estimate
S
Dependencies
Acceptance criteria
$screen
screenName = LocationView
Out of scope
Sign-off
Android
iOS
Subtasks
Android
iOS
Other
The text was updated successfully, but these errors were encountered: