Currently, Google is busy in experimenting some new features that enable the user to use web applications by staying awake even if there is no keyboard and mouse activity. For this purpose, WakeLock API will be used to wake lock the screen, protecting it from entering into the power-saving mode.
The code for WakeLock API is available and will be used as a new feature very soon. There are many pros and cons of the Wake Lock to look for before going crazy after this new feature.
Users can certainly take advantage of this new feature while watching long videos, following a recipe, navigation and other tasks that require longer screen time. You can also read e-books for hours without worrying about your screen going to sleep again and again.
The WakeLock API is currently in works but the developers must be aware of the compatibility issues that can arise after its implementation.
The intent to implement WakeLock API is existing since April 2018 after second iteration of this new feature is carried out. Right now, the developers are discussing the shape of the API and if the “screen wake lock” subset of the full specification is sufficient for their use cases.
Once the test turns out to be successful, the new feature will be launched for Chrome OS, Android, Windows, Linux, and Mac.
The first drawback is that there is no notification or permissions in the experimental phase to aware the user of the awake state while the page is open in the foreground.
The power and battery of the gadget will be affected enormously as the system will not send any notification to the user about the screen lock.
Real-time tracking will become an issue along with facing cryptomining troubles. Anyone can easily track the movement of the user even when the user is not using the screen.
Photo: Jon Fingas / Engadget
Read next: After Mozilla, Google Chrome tests to block third party cookies to warn advertisers
The code for WakeLock API is available and will be used as a new feature very soon. There are many pros and cons of the Wake Lock to look for before going crazy after this new feature.
Wake Lock Pros
To activate Wake Lock, the user would have to make a request to prevent the system from power lock or from turning off the display. The reasons to introduce this new feature is to enable users get rid of native apps to perform several operations.Users can certainly take advantage of this new feature while watching long videos, following a recipe, navigation and other tasks that require longer screen time. You can also read e-books for hours without worrying about your screen going to sleep again and again.
The WakeLock API is currently in works but the developers must be aware of the compatibility issues that can arise after its implementation.
The intent to implement WakeLock API is existing since April 2018 after second iteration of this new feature is carried out. Right now, the developers are discussing the shape of the API and if the “screen wake lock” subset of the full specification is sufficient for their use cases.
Once the test turns out to be successful, the new feature will be launched for Chrome OS, Android, Windows, Linux, and Mac.
Wake Lock Cons
If this new feature is launched, Chrome will be the one web browsers that will be subjected to more and more abuse possibilities.The first drawback is that there is no notification or permissions in the experimental phase to aware the user of the awake state while the page is open in the foreground.
The power and battery of the gadget will be affected enormously as the system will not send any notification to the user about the screen lock.
Real-time tracking will become an issue along with facing cryptomining troubles. Anyone can easily track the movement of the user even when the user is not using the screen.
Photo: Jon Fingas / Engadget
Read next: After Mozilla, Google Chrome tests to block third party cookies to warn advertisers
