


Weekly Platform News: HTML Loading Attribute, the Main ARIA Specifications, and Moving from iFrame to Shadow DOM
Apr 17, 2025 am 10:55 AMThis week’s platform news roundup: Chrome introduces a new loading attribute that provides accessibility specifications for web developers, and the BBC’s migration of visualizations to Shadow DOM.
Chrome launches loading attributes
Chrome now supports HTML loading properties for lazy loading images and iframes. You can add loading="lazy"
to<mark>延遲加載圖像</mark>
and iframe (located below the viewport) and they will not be loaded until the user scrolls nearby.
Google recommends treating this feature as a progressive enhancement, or using it on top of existing JavaScript-based lazy loading solutions.
This feature has not been added to the HTML standard (but there is an open pull request), and its Chrome status page lists multiple links to Google Docs. (From web.dev)
ARIA Specification Overview
Key accessibility specifications for web developers:
Related: “Associate with the ARIA Authoring Practices Guide” by Simon Pieters and Valerie Young
Shadow DOM on the BBC website
The BBC has implemented embedded interactive visualization on its website from<iframe></iframe>
Migrate to Shadow DOM. This results in a significant improvement in loading performance ("more than 25% faster").
The available Shadow DOM polyfills cannot reliably prevent styles from leaking across Shadow DOM boundaries, so they decided to fall back to the browser that does not support Shadow DOM.<iframe></iframe>
.
Shadow DOM [...] can serve content in a similar way to an iframe, in terms of encapsulation, but without negative overhead [...] We want to encapsulate an element whose content will be displayed seamlessly as part of the page. Shadow DOM provides this for us without custom elements.
A major disadvantage of this new approach is that CSS media queries can no longer be used to conditionally apply styles based on the width of the content (because the content is no longer loaded into a separate embedded document).
When using an iframe, media query provides our content width; when using Shadow DOM, media query provides the device itself width. This is a huge challenge for us. We have no way of knowing the size of the content when it is provided.
(From Toby Cox)
Other news...
- The next version of Chrome will introduce the Largest Contentful Paint performance metric; this new metric more accurately replaces the first meaningful drawing, which measures when the largest element in the viewport is rendered (usually the largest image or text paragraph) (from Phil Walton)
- Microsoft has created a prototype of a new tool for viewing web DOM in 3D; this tool is now available experimentally in Edge Preview (from Edge DevTools)
- Tracking protection is enabled by default in Edge preview; it is set to balancing mode by default, which "blocks malicious trackers and some third-party trackers" (from Techdows)
Read more news in my new weekly Sunday edition . Visit webplatform.news for more information.
The above is the detailed content of Weekly Platform News: HTML Loading Attribute, the Main ARIA Specifications, and Moving from iFrame to Shadow DOM. 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)

There are three ways to create a CSS loading rotator: 1. Use the basic rotator of borders to achieve simple animation through HTML and CSS; 2. Use a custom rotator of multiple points to achieve the jump effect through different delay times; 3. Add a rotator in the button and switch classes through JavaScript to display the loading status. Each approach emphasizes the importance of design details such as color, size, accessibility and performance optimization to enhance the user experience.

To deal with CSS browser compatibility and prefix issues, you need to understand the differences in browser support and use vendor prefixes reasonably. 1. Understand common problems such as Flexbox and Grid support, position:sticky invalid, and animation performance is different; 2. Check CanIuse confirmation feature support status; 3. Correctly use -webkit-, -moz-, -ms-, -o- and other manufacturer prefixes; 4. It is recommended to use Autoprefixer to automatically add prefixes; 5. Install PostCSS and configure browserslist to specify the target browser; 6. Automatically handle compatibility during construction; 7. Modernizr detection features can be used for old projects; 8. No need to pursue consistency of all browsers,

Use the clip-path attribute of CSS to crop elements into custom shapes, such as triangles, circular notches, polygons, etc., without relying on pictures or SVGs. Its advantages include: 1. Supports a variety of basic shapes such as circle, ellipse, polygon, etc.; 2. Responsive adjustment and adaptable to mobile terminals; 3. Easy to animation, and can be combined with hover or JavaScript to achieve dynamic effects; 4. It does not affect the layout flow, and only crops the display area. Common usages are such as circular clip-path:circle (50pxatcenter) and triangle clip-path:polygon (50%0%, 100 0%, 0 0%). Notice

Themaindifferencesbetweendisplay:inline,block,andinline-blockinHTML/CSSarelayoutbehavior,spaceusage,andstylingcontrol.1.Inlineelementsflowwithtext,don’tstartonnewlines,ignorewidth/height,andonlyapplyhorizontalpadding/margins—idealforinlinetextstyling

Setting the style of links you have visited can improve the user experience, especially in content-intensive websites to help users navigate better. 1. Use CSS's: visited pseudo-class to define the style of the visited link, such as color changes; 2. Note that the browser only allows modification of some attributes due to privacy restrictions; 3. The color selection should be coordinated with the overall style to avoid abruptness; 4. The mobile terminal may not display this effect, and it is recommended to combine it with other visual prompts such as icon auxiliary logos.

To create responsive images using CSS, it can be mainly achieved through the following methods: 1. Use max-width:100% and height:auto to allow the image to adapt to the container width while maintaining the proportion; 2. Use HTML's srcset and sizes attributes to intelligently load the image sources adapted to different screens; 3. Use object-fit and object-position to control image cropping and focus display. Together, these methods ensure that the images are presented clearly and beautifully on different devices.

The choice of CSS units depends on design requirements and responsive requirements. 1.px is used for fixed size, suitable for precise control but lack of elasticity; 2.em is a relative unit, which is easily caused by the influence of the parent element, while rem is more stable based on the root element and is suitable for global scaling; 3.vw/vh is based on the viewport size, suitable for responsive design, but attention should be paid to the performance under extreme screens; 4. When choosing, it should be determined based on whether responsive adjustments, element hierarchy relationships and viewport dependence. Reasonable use can improve layout flexibility and maintenance.

Different browsers have differences in CSS parsing, resulting in inconsistent display effects, mainly including the default style difference, box model calculation method, Flexbox and Grid layout support level, and inconsistent behavior of certain CSS attributes. 1. The default style processing is inconsistent. The solution is to use CSSReset or Normalize.css to unify the initial style; 2. The box model calculation method of the old version of IE is different. It is recommended to use box-sizing:border-box in a unified manner; 3. Flexbox and Grid perform differently in edge cases or in old versions. More tests and use Autoprefixer; 4. Some CSS attribute behaviors are inconsistent. CanIuse must be consulted and downgraded.
