{"id":2213,"date":"2026-09-25T08:35:10","date_gmt":"2026-09-25T08:35:10","guid":{"rendered":"https:\/\/newsraise.com\/in\/2026\/09\/25\/google-chrome-154-iframe-auto-resize-http-prompts\/"},"modified":"2026-09-25T08:35:10","modified_gmt":"2026-09-25T08:35:10","slug":"google-chrome-154-iframe-auto-resize-http-prompts","status":"publish","type":"post","link":"https:\/\/newsraise.com\/in\/2026\/09\/25\/google-chrome-154-iframe-auto-resize-http-prompts\/","title":{"rendered":"Google launches Chrome 154 with iframe auto\u2011resize and HTTP prompts"},"content":{"rendered":"\n<!-- Quick Adsense WordPress Plugin: http:\/\/quickadsense.com\/ -->\n<div class=\"9fece8afa224fd09e54b043d0febfb58\" data-index=\"1\" style=\"float: none; margin:10px 0 10px 0; text-align:center;\">\n<script async src=\"https:\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js\"><\/script>\r\n<!-- NR ATF -->\r\n<ins class=\"adsbygoogle\"\r\n     style=\"display:block\"\r\n     data-ad-client=\"ca-pub-8898941184964366\"\r\n     data-ad-slot=\"4839033563\"\r\n     data-ad-format=\"auto\"\r\n     data-full-width-responsive=\"true\"><\/ins>\r\n<script>\r\n     (adsbygoogle = window.adsbygoogle || []).push({});\r\n<\/script>\n<\/div>\n<p>Google released Chrome 154 as the newest stable version of its flagship browser on September 25. The update makes two user\u2011facing changes default: an automatic resizing mechanism for iframes and a confirmation dialog that appears before the browser connects to sites that use the unencrypted <code>http:\/\/<\/code> scheme. In addition, the release bundles a range of CSS and JavaScript API extensions aimed at developers.<\/p>\n<h2>Automatic iframe resizing simplifies embedded content<\/h2>\n<p>Historically, developers who wanted an iframe to grow or shrink based on the size of the embedded document had to write JavaScript that measured the child page, sent the dimensions to the parent via <code>postMessage()<\/code>, and then adjusted the iframe\u2019s height attribute. Chrome 154 removes that complexity. By applying a specific CSS rule to the iframe element on the parent page and inserting a meta tag into the embedded page, the browser automatically matches the iframe\u2019s height to the content\u2019s layout. The change streamlines the creation of dynamic widgets such as blog sidebars, comment sections, and third\u2011party embeds, where the amount of content can vary widely.<\/p>\n<p>Alongside the iframe improvement, Chrome 154 expands scroll\u2011marker\u2011related CSS capabilities. The <code>scroll-marker-group<\/code> property now supports two distinct modes. In the default \u201clinks\u201d mode, markers act as navigation links, allowing users to move focus sequentially with the Tab key. When the \u201ctabs\u201d mode is selected, the group behaves like a tab list: only the active marker receives focus, arrow keys shift focus between markers, and content belonging to inactive tabs is omitted from the accessibility tree. This dual\u2011mode approach gives developers greater flexibility to build accessible carousels and tabbed interfaces using primarily CSS.<\/p>\n<h2>Security upgrade: ask before HTTP<\/h2>\n<p>Chrome 154 also changes the default handling of insecure connections. The new \u201cAsk before HTTP\u201d setting triggers a confirmation prompt whenever a user attempts to navigate to a URL that begins with <code>http:\/\/<\/code>. While HTTPS encrypts traffic between browser and server, HTTP transmits data in clear text, exposing users to potential interception or tampering. By prompting users, Chrome reduces the likelihood of accidental exposure to insecure sites. Enterprise administrators can still manage the behavior through the <code>HttpsOnlyMode<\/code> policy, which provides granular control over the feature in managed environments.<\/p>\n<p>The release notes also mention that the browser\u2019s Background Fetch API now enforces Cross\u2011Origin Resource Sharing (CORS) rules, and that attempts to reach local or loopback addresses require explicit Local Network Access permission. These measures tighten the security model for background network operations and local\u2011network interactions.<\/p>\n<h2>Developer\u2011focused API additions and platform enhancements<\/h2>\n<p>Developers receive a suite of new APIs and refinements in Chrome 154. Workers can now construct various CSS Typed Object Model (Typed OM) objects directly, expanding the ability to manipulate styles in background scripts. Font handling is enriched with a <code>FontFace.width<\/code> property and a corresponding <code>font-width<\/code> descriptor for <code>@font-face<\/code>, both acting as aliases for the existing <code>stretch<\/code> and <code>font-stretch<\/code> attributes.<\/p>\n<p>The \u201clight dismiss\u201d behavior for popovers and dialogs has been tuned so that scrolling on touch screens or right\u2011click actions no longer close the overlay unintentionally. On the JavaScript side, <code>Iterator.prototype.includes()<\/code> is introduced, mirroring the familiar <code>Array.prototype.includes()<\/code> semantics for iterator objects. The <code>WebSocket<\/code> constructor now accepts a second argument \u2013 a <code>WebSocketInit<\/code> options object \u2013 paving the way for future extensions. One of the new options, <code>targetAddressSpace<\/code>, lets developers specify whether the connection should target a \u201clocal\u201d or \u201cloopback\u201d address space, which is useful for communicating with local servers that lack HTTPS support.<\/p>\n<p>Additional updates include a stricter CORS check for the Background Fetch API, a new error condition for Secure Payment Confirmation when a language tag does not match the dialog language, and the introduction of a \u201cWindow Shape API\u201d for Isolated Web Apps on ChromeOS allow\u2011listed devices. The latter enables developers to define non\u2011rectangular windows or windows composed of multiple separate regions, opening possibilities for widgets and floating panels.<\/p>\n<p>Although the release notes list support for the CSS <code>text-decoration-inset<\/code> property, ChromeStatus indicates that its activation has been delayed until Chrome 156.<\/p>\n<p>Chrome 154 also launches several experimental features under origin trials. \u201cPrivate Verification Tokens (PVT)\u201d are being tested to allow trust signals gathered during normal browsing to be carried into incognito sessions, with the goal of reducing repetitive challenges such as CAPTCHAs while preserving privacy.<\/p>\n<p>Beyond the core browser, Google is enhancing cross\u2011device continuity. According to reporting by The Verge, the existing \u201csend tab\u201d feature now remembers scroll position, so users who switch from mobile to desktop (or vice versa) resume reading at the exact spot they left off. Form entries that have not yet been submitted are also retained across devices, helping users continue lengthy tasks without losing progress.<\/p>\n<p>The Gemini AI assistant, integrated into Chrome, receives new study\u2011support capabilities. It can now analyze, visualize, and summarize a broader range of media, including podcasts and videos hosted outside of YouTube. After playing an audio or video file, users may ask Gemini to extract key points, locate specific information, or clarify confusing sections. Additionally, Gemini can generate interactive quizzes based on the content of open tabs. The quiz feature is rolling out in English for desktop users in the United States and India, with plans to expand to other regions and to mobile platforms in the coming months.<\/p>\n<p>The next stable version, Chrome 155, is slated for release on October 6, 2026, local time. Meanwhile, Google\u2019s broader ecosystem continues to evolve, with services such as BigGo Finance positioned to appear first in Google Search Top Stories, promising users immediate access to comprehensive financial news.<\/p>\n\n<div style=\"font-size: 0px; height: 0px; line-height: 0px; margin: 0; padding: 0; clear: both;\"><\/div>","protected":false},"excerpt":{"rendered":"<p>Google rolled out Chrome 154, adding default iframe auto\u2011resize, a prompt before connecting to HTTP sites, and a suite of developer\u2011focused API enhancements.<\/p>\n","protected":false},"author":2,"featured_media":2214,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[299],"tags":[2377,1426,1375,2379,2378],"class_list":["post-2213","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-browser-update","tag-chrome","tag-google","tag-web-development","tag-web-security","entry"],"_links":{"self":[{"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/posts\/2213","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/comments?post=2213"}],"version-history":[{"count":0,"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/posts\/2213\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/media\/2214"}],"wp:attachment":[{"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/media?parent=2213"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/categories?post=2213"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/newsraise.com\/in\/wp-json\/wp\/v2\/tags?post=2213"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}