Skip to content
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

Images expand in the timeline, causing a pop-in effect and scrolling issues #6654

Closed
turt2live opened this issue May 2, 2018 · 10 comments
Closed
Labels
A-Media A-Timeline P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@turt2live
Copy link
Member

Description

This is a regression from a previous version (possibly related to the image stuff?). Whenever someone posts an image, it starts of at ~30px high then pops in to the full height after loading. This can sometimes throw off the scroll position, leaving the user at a weird place. Previously the space was reserved for the image in the timeline.

Version information

  • Platform: web (in-browser)
  • Browser: Chrome 65
  • OS: Windows 10
  • URL: riot.im/develop
@lampholder
Copy link
Member

I thought this was fixed (with the fix itself then causing #6652). But you filed this a day ago, which suggests it's still broken :\

@lampholder lampholder added T-Defect ui/ux P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround A-Timeline A-Media labels May 3, 2018
@turt2live
Copy link
Member Author

In this case it's the opposite of #6652: images start small then expand.

@turt2live
Copy link
Member Author

For scale on how annoying this is: I deployed 0.15.1 to our webserver and got 5 complaints in the first 15 minutes. Rolling back to 0.14.2 'fixes' the issue.

@lukebarnard1
Copy link
Contributor

lukebarnard1 commented May 17, 2018

OK. Now that we've released something, let's look at this more carefully. I'm pretty sure there's a simple solution that involves no fixup height shenanigans.

@dbkr
Copy link
Member

dbkr commented May 17, 2018

Is this in an e2e room?

@dbkr
Copy link
Member

dbkr commented May 17, 2018

I suspect it almost certainly is, which means its #6742 which I didn't realise was a regression

@turt2live
Copy link
Member Author

This is not an e2e room. I generally don't use e2e personally except in rare cases.

It's also not specific to a given room. As mentioned in riot-dev, I can try to get a recording if it helps.

@ara4n
Copy link
Member

ara4n commented May 17, 2018

@turt2live can you confirm this fixed in 0.15.2 btw?

@turt2live
Copy link
Member Author

Is fixed, thank you!

@ara4n
Copy link
Member

ara4n commented May 17, 2018

thanks for bumping it earlier - i'd assumed it had been fixed earlier and for whatever reason we hadn't been seeing the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Media A-Timeline P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Development

No branches or pull requests

5 participants