New issue
Advanced search Search tips

Issue 818465 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

imags are not loaded on time (starting from 67.0.3360.0)

Project Member Reported by mar...@mwiacek.com, Mar 3 2018

Issue description

Device name:s7

From "Settings > About Chrome"
Application version:67.0.3360.0
Operating system:7

URLs (if applicable):https://pclab.pl/news77175.html

Steps to reproduce:
(1)open url
(2)scroll slowly down

Expected result:
images are loaded when white area connected with them is visible

Actual result:
images are not loaded on time and user needs to move page few times to have reaction
 

Comment 1 by mar...@mwiacek.com, Mar 4 2018

Summary: imags are not loaded on time (starting from 67.0.3360.0) (was: imags are not loaded on time (67.0.3360.0))
I have theory, that page offsets are not correctly marked and pictures not loaded on time.
Labels: Needs-triage-Mobile

Comment 3 by pdr@chromium.org, Mar 6 2018

Thanks for filing these bugs. I think this is likely the same as  https://crbug.com/818464  and should be fixed. Can you check whether this has been fixed in the latest canary?

Comment 4 by mar...@mwiacek.com, Mar 6 2018

 https://crbug.com/818464  was marked as duplicate for https://bugs.chromium.org/p/chromium/issues/detail?id=818519, which is Twitter related.

Here we don't have Twitter and with 3362 (latest Canary available for me) I still see this problem.
Cc: pdr@chromium.org pnangunoori@chromium.org
Labels: Triaged-Mobile
Tested on Samsung S6 Android 6.0.1, Samsung J7 Android 7.0.0 and Pixel Android 8 using the latest Canary #67.0.3363.3, Stable #65.0.3325.109 & 60.0.3072.0 and able to reproduce the issue. Issue is also reproduced on FireFox mobile version. And, it seems to be the site specific issue.

pdr@ -- This seems to be site related issue. Could you please confirm.

Thanks!

Comment 6 by pdr@chromium.org, Mar 7 2018

Status: WontFix (was: Unconfirmed)
Based on pnangunoori's comment, I tried this in Firefox and do see the same issue. I think this is a site issue after all.

I'll close this as WontFix for now but please comment if this analysis is wrong.

Sign in to add a comment