leehom913@ Thanks for the issue.

Tested this issue on Windows 10, 7, Mac OS 10.13.3 on the reported version 66.0.3359.139 and the latest Canary 68.0.3436.0 and unable to reproduce the issue.

On entering 'navigator.deviceMemory' in console, it is returning 8 in all the pages.
Attached is the screen cast for reference.

Request you to update chrome to the latest Stable, retry the issue on a new chrome profile without any flags,extensions and update the thread with the observations.

thanks,,''

Deleted: 844394.mp4 2.0 MB

	844394.mp4 2.0 MB View Download

the page which navigator.deviceMemory undefined is 
http://www.droidsec.cn/drozer%E6%A8%A1%E5%9D%97%E7%9A%84%E7%BC%96%E5%86%99%E5%8F%8A%E6%A8%A1%E5%9D%97%E5%8A%A8%E6%80%81%E5%8A%A0%E8%BD%BD%E9%97%AE%E9%A2%98%E7%A0%94%E7%A9%B6/

Deleted: 20180522_101136.mp4 8.3 MB

	20180522_101136.mp4 8.3 MB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

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

sorry, please download it

leehom913@ Thanks for the update

Able to reproduce the issue on Windows 10, Mac OS 10.13.3 and Ubuntu 14.04 on the latest Canary 68.0.3439.0 and Stable 66.0.3359.181 as per comment #3.

In the latest Chrome builds, On navigating to the link given in comment #3, entering 'navigator.deviceMemory' in console, it is returning undefined. On any other webpage, navigator.deviceMemory is returning 8 .

In M-60 builds, entering navigator.deviceMemory on any page is returning undefined.
Attached is the screen shot for reference.

This is a Non-Regression issue as this behavior is observed from M60 Chrome builds.
Hence marking this as Untriaged for further updates from Dev.

Thanks..

Deleted: 844394-M60.PNG 94.2 KB

	844394-M60.PNG 94.2 KB View Download

This does not seem like a DOM bug. fmeawad@, history shows you touching this a little at least, any idea where to send this bug?

Thank you for reporting the issue.

This is is WAI,

navigator.deviceMemory only works in secure pages. The page in the example that is returning undefined is an http page (unsecure page).

If you consult sections 3 and 4 of the spec: https://w3c.github.io/device-memory/#sec-device-memory-js-api
you will find that in the definition it mentions that it is only available for secure context, and in the consideration section it mentions that it will only be available in https pages.

Thank you very much for your answer~