| Four weeks have passed since the release of Chrome 113, and Google recently released Chrome 114 on time. |
Four weeks have passed since the release of Chrome 113, and Google recently released Chrome 114 on time. Chrome 114 has CHIPS enabled by default, which is part of Google's move to phase out third-party cookies with new cookie attributes; Chrome 114 also enables the Popover API by default to make popovers easier to implement.
text-wrap:balance
Use text-wrap-balance to improve text layout. The animation below shows the difference you can make with just one line of code.
As a developer, you don't know the final size of the text, the font size, or even the language of the text. All variables are needed to efficiently handle text wrapping. Since the browser does know all the factors, with text-wrap:balance you can ask the browser to figure out the best solution.
Balanced blocks of text are more pleasing to the reader's eyes. It grabs the reader's attention better and is generally easier to read.
CHIPS: Cookies with independent partition state.
Previously, when a user visited site A, embedded site C could set a cookie on the user's machine. If the user then visits Site B, which is also embedded in Site C, Site C can access the same cookie that was set on Site A. This allows Site C to compile the user's browsing activity across Sites A, B, and each site it embeds.
While cross-site tracking is an issue, there are valid cross-site cookie requirements that can be implemented in a privacy-preserving manner through cookie partitioning.
With CHIPS, when a user visits site A and the embedded content in site C sets a cookie with the Partitioned attribute, the cookie set when site C is embedded on site A is only saved in the partitioned jar. The browser will only send this cookie if the top-level site is A.
When a user visits a new site, say site B, site C will not receive the cookie that was set when C was embedded in site A.
Popover API
With the Popover API, it's easier to create temporary user interface (UI) elements that are displayed on top of all other Web application UIs.
These elements include user-interactive elements such as action menus, form element suggestions, content selectors, and teaching UI. The new popover property enables any element to be automatically displayed on top. This means developers no longer have to worry about positioning, stacking elements, focus, or keyboard interaction.
other
Devtools lets you pause and debug C and C++ code in DWARF-enabled WebAssembly applications. The
exclusionFilters option in navigator.bluetooth.requestDevice() allows web developers to exclude some devices from browser selectors.
More details can be found at: https://developer.chrome.com/en/blog/new-in-chrome-114/
The original text comes from: Chrome 114 is officially released, supporting CHIPS - OSCHINA - Chinese Open Source Technology Exchange Community
Address of this article: Chrome114 is released on time and already supports CHIPS | "This is how Linux should learn"