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

Issue 679243 link

Starred by 1 user
Status: Fixed
Owner:
█ mikhail....@intel.com
Email to this user bounced
Closed: Jan 2017
Cc:
█ brajkumar@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

[REG][Generic Sensor]Cannot fire onchange event after refreshing the page

Reported by canx....@intel.com, Jan 9 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
Test case: https://honry.github.io/demo/tests/onchange-test.https.html
1. Run test, onchange event fired.
2. refresh the page, rerun the test

What is the expected behavior?
Onchange event should be fired.

What went wrong?
Cannot fire onchange event after refreshing the page

Did this work before? Yes Google Chrome Canary 57.0.2959.0 on Windows/Mac OS/Android , Google Chrome Dev 57.0.2950.4 on Linux

Does this work in other browsers? N/A

Chrome version: 57.0.2971.0  Channel: canary
OS Version: 8.1, 10
Flash Version: Shockwave Flash 24.0 r0

This issue also reproduce on Linux/Mac OS and Android.

Comment 1 by brajkumar@chromium.org, Jan 9 2017

Cc: brajkumar@chromium.org
Labels: Needs-Feedback
Tested this issue on Windows-10 and Ubuntu 14.04 using chrome latest canary M57-55.0.2883.87. By opening the provided test case link observed the result is displayed saying Fail. While opening the dev console seeing error "Failed to load resource: the server responded with status of 404.
 
Observed same behavior on chrome #57.0.2959.0 as well. Could you please let us know is there any other alternate way to reproduce this issue from chrome test team end.

Thanks!
Screen-shot.PNG
291 KB View Download

Comment 2 by canx....@intel.com, Jan 9 2017 

@mikhail.pozdnyakov  Please help to take a look this issue.Thanks

Comment 3 by mikhail....@intel.com, Jan 13 2017

Owner: mikhail....@intel.com
Status: Assigned (was: Unconfirmed)

Comment 4 by mikhail....@intel.com, Jan 25 2017

Status: Started (was: Assigned)
Project Member

Comment 5 by bugdroid1@chromium.org, Jan 27 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/c78e848fc18f203167cb53aedc0e3736bce149b1

commit c78e848fc18f203167cb53aedc0e3736bce149b1
Author: mikhail.pozdnyakov <mikhail.pozdnyakov@intel.com>
Date: Fri Jan 27 13:31:00 2017

[Sensors] Fix reading updates after page refresh

This patch fixes reading updates after page refresh. The route cause of the problem was that the outdated document instance was cached in SensorProxy.

BUG= 679243 
BUG= 606766 

Review-Url: https://codereview.chromium.org/2644873002
Cr-Commit-Position: refs/heads/master@{#446658}

[modify] https://crrev.com/c78e848fc18f203167cb53aedc0e3736bce149b1/third_party/WebKit/Source/modules/sensor/Sensor.cpp
[modify] https://crrev.com/c78e848fc18f203167cb53aedc0e3736bce149b1/third_party/WebKit/Source/modules/sensor/SensorProviderProxy.cpp
[modify] https://crrev.com/c78e848fc18f203167cb53aedc0e3736bce149b1/third_party/WebKit/Source/modules/sensor/SensorProviderProxy.h
[modify] https://crrev.com/c78e848fc18f203167cb53aedc0e3736bce149b1/third_party/WebKit/Source/modules/sensor/SensorProxy.cpp
[modify] https://crrev.com/c78e848fc18f203167cb53aedc0e3736bce149b1/third_party/WebKit/Source/modules/sensor/SensorProxy.h
[modify] https://crrev.com/c78e848fc18f203167cb53aedc0e3736bce149b1/third_party/WebKit/Source/modules/sensor/SensorReadingUpdater.cpp
[modify] https://crrev.com/c78e848fc18f203167cb53aedc0e3736bce149b1/third_party/WebKit/Source/modules/sensor/SensorReadingUpdater.h

Comment 6 by mikhail....@intel.com, Jan 27 2017

Status: Fixed (was: Started)

Comment 7 by canx....@intel.com, Feb 4 2017 

@mikhail.pozdnyakov , I verified this issue with the latest chromium,
It's has been fixed on windows/Android canary channel(58.0.3000.4).
But this issue is still exist on Linux Dev channel(57.0.2987.19), please help to fix it on Linux.
Thanks.

Comment 8 by canx....@intel.com, Feb 4 2017 

I updated the latest chromium on Linux Dev channel (58.0.3000.4).
This issue has been fixed.
Thanks.
►

Sign in to add a comment