New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 744208 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jul 24
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

[Restrict-View-Google] Scroll up and down problem

Project Member Reported by mili.adl...@samsung.com, Jul 17 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
1. Try to access Naver -> 
2. Go to Naver blog
3. Not able to scroll up and down

What is the expected behavior?
Scroll up and down should be smooth for the users

What went wrong?
Not able to scroll up and down while accessing Naver blogs

Did this work before? N/A 

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

The issue is seen sometimes.
 
Getting these logs : 
Line 68161 : 07-15 22:05:24.668   712   712 I chromium: [INFO:CONSOLE(15)] "The key "target-densitydpi" is not supported.", source: https://m.blog.naver.com/PostView.nhn?blogId=badafishing2016&logNo=221024432360&proxyReferer=https%3A%2F%2Fm.search.naver.com%2Fsearch.naver%3Fquery%3D%25EB%258C%2580%25EB%258F%2599%25EB%25B0%25B0%2B%25EB%2582%259A%25EC%258B%259C%26where%3Dm%26sm%3Dmob_hty.idx%26acq%3D%26acr%3D%26qdt%3D1 (15)
Line 68352 : 07-15 22:05:25.204   712   712 I chromium: [INFO:CONSOLE(1)] "해당 옵션은 사용할 수 없습니다.
Line 68353 : 07-15 22:05:25.204   712   712 I chromium:    xhr-timout", source: https://ssl.pstatic.net/t.static.blog/nmobile/versioning/LegoCommonJS-1912307012_https.js (1)
Line 71164 : 07-15 22:05:32.791   712   712 I chromium: [INFO:CONSOLE(1)] "Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.", source: https://ssl.pstatic.net/t.static.blog/nmobile/versioning/LegoCommonJS-1912307012_https.js (1)
Line 89804 : 07-15 22:06:19.976   712   712 I chromium: [INFO:CONSOLE(15)] "The key "target-densitydpi" is not supported.", source: https://m.blog.naver.com/PostView.nhn?blogId=badafishing2016&logNo=221024432360&proxyReferer=https%3A%2F%2Fm.search.naver.com%2Fsearch.naver%3Fquery%3D%25EB%258C%2580%25EB%258F%2599%25EB%25B0%25B0%2B%25EB%2582%259A%25EC%258B%259C%26where%3Dm%26sm%3Dmob_hty.idx%26acq%3D%26acr%3D%26qdt%3D1 (15)
Line 90000 : 07-15 22:06:20.450   712   712 I chromium: [INFO:CONSOLE(1)] "해당 옵션은 사용할 수 없습니다.
Line 90001 : 07-15 22:06:20.450   712   712 I chromium:    xhr-timout", source: https://ssl.pstatic.net/t.static.blog/nmobile/versioning/LegoCommonJS-1912307012_https.js (1)
Line 90139 : 07-15 22:06:20.923   712   712 I chromium: [INFO:CONSOLE(1)] "Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.", source: https://ssl.pstatic.net/t.static.blog/nmobile/versioning/LegoCommonJS-1912307012_https.js (1)
Labels: Needs-Triage-M59
Cc: brajkumar@chromium.org
Labels: Needs-Feedback
Tested this issue on Windows-10 using chrome latest stable #59.0.3071.115 by following steps mentioned below, Please correct me incase if any of theses steps are not correct.

1. Navigated to site https://section.blog.naver.com/SectionMain.nhn
2. Scrolled the webpage top to bottom screen ratio at 110%
3. Observed no scrolling issue using external mouse and touch pad.

Reporter@ Are you able to reproduce this issue on incognito mode as well? Please recheck this issue by crating a new profile under chrome://settings with no apps or extensions in your browser. 

Thanks!
This is the problem which is seen sometimes.
Not able to reproduce it right now.

In many issues we find such kind of logs are coming :
Query :
What could be the probable cause for such logs? 
Is the app should check as the deprecated APIs are used?

Project Member

Comment 5 by sheriffbot@chromium.org, Jul 17 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Since this issue has doesn't have consistent Repro steps, requesting UI team to look in  to this issue.

Thanks!!
Is there any update on this issue? 
Project Member

Comment 8 by sheriffbot@chromium.org, Jul 24

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment