


Weekly Platform News: HTML Loading Attribute, the Main ARIA Specifications, and Moving from iFrame to Shadow DOM
This 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)

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.

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.

opacity is an attribute in CSS that controls the overall transparency of an element, with values ranging from 0 (fully transparent) to 1 (fully opaque). 1. It is often used for the image hover fade effect, and enhances the interactive experience by setting the opacity transition; 2. Making a background mask layer to improve text readability; 3. Visual feedback of control buttons or icons in the disabled state. Note that it affects all child elements, unlike rgba, which only affects the specified color part. Smooth animation can be achieved with transition, but frequent use may affect performance. It is recommended to use it in combination with will-change or transform. Rational application of opacity can enhance page hierarchy and interactivity, but it should avoid interfering with users.

accent-color is an attribute used in CSS to customize the highlight colors of form elements such as checkboxes, radio buttons and sliders; 1. It directly changes the default color of the selected state of the form control, such as changing the blue check mark of the checkbox to red; 2. Supported elements include input boxes of type="checkbox", type="radio" and type="range"; 3. Using accent-color can avoid complex custom styles and extra DOM structures, and maintain native accessibility; 4. It is generally supported by modern browsers, and old browsers need to be downgraded; 5. Set accent-col

The:has()pseudo-classinCSSallowstargetingaparentelementbasedonitschildelements.Itworksbyusingthesyntaxparent:has(child-selector)toapplystylesconditionally.Forexample,div:has(img)appliesstylestoadivcontaininganimage.Multipleselectorscanbeusedwithcomma

To beautify the beginning of a paragraph to enhance visual appeal, a common practice is to use pseudo-elements of CSS or manually style the document. In web development, p::first-letter can be used to set the first letter style, such as enlarging, bolding, and discoloring, but it should be noted that it is only suitable for block-level elements; if you want to highlight the entire first line, use p::first-line to add styles; in document software such as Word, you can manually adjust the first letter format or create style templates, and InDesign has a built-in "first-sinking" function suitable for publishing and design; when applying, you need to pay attention to details, such as avoiding complex styles affecting reading and ensuring compatibility and format consistency.

Browser default styles ensure basic readability by automatically applying margins, fills, fonts, and form element styles, but can cause inconsistent cross-browser layouts. 1. The default margin and fill change the layout flow, such as the spacing of titles, paragraphs and lists; 2. The default font settings affect readability, such as 16px font size and TimesNewRoman font; 3. The form elements are very different in different browsers, so the appearance needs to be reset; 4. Some tags such as strong and em have default emphasis styles and need to be explicitly overwritten. Workarounds include using Normalize.css, reset styles, or globally clear margins and fills, while customizing fonts and form styles for consistency.

Use the ::selection pseudo-element of CSS to customize the highlighting style when the web page text is selected to improve the aesthetics and unity of the page. 1. Basic settings: define background-color and color through ::selection, such as yellow background with dark gray fonts; specific elements such as p::selection can also be limited. 2. Compatibility processing: Add the -webkit- prefix to be compatible with Safari and mobile browsers, and the Firefox and Edge standards are well supported. 3. Pay attention to readability: Avoid excessive color contrast or too fancy, and should be coordinated with the overall design. For example, choose a soft blue base in dark mode to improve visual comfort. Reasonable use can enhance the texture of the interface, ignore details
