Explore the HTML5 Page Visibility API
Aug 28, 2023 pm 07:33 PMEarlier our browsers did not have tabbed browsing feature but today when you check all available browsers we can see that all browsers provide This function. As a programmer, I usually have 10-15 tabs open at a time, and sometimes this number exceeds 25-30.
Why use this API?
Previously, it was impossible to determine which tab was active and which tab was active, but with the help of the HTML5 Visibility API, we can detect whether a visitor is viewing our web page.
In this tutorial, we will learn how to deal with the HTML5 Visibility API and a simple demonstration to discover the state of the page. In this demo, we will change the document title based on the page visibility state.
Check the visibility status of the page
With the introduction of this API, we welcome two new document properties that serve two different functions. The first is document.visibilityState
and the second is document.hidden
.
document.visibilityState
contains four different values ??as follows:
- Hide: The page is not visible on any screen
-
Pre-rendering: The page loads off-screen and is invisible to the user
-
Visible: Page visible
-
Unloaded: The page is about to be unloaded (the user is leaving the current page)
document.hidden
is a Boolean property that is set to false if the page is visible and set to true if the page is hidden.
Now we can control how our website behaves when it is hidden from users.
We know our availability property right away, but now it's time to listen to the event so that we can be notified of new situations regarding the page's visibility. This is done via the visibilitychange
event. We'll see a quick demonstration on how to handle this event.
document.addEventListener('visibilitychange', function(event) { if (!document.hidden) { // The page is visible. } else { // The page is hidden. } });
This code is just a basic example of utilizing this event and discovering the current state of the web page. But just so you know, these properties and methods should all use vendor prefixes because these events and properties are vendor-prefixed in some browsers. Now we'll see the same code cross-browser:
// Get Browser-Specifc Prefix function getBrowserPrefix() { // Check for the unprefixed property. if ('hidden' in document) { return null; } // All the possible prefixes. var browserPrefixes = ['moz', 'ms', 'o', 'webkit']; for (var i = 0; i < browserPrefixes.length; i++) { var prefix = browserPrefixes[i] + 'Hidden'; if (prefix in document) { return browserPrefixes[i]; } } // The API is not supported in browser. return null; } // Get Browser Specific Hidden Property function hiddenProperty(prefix) { if (prefix) { return prefix + 'Hidden'; } else { return 'hidden'; } } // Get Browser Specific Visibility State function visibilityState(prefix) { if (prefix) { return prefix + 'VisibilityState'; } else { return 'visibilityState'; } } // Get Browser Specific Event function visibilityEvent(prefix) { if (prefix) { return prefix + 'visibilitychange'; } else { return 'visibilitychange'; } }
We have all the browser prefix properties and the events are ready to be applied. Now we will change the previous code accordingly.
// Get Browser Prefix var prefix = getBrowserPrefix(); var hidden = hiddenProperty(prefix); var visibilityState = visibilityState(prefix); var visibilityEvent = visibilityEvent(prefix); document.addEventListener(visibilityEvent, function(event) { if (!document[hidden]) { // The page is visible. } else { // The page is hidden. } });
Where can we use this API?
We can consider using this API in many different scenarios.
- Suppose you are on a dashboard and the page is polling at regular intervals (say two minutes) for details of some RSS feed or API. Therefore, we can limit calls to the RSS feed or API if the page is not visible to the user (i.e. the user is not actually viewing the page).
- is used for image sliders. We can limit the movement of the slider image when the page is hidden.
- In a similar way, we can show HTML notifications only when the page is hidden from the user.
So far we've seen the code that uses the HTML5 Page Visibility API, it's time to take some immediate action.
Demo
- Demo 1: This demo shows how to use the Page Visibility API to change the page title. View demo
- Demo 2: This demo demonstrates how to limit polling of data from the server when the page is inactive.
In this demo we will look at how to restrict polling the server for the latest information, but only while the user is viewing the page. I'm assuming jQuery is already included in your page. Here we will just increment the count, but this could be replaced with real server polling.
HTML
<!-- This element will show updated count --> <h1 id="valueContainer">0</h1>
JavaScript
<script type="text/javascript"> // Get Browser Prefix var prefix = getBrowserPrefix(); var hidden = hiddenProperty(prefix); var visibilityState = visibilityState(prefix); var visibilityEvent = visibilityEvent(prefix); var timer = null; function increaseVal() { var newVal = parseInt($('#valueContainer').text()) + parseInt(1); $('#valueContainer').text(newVal); document.title = newVal + ': Running'; timer = setTimeout(function() { increaseVal(); }, 1); } // Visibility Change document.addEventListener(visibilityEvent, function(event) { if (document[hidden]) { clearTimeout(timer); var val = parseInt($('#valueContainer').text()); document.title = val + ': Pause'; } else { increaseVal(); } }); increaseVal(); </script>
Demo view
Browser support
If you want to see browser support for this API, then I recommend checking out Can I use it? . But to find browser support programmatically, I recommend reading this article to detect support for various HTML5 features. So far, we have good support for this API in almost all major and latest browsers.
in conclusion
I would like to say that we have a very good API that only consists of two properties and an event. This way, it can be easily integrated with your existing applications, which may have a positive impact on your user experience. Finally, now we can control how our sites behave when they are hidden from users.
The above is the detailed content of Explore the HTML5 Page Visibility API. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

The main reasons why WordPress causes the surge in server CPU usage include plug-in problems, inefficient database query, poor quality of theme code, or surge in traffic. 1. First, confirm whether it is a high load caused by WordPress through top, htop or control panel tools; 2. Enter troubleshooting mode to gradually enable plug-ins to troubleshoot performance bottlenecks, use QueryMonitor to analyze the plug-in execution and delete or replace inefficient plug-ins; 3. Install cache plug-ins, clean up redundant data, analyze slow query logs to optimize the database; 4. Check whether the topic has problems such as overloading content, complex queries, or lack of caching mechanisms. It is recommended to use standard topic tests to compare and optimize the code logic. Follow the above steps to check and solve the location and solve the problem one by one.

Miniving JavaScript files can improve WordPress website loading speed by removing blanks, comments, and useless code. 1. Use cache plug-ins that support merge compression, such as W3TotalCache, enable and select compression mode in the "Minify" option; 2. Use a dedicated compression plug-in such as FastVelocityMinify to provide more granular control; 3. Manually compress JS files and upload them through FTP, suitable for users familiar with development tools. Note that some themes or plug-in scripts may conflict with the compression function, and you need to thoroughly test the website functions after activation.

Methods to optimize WordPress sites that do not rely on plug-ins include: 1. Use lightweight themes, such as Astra or GeneratePress, to avoid pile-up themes; 2. Manually compress and merge CSS and JS files to reduce HTTP requests; 3. Optimize images before uploading, use WebP format and control file size; 4. Configure.htaccess to enable browser cache, and connect to CDN to improve static resource loading speed; 5. Limit article revisions and regularly clean database redundant data.

The most effective way to prevent comment spam is to automatically identify and intercept it through programmatic means. 1. Use verification code mechanisms (such as Googler CAPTCHA or hCaptcha) to effectively distinguish between humans and robots, especially suitable for public websites; 2. Set hidden fields (Honeypot technology), and use robots to automatically fill in features to identify spam comments without affecting user experience; 3. Check the blacklist of comment content keywords, filter spam information through sensitive word matching, and pay attention to avoid misjudgment; 4. Judge the frequency and source IP of comments, limit the number of submissions per unit time and establish a blacklist; 5. Use third-party anti-spam services (such as Akismet, Cloudflare) to improve identification accuracy. Can be based on the website

TransientsAPI is a built-in tool in WordPress for temporarily storing automatic expiration data. Its core functions are set_transient, get_transient and delete_transient. Compared with OptionsAPI, transients supports setting time of survival (TTL), which is suitable for scenarios such as cache API request results and complex computing data. When using it, you need to pay attention to the uniqueness of key naming and namespace, cache "lazy deletion" mechanism, and the issue that may not last in the object cache environment. Typical application scenarios include reducing external request frequency, controlling code execution rhythm, and improving page loading performance.

When developing Gutenberg blocks, the correct method of enqueue assets includes: 1. Use register_block_type to specify the paths of editor_script, editor_style and style; 2. Register resources through wp_register_script and wp_register_style in functions.php or plug-in, and set the correct dependencies and versions; 3. Configure the build tool to output the appropriate module format and ensure that the path is consistent; 4. Control the loading logic of the front-end style through add_theme_support or enqueue_block_assets to ensure that the loading logic of the front-end style is ensured.

To add custom user fields, you need to select the extension method according to the platform and pay attention to data verification and permission control. Common practices include: 1. Use additional tables or key-value pairs of the database to store information; 2. Add input boxes to the front end and integrate with the back end; 3. Constrain format checks and access permissions for sensitive data; 4. Update interfaces and templates to support new field display and editing, while taking into account mobile adaptation and user experience.

robots.txt is crucial to the SEO of WordPress websites, and can guide search engines to crawl behavior, avoid duplicate content and improve efficiency. 1. Block system paths such as /wp-admin/ and /wp-includes/, but avoid accidentally blocking the /uploads/ directory; 2. Add Sitemap paths such as Sitemap: https://yourdomain.com/sitemap.xml to help search engines quickly discover site maps; 3. Limit /page/ and URLs with parameters to reduce crawler waste, but be careful not to block important archive pages; 4. Avoid common mistakes such as accidentally blocking the entire site, cache plug-in affecting updates, and ignoring the matching of mobile terminals and subdomains.
