fullscreen api safari ios

WebKit Features in Safari 16.4

Mar 27, 2023

by Patrick Angle, Marcos Caceres, Razvan Caliman, Jon Davis, Brady Eidson, Timothy Hatcher, Ryosuke Niwa, and Jen Simmons

Web Push on iOS and iPadOS

Improvements for web apps, web components, javascript and webassembly, images, video, and audio, developer tooling, web inspector, safari web extensions, safari content blockers, new restrictions in lockdown mode, more improvements.

Today, we’re thrilled to tell you about the many additions to WebKit that are included in Safari 16.4. This release is packed with 135 new web features and over 280 polish updates. Let’s take a look.

You can experience Safari 16.4 on macOS Ventura , macOS Monterey, macOS Big Sur, iPadOS 16 , and iOS 16 . Update to Safari 16.4 on macOS Monterey or macOS Big Sur by going to System Preferences → Software Update → More info, and choosing to update Safari. Or update on macOS Ventura, iOS or iPadOS, by going to Settings → General → Software Update.

iOS and iPadOS 16.4 add support for Web Push to web apps added to the Home Screen. Web Push makes it possible for web developers to send push notifications to their users through the use of Push API , Notifications API , and Service Workers .

Deeply integrated with iOS and iPadOS, Web Push notifications from web apps work exactly like notifications from other apps. They show on the Lock Screen, in Notification Center, and on a paired Apple Watch. Focus provides ways for users to precisely configure when or where to receive Web Push notifications — putting users firmly in control of the experience. For more details, read Web Push for Web Apps on iOS and iPadOS .

WebKit on iOS and iPadOS 16.4 adds support for the Badging API . It allows web app developers to display an app badge count just like any other app on iOS or iPadOS. Permission for a Home Screen web app to use the Badging API is automatically granted when a user gives permission for notifications.

To support notifications and badging for multiple installs of the same web app, WebKit adds support for the id member of the Web Application Manifest standard. Doing so continues to provide users the convenience of saving multiple copies of a web app, perhaps logged in to different accounts separating work and personal usage — which is especially powerful when combined with the ability to customize Home Screen pages with different sets of apps for each Focus .

iOS and iPadOS 16.4 also add support so that third-party web browsers can offer “Add to Home Screen” in the Share menu. For the details on how browsers can implement support, as well more information about all the improvements to web apps, read Web Push for Web Apps on iOS and iPadOS .

We continue to care deeply about both the needs of a wide-range of web developers and the everyday experience of users. Please keep sending us your ideas and requests . There’s more work to do, and we couldn’t be more excited about where this space is headed.

Web Components is a suite of technologies that together make it possible to create reusable custom HTML elements with encapsulated functionality. Safari 16.4 improves support for Web Components with several powerful new capabilities.

Safari 16.4 adds support Declarative Shadow DOM, allowing developers to define shadow DOM without the use of JavaScript. And it adds support for ElementInternals , providing the basis for improved accessibility for web components, while enabling custom elements to participate in forms alongside built-in form elements.

Also, there’s now support for the Imperative Slot API. Slots define where content goes in the template of a custom element. The Imperative Slot API allows developers to specify the assigned node for a slot element in JavaScript for additional flexibility.

Safari 16.4 adds support for quite a few new CSS properties, values, pseudo-classes and syntaxes. We are proud to be leading the way in several areas to the future of graphic design on the web.

Margin Trim

The margin-trim property can be used to eliminate margins from elements that are abutting their container. For example, imagine we have a section element, and inside it we have content consisting of an h2 headline and several paragraphs. The section is styled as a card, with an off-white background and some padding. Like usual, the headline and paragraphs all have top and bottom margins — which provide space between them. But we actually don’t want a margin above the first headline, or after the last paragraph. Those margins get added to the padding, and create more space than what’s desired.

Often web developers handle this situation by removing the top margin on the headline with h2 { margin-block-start: 0 } and the bottom margin on the last paragraph with p:last-child { margin-block-end: 0 } — and hoping for the best. Problems occur, however, when unexpected content is placed in this box. Maybe another instance starts with an h3 , and no one wrote code to remove the top margin from that h3 . Or a second h2 is written into the text in the middle of the box, and now it’s missing the top margin that it needs.

The margin-trim property allows us to write more robust and flexible code. We can avoid removing margins from individual children, and instead put margin-trim: block on the container.

This communicates to the browser: please trim away any margins that butt up against the container. The rule margin-trim: block trims margins in the block direction, while margin-trim: inline trims margins in the inline direction.

Try this demo for yourself in Safari 16.4 or Safari Technology Preview to see the results.

Safari 16.4 also adds support for the new line height and root line height units, lh and rlh . Now you can set any measurement relative to the line-height. For example, perhaps you’d like to set the margin above and below your paragraphs to match your line-height.

The lh unit references the current line-height of an element, while the rlh unit references the root line height — much like em and rem.

Safari 16.4 adds support for font-size-adjust . This CSS property provides a way to preserve the apparent size and readability of text when different fonts are being used. While a web developer can tell the browser to typeset text using a specific font size, the reality is that different fonts will render as different visual sizes. You can especially see this difference when more than one font is used in a single paragraph. In the following demo , the body text is set with a serif font, while the code is typeset in a monospace font — and they do not look to be the same size. The resulting differences in x-height can be quite disruptive to reading. The demo also provides a range of font fallback options for different operating systems, which introduces even more complexity. Sometimes the monospace font is bigger than the body text, and other times it’s smaller, depending on which font family is actually used. The font-size-adjust property gives web developers a solution to this problem. In this case, we simply write code { font-size-adjust: 0.47; } to ask the browser to adjust the size of the code font to match the actual glyph size of the body font.

To round out support for the font size keywords, font-size: xxx-large is now supported in Safari 16.4.

Pseudo-classes

Safari 16.4 also adds support for several new pseudo-classes. Targeting a particular text direction, the :dir() pseudo-class lets you define styles depending on whether the language’s script flows ltr (left-to-right) or rtl ( right-to-left ). For example, perhaps you want to rotate a logo image a bit to the left or right, depending on the text direction:

Along with unprefixing the Fullscreen API (see below), the CSS :fullscreen pseudo-class is also now unprefixed. And in Safari 16.4, the :modal pseudo-class also matches fullscreen elements.

Safari 16.4 adds :has() support for the :lang pseudo-class, making it possible to style any part of a page when a particular language is being used on that page. In addition, the following media pseudo-classes now work dynamically inside of :has() , opening up a world of possibilities for styling when audio and video are in different states of being played or manipulated — :playing , :paused , :seeking , :buffering , :stalled , :picture-in-picture , :volume-locked , and :muted . To learn more about :has() , read Using :has() as a CSS Parent Selector and much more .

Safari 16.4 adds support for Relative Color Syntax. It provides a way to specify a color value in a much more dynamic fashion. Perhaps you want to use a hexadecimal value for blue, but make that color translucent — passing it into the hsl color space to do the calculation.

Or maybe you want to define a color as a variable, and then adjust that color using a mathematical formula in the lch color space, telling it to cut the lightness ( l ) in half with calc(l / 2) , while keeping the chroma ( c ) and hue ( h ) the same.

Relative Color Syntax is powerful. Originally appearing in Safari Technology Preview 122 in Feb 2021, we’ve been waiting for the CSS Working Group to complete its work so we could ship. There isn’t documentation on MDN or Can I Use about Relative Color Syntax yet, but likely will be soon. Meanwhile the Color 5 specification is the place to learn all about it.

Last December, Safari 16.2 added support for color-mix() . Another new way to specify a color value, the functional notation of color-mix makes it possible to tell a browser to mix two different colors together, using a certain color space .

Safari 16.4 adds support for using currentColor with color-mix() . For example, let’s say we want to grab whatever the current text color might be, and mix 50% of it with white to use as a hover color. And we want the mathematical calculations of the mixing to happen in the oklab color space. We can do exactly that with:

Safari 16.2 also added support for Gradient Interpolation Color Spaces last December. It allows the interpolation math of gradients — the method of determining intermediate color values — to happen across different color spaces. This illustration shows the differences between the default sRGB interpolation compared to interpolation in lab and lch color spaces:

Safari 16.4 adds support for the new system color keywords . Think of them as variables which represent the default colors established by the user, browser, or OS — defaults that change depending on whether the system is set to light mode, dark mode, high contrast mode, etc. For instance, Canvas represents the current default background color of the HTML page. Use system color keywords just like other named colors in CSS. For example, h4 { color: FieldText; } will style h4 headlines to match the default color of text inside form fields. When a user switches from light to dark mode, the h4 color will automatically change as well. Find the full list of system colors in CSS Color level 4 .

Media Queries Syntax Improvements

Safari 16.4 adds support for the syntax improvements from Media Queries level 4. Range syntax provides an alternative way to write out a range of values for width or height. For example, if you want to define styles that are applied when the browser viewport is between 400 and 900 pixels wide, in the original Media Query syntax, you would have written:

Now with the new syntax from Media Queries level 4, you can instead write:

This is the same range syntax that’s been part of Container Queries from its beginning, which shipped in Safari 16.0 .

Media Queries level 4 also brings more understandable syntax for combining queries using boolean logic with and , not , and or . For example:

Can instead be greatly simplified as:

Or, along with the range syntax changes, as:

Custom Properties

Safari 16.4 adds support for CSS Properties and Values API with support for the @property at-rule. It greatly extends the capabilities of CSS variables by allowing developers to specify the syntax of the variable, the inheritance behavior, and the variable initial value — similar to how browser engines define CSS properties.

With @property support, developers can to do things in CSS that were impossible before, like animate gradients or specific parts of transforms.

Web Animations

Safari 16.4 includes some additional improvements for web animations. You can animate custom properties. Animating the blending of mismatched filter lists is now supported. And Safari now supports KeyframeEffect.iterationComposite .

Outline + Border Radius

Until now, if a web developer styled an element that had an outline with a custom outline-style , and that element had curved corners, the outline would not follow the curve in Safari. Now in Safari 16.4, outline always follows the curve of border-radius .

CSS Typed OM

Safari 16.4 adds support for CSS Typed OM , which can be used to expose CSS values as typed JavaScript objects. Input validation for CSSColorValues is also supported as part of CSS Typed OM. Support for Constructible and Adoptable CSSStyleSheet objects also comes to Safari 16.4.

Safari 16.4 now supports lazy loading iframes with loading="lazy" . You might put it on a video embed iframe, for example , to let the browser know if this element is offscreen, it doesn’t need to load until the user is about to scroll it into view.

By the way, you should always include the height and width attributes on iframes, so browsers can reserve space in the layout for it before the iframe has loaded. If you resize the iframe with CSS, be sure to define both width and height in your CSS. You can also use the aspect-ratio property to make sure an iframe keeps it’s shape as it’s resized by CSS.

Now in Safari 16.4, a gray line no longer appears to mark the space where a lazy-loaded image will appear once it’s been loaded.

Safari 16.4 also includes two improvements for <input type="file"> . Now a thumbnail of a selected file will appear on macOS. And the cancel event is supported.

Safari 16.4 brings a number of useful new additions for developers in JavaScript and WebAssembly.

RegExp Lookbehind makes it possible to write Regular Expressions that check what’s before your regexp match. For example, match patterns like (?<=foo)bar matches bar only when there is a foo before it. It works for both positive and negative lookbehind.

JavaScript Import Maps give web developers the same sort of versioned file mapping used in other module systems, without the need for a build step.

Growable SharedArrayBuffer provided a more efficient mechanism for growing an existing buffer for generic raw binary data. And resizable ArrayBuffer allows for resizing of a byte array in JavaScript.

In WebAssembly, we’ve added support for 128-bit SIMD.

Safari 16.4 also includes:

• Array.fromAsync
• Array#group and Array#groupToMap
• Atomics.waitAsync
• import.meta.resolve()
• Intl.DurationFormat
• String#isWellFormed and String#toWellFormed
• class static initialization blocks
• Symbols in WeakMap and WeakSet

Safari 16.4 adds support for quite a few new Web API. We prioritized the features you’ve told us you need most.

Offscreen Canvas

When using Canvas, the rendering, animation, and user interaction usually happens on the main execution thread of a web application. Offscreen Canvas provides a canvas that can be rendered off screen, decoupling the DOM and the Canvas API so that the <canvas> element is no longer entirely dependent on the DOM. Rendering can now also be transferred to a worker context, allowing developers to run tasks in a separate thread and avoid heavy work on the main thread that can negatively impact the user experience. The combination of DOM-independent operations and rendering of the main thread can provide a significantly better experience for users, especially on low-power devices. In Safari 16.4 we’ve added Offscreen Canvas support for 2D operations. Support for 3D in Offscreen Canvas is in development.

Fullscreen API

Safari 16.4 now supports the updated and unprefixed Fullscreen API on macOS and iPadOS. Fullscreen API provides a way to present a DOM element’s content so that it fills the user’s entire screen, and to exit fullscreen mode once it’s unneeded. The user is given control over exiting fullscreen mode through various mechanisms, include pressing the ‘Esc’ key on the keyboard, or performing a downwards gesture on touch-enabled devices. This ensures that the user always has the ability to exit fullscreen whenever they desire, preserving their control over the browsing experience.

Screen Orientation API

Along with the Fullscreen API we’ve added preliminary support for Screen Orientation API in Safari 16.4, including:

• ScreenOrientation.prototype.type returns the screen’s current orientation.
• ScreenOrientation.prototype.angle returns the screen’s current orientation angle.
• ScreenOrientation.prototype.onchange event handler, which fires whenever the screen changes orientation.

Support for the lock() and unlock() methods remain experimental features for the time being. If you’d like to try them out, you can enable them in the Settings app on iOS and iPadOS 16.4 via Safari → Advanced → Experimental Features → Screen Orientation API (Locking / Unlocking).

Screen Wake Lock API

The Screen Wake Lock API provides a mechanism to prevent devices from dimming or locking the screen. The API is useful for any application that requires the screen to stay on for an extended period of time to provide uninterrupted user experience, such as a cooking site, or for displaying a QR code.

User Activation API

User Activation API provides web developers with a means to check whether a user meaningfully interacted with a web page. This is useful as some APIs require meaningful “user activation”, such as, a click or touch, before they can be used. Because user activation is based on a timer, the API can be used to check if document currently has user activation as otherwise a call to an API would fail. Read The User Activation API for more details and usage examples.

WebGL Canvas Wide Gamut Color

WebGL canvas now supports the display-p3 wide-gamut color space. To learn more about color space support, read Improving Color on the Web , Wide Gamut Color in CSS with Display-P3 , and Wide Gamut 2D Graphics using HTML Canvas .

Compression Streams API

Compression Streams API allows for compressing and decompressing streams of data in directly in the browser, reducing the need for a third-party JavaScript compression library. This is handy if you need to “gzip” a stream of data to send to a server or to save on the user’s device.

Safari 16.4 also includes many other new Web API features, including:

• Reporting API
• Notification API in dedicated workers
• Permissions API for dedicated workers
• Service Workers and Shared Workers to the Permissions API
• gamepad.vibrationActuator
• A submitter parameter in the FormData constructor
• COEP violation reporting
• COOP/COEP navigation violation reporting
• Fetch Initiator
• Fetch Metadata Request Headers
• importing compressed EC keys in WebCrypto
• loading scripts for nested workers
• non-autofill credential type for the autocomplete attribute
• revoking Blob URLs across same-origin contexts
• isComposing attribute on InputEvent
• termination of nested workers
• transfer size metrics for first parties in ServerTiming and PerformanceResourceTiming
• KeyframeEffect.iterationComposite
• WEBGL_clip_cull_distance

Last fall, Safari 16 brought support for AVIF images to iOS 16, iPadOS 16 and macOS Ventura. Now with Safari 16.4, AVIF is also supported on macOS Monterey and macOS Big Sur. Updates to our AVIF implementation ensure animated images and images with film grain (noise synthesis) are now fully supported, and that AVIF works inside the <picture> element. We’ve also updated our AVIF implementation to be more lenient in accepting and displaying images that don’t properly conform to the AVIF standard.

Safari 16.4 adds support for the video portion of Web Codecs API . This gives web developers complete control over how media is processed by providing low-level access to the individual frames of a video stream. It’s especially useful for applications that do video editing, video conferencing, or other real-time processing of video.

Media features new to Safari 16.4 also include:

• Improvements to audio quality for web video conferencing
• Support for a subset of the AudioSession Web API
• Support for AVCapture virtual cameras
• Support for inbound rtp trackIdentifier stat field
• Support for VTT-based extended audio descriptions
• Support to allow a site to provide an “alternate” URL to be used during AirPlay

WKPreferences , used by WKWebView on iOS and iPadOS 16.4, adds a new shouldPrintBackgrounds API that allows clients to opt-in to including a pages’s background when printing.

Inspectable WebKit and JavaScriptCore API

Across all platforms supporting WKWebView or JSContext , a new property is available called isInspectable ( inspectable in Objective-C) on macOS 13.4 and iOS, iPadOS, and tvOS 16.4. It defaults to false , and you can set it to true to opt-in to content being inspectable using Web Inspector, even in release builds of apps.

When an app has enabled inspection, it can be inspected from Safari’s Develop menu in the submenu for either the current computer or an attached device. For iOS and iPadOS, you must also have enabled Web Inspector in the Settings app under Safari > Advanced > Web Inspector .

To learn more, read Enabling the Inspection of Web Content in Apps .

When automating Safari 16.4 with safaridriver , we now supports commands for getting elements inside shadow roots, as well as accessibility commands for getting the computed role and label of elements. When adding a cookie with safaridriver , the SameSite attribute is now supported. Improvements have also been made to performing keyboard actions, including better support for modifier keys behind held and support for typing characters represented by multiple code points, including emoji. These improvements make writing cross-browser tests for your website even easier.

Typography Tooling

Web Inspector in Safari 16.4 adds new typography inspection capabilities in the Fonts details sidebar of the Elements Tab.

Warnings are now shown for synthesized bold and oblique when the rendering engine has to generate these styles for a font that doesn’t provide a suitable style. This may be an indicator that the font file for a declared @font-face was not loaded. Or it may be that the specific value for font-weight or font-style isn’t supported by the used font.

A variable font is a font format that contains instructions on how to generate, from a single file, multiple style variations, such as weight, stretch, slant, optical sizing, and others. Some variable fonts allow for a lot of fine-tuning of their appearance, like the stroke thickness, the ascender height or descender depth, and even the curves or roundness of particular glyphs. These characteristics are expressed as variation axes and they each have a custom value range defined by the type designer.

The Fonts details sidebar now provides interactive controls to adjust values of variation axes exposed by a variable font and see the results live on the inspected page allowing you to get the font style that’s exactly right for you.

Tooling for Conditionals in CSS

The controls under the new User Preference Overrides popover in the Elements Tab allow you to emulate the states of media features like prefers-reduced-motion and prefers-contrast to ensure that the web content you create adapts to the user’s needs. The toggle to emulate the states of prefers-color-scheme , which was previously a standalone button, has moved to this new popover.

The Styles panel of the Elements Tab now allows editing the condition text for @media , @container and @supports CSS rules. This allows you to make adjustments in-context and immediately see the results on the inspected page. Here’s a quick tip: edit the condition of @supports to its inverse, like @supports not (display: grid) , to quickly check your progressive enhancement approach to styling and layout.

Badging HTML Elements

New badges for elements in the DOM tree of the Elements Tab join the existing badges for Grid and Flex containers. The new Scroll badge calls out scrollable elements, and the new Events badge provides quick access to the event listeners associated with the element when clicked. And a new Badges toolbar item makes it easy to show just the badges you are interested in and hide others.

Changes to Web Inspector in Safari 16.4 also include:

• Elements Tab: Improved visual hierarchy of the Layout sidebar.
• Elements Tab: Added support for nodes that aren’t visible on the page to appear dimmed in the DOM tree.
• Console Tab: Added support for console snippets.
• Sources Tab: Added showing relevant special breakpoints in the Pause Reason section.
• Sources Tab: Added support for inline breakpoints.
• Sources Tab: Added support for symbolic breakpoints
• Network Tab: Added a Path column.
• Network Tab: Added alphabetic sorting of headers.
• Network Tab: Added support for per-page network throttling.
• Network Tab: Added using the Shift key to highlight the initiator or initiated resources.
• Graphics Tab: Added OpenGL object IDs in the Canvas inspector.
• Settings Tab: Added a setting to turn off dimming nodes that aren’t visible on the page.
• Added support for function breakpoints and tracepoints.

Enhancements to Declarative Net Request

Safari is always working on improving support for declarativeNetRequest , the declarative way for web extensions to block and modify network requests. In Safari 16.4, several enhancements have been added to the API:

• The declarativeNetRequest.setExtensionActionOptions API can be used to configure whether to automatically display the action count (number of blocked loads, etc.) as the extension’s badge text.
• The modifyHeaders action type has been added to rewrite request and response headers. This action requires granted website permissions for the affected domains and the declarativeNetRequestWithHostAccess permission in the manifest.
• The redirect action type now requires the declarativeNetRequestWithHostAccess permission in the manifest.
• The MAX_NUMBER_OF_DYNAMIC_AND_SESSION_RULES property has been added to check the maximum number of combined dynamic and session rules an extension can add. The current limit is set at 5,000 rules.

These enhancements give developers more options to customize their content blocking extensions and provide users with better privacy protection.

SVG Icon Support in Web Extensions

Safari 16.4 now supports SVG images as extension and action icons, giving developers more options for creating high-quality extensions. This support brings Safari in line with Firefox, allowing for consistent experiences across platforms. The ability to scale vector icons appropriately for any device means developers no longer need multiple sizes, simplifying the process of creating polished and professional-looking extensions.

Dynamic Content Scripts

Safari 16.4 introduces support for the new scripting.registerContentScript API, which enables developers to create dynamic content scripts that can be registered, updated, or removed programmatically. This API augments the static content scripts declared in the extension manifest, providing developers with more flexibility in managing content scripts and enabling them to create more advanced features for their extensions.

Toggle Reader Mode

The tabs.toggleReaderMode API has been added to Safari 16.4, which enables extensions to toggle Reader Mode for any tab. This function is particularly useful for extensions that want to enhance the user’s browsing experience by allowing them to focus on the content they want to read. By using this API, developers can create extensions that automate the process of enabling Reader Mode for articles, making it easier and more convenient for users to read online content.

Session Storage

The storage.session API, now supported in Safari 16.4, enables extensions to store data in memory for the duration of the browser session, making it a useful tool for storing data that takes a long time to compute or is needed quickly between non-persistent background page loads. This API is particularly useful for storing sensitive or security-related data, such as decryption keys or authentication tokens, that would be inappropriate to store in local storage. The session storage area is not persisted to disk and is cleared when Safari quits, providing enhanced security and privacy for users.

Background Modules

Developers can now take advantage of modules in background service workers and pages by setting "type": "module" in the background section of the manifest. This allows for more organized and maintainable extension code, making it easier to manage complex codebases. By setting this option, background scripts will be loaded as ES modules, enabling the use of import statements to load dependencies and use the latest JavaScript language features.

Safari 16.4 has added support for :has() selectors in Safari Content Blocker rules. This is a powerful new addition to the declarative content blocking capabilities of Safari, as it allows developers to select and hide parent elements that contain certain child elements. Its inclusion in Safari Content Blocker rules opens up a whole new range of possibilities for content blocking. Now developers can create more nuanced and precise rules that can target specific parts of a web page, making it easier to block unwanted content while preserving the user’s browsing experience. This is yet another example of Safari’s commitment to providing a secure and private browsing experience for its users while also offering developers the tools they need to create innovative and effective extensions.

Lockdown Mode is an optional, extreme protection that’s designed for the very few individuals who, because of who they are or what they do, might be personally targeted by some of the most sophisticated digital threats. Most people are never targeted by attacks of this nature.

If a user chooses to enable Lockdown mode on iOS 16.4, iPadOS 16.4, or macOS Ventura 13.3, Safari will now:

• Disable binary fonts in the CSS Font Loading API
• Disable Cache API
• Disable CacheStorage API
• Disable ServiceWorkers
• Disable SVG fonts
• Disable the WebLocks API
• Disable WebSpeech API

Safari 16.4 now supports dark mode for plain text files. It has support for smooth key-driven scrolling on macOS. And it adds prevention of redirects to data: or about: URLs.

In addition to the 135 new features, WebKit for Safari 16.4 includes an incredible amount work polishing existing features. We’ve heard from you that you want to know more about the many fixes going into each release of Safari. We’ve done our best to list everything that might be of interest to developers, in this case, 280 of those improvements:

• Fixed -webkit-mask-box-image: initial to set the correct initial value.
• Fixed -webkit-radial-gradient parsing accidentally treating several mandatory commas as optional.
• Fixed ::placeholder to not support writing-mode , direction , or text-orientation.
• Fixed @supports to not work if not , or , or and isn’t followed by a space.
• Fixed background-repeat not getting correctly exposed through inline styles.
• Fixed baseline-shift to allow length or percentage, but not numbers.
• Fixed contain: inline-size for replaced elements.
• Fixed CSSPerspective.toMatrix() to throw a TypeError if its length is incompatible with the px unit.
• Fixed cx , cy , x , and y CSS properties to allow length or percentage, but not numbers.
• Fixed filter: blur on an absolutely positioned image losing overflow: hidden .
• Fixed font-face to accept ranges in reverse order, and reverse them for computed styles.
• Fixed font-style: oblique must allow angles equal to 90deg or -90deg.
• Fixed font-style: oblique with calc() to allow out-of-range angles and clamp them for computed style.
• Fixed font-weight to clamp to 1 as a minimum.
• Fixed font shorthand to reject out-of-range angles for font-style .
• Fixed font shorthand to reset more longhand properties.
• Fixed overflow-x: clip causing a sibling image to not load.
• Fixed overflow: clip not working on SVG elements.
• Fixed stroke-dasharray parsing to align with standards.
• Fixed stroke-width and stroke-dashoffset parsing to align with standards.
• Fixed text-decoration-thickness property not repainting when changed.
• Fixed allowing calc() that combines percentages and lengths for line-height .
• Fixed an issue where using box-sizing: border-box causes the calculated aspect-ratio to create negative content sizes.
• Fixed an issue with a monospace font on a parent causing children with a sans-serif font using rem or rlh units to grow to a larger size.
• Fixed behavior of cursor: auto over links.
• Fixed buttons with auto width and height to not set intrinsic margins.
• Fixed calculating block size to use the correct box-sizing with aspect ratio.
• Fixed cells overflowing their contents when a table cell has inline children which change writing-mode .
• Fixed clipping perspective calc() values to 0.
• Fixed font shorthand to not reject values that happen to have CSS-wide keywords as non-first identifiers in a font family name.
• Fixed hit testing for double-click selection on overflowing inline content.
• Fixed honoring the content block size minimum for a <fieldset> element with aspect-ratio applied.
• Fixed incorrectly positioned line break in contenteditable with tabs.
• Fixed invalidation for class names within :nth-child() selector lists.
• Fixed omitting the normal value for line-height from the font shorthand in the specified style, not just the computed style.
• Fixed pseudo-elements to not be treated as ASCII case-insensitive.
• Fixed rejecting a selector argument for :nth-of-type or :nth-last-of-type .
• Fixed serialization order for contain .
• Fixed strings not wrapped at zero width spaces when word-break: keep-all is set.
• Fixed supporting <string> as an unprefixed keyframe name.
• Fixed the :has() pseudo-selector parsing to be unforgiving.
• Fixed the font-face src descriptor format to allow only specified formats, others are a parse error.
• Fixed the tz component not accounting for zoom when creating a matrix3d () value.
• Fixed the computed value for stroke-dasharray to be in px .
• Fixed the effect of the writing-mode property not getting removed when the property is removed from the root element.
• Fixed the position of text-shadow used with text-combine-upright .
• Fixed the title of a style element with an invalid type to never be added to preferred stylesheet set.
• Fixed the transferred min/max sizes to be constrained by defined sizes for aspect ratio.
• Fixed the user-agent stylesheet to align hidden elements, abbr , acronym , marquee , and fieldset with HTML specifications.
• Fixed to always use percentages for computed values of font-stretch , never keywords.
• Fixed to not require whitespace between of and the selector list in :nth-child or :nth-last-child .
• Fixed CSS.supports returning false for custom properties.
• Fixed CSS.supports whitespace handling with !important .
• Fixed forgiving selectors to not be reported as supported with CSS.supports("selector(...)") .
• Fixed getComputedStyle() to return a function list for the transform property.
• Fixed linear-gradient keyword values not getting converted to their rgb() equivalents for getComputedStyle() .

Content Security Policy

• Fixed updating the Content Security Policy when a new header is sent as part of a 304 response.
• Fixed <input type="submit"> , <input type="reset">, and <input type="button"> to honor font-size , padding , height , and work with multi-line values.
• Fixed firing the change event for <input type="file"> when a different file with the same name is selected.
• Fixed preventing a disabled <fieldset> element from getting focus.
• Fixed the :out-of-range pseudo class matching for empty input[type=number] .
• Fixed Array.prototype.indexOf constant-folding to account for a non-numeric index.
• Fixed Intl.NumberFormat useGrouping handling to match updated specs.
• Fixed Intl.NumberFormat ignoring maximumFractionDigits with compact notation.
• Fixed String.prototype.includes incorrectly returning false when the string is empty and the position is past end of the string.
• Fixed toLocaleLowerCase and toLocaleUpperCase to throw an exception on an empty string.
• Fixed aligning the parsing of <body link vlink alink> to follow standards.
• Fixed <legend> to accept more display property values than display: block .

Intelligent Tracking Prevention

• Fixed user initiated cross-domain link navigations getting counted as Top Frame Redirects.
• Fixed some display issues with HDR AVIF images.
• Fixed the accept header to correctly indicate AVIF support.

Lockdown Mode

• Fixed common cases of missing glyphs due to custom icon fonts.
• Fixed enumerateDevices may return filtered devices even if page is capturing.
• Fixed MediaRecorder.stop() firing an additional dataavailable event with bytes after MediaRecorder.pause() .
• Fixed duplicate timeupdate events.
• Fixed limiting DOMAudioSession to third-party iframes with microphone access.
• Fixed MSE to not seek with no seekable range.
• Fixed mute microphone capture if capture fails to start because microphone is used by a high priority application.
• Fixed not allowing text selection to start on an HTMLMediaElement.
• Fixed only requiring a transient user activation for Web Audio rendering.
• Fixed screen capture to fail gracefully if the window or screen selection takes too long.
• Fixed switching to alternate <source> element for AirPlay when necessary.
• Fixed the local WebRTC video element pausing after bluetooth audioinput is disconnected.
• Fixed trying to use low latency for WebRTC HEVC encoder when available.
• Fixed unmuting a TikTok video pauses it.
• Fixed WebVTT styles not applied with in-band tracks.
• Ensured negative letter-spacing does not pull content outside of the inline box
• Fixed <div> with border-radius not painted correctly while using jQuery’s .slideToggle() .
• Fixed border-radius clipping on composited layers.
• Fixed box-shadow to paint correctly on inline elements.
• Fixed box-shadow invalidation on inline boxes.
• Fixed calculating the width of an inline text box using simplified measuring to handle fonts with Zero Width Joiner , Zero Width Non-Joner , or Zero Width No-Break Space .
• Fixed clearing floats added dynamically to previous siblings.
• Fixed clipping the source image when the source rectangle is outside of the source image in canvas.
• Fixed CSS keyframes names to not allow CSS wide keywords.
• Fixed elements with negative margins not avoiding floats when appropriate.
• Fixed floating boxes overlapping with their margin boxes.
• Fixed HTMLImageElement width and height to update layout to return styled dimensions not the image attributes.
• Fixed ignoring nowrap on <td nowrap="nowrap"> when an absolute width is specified.
• Fixed incorrect clipping when a layer is present between the column and the content layer.
• Fixed incorrect static position of absolute positioned elements inside relative positioned containers.
• Fixed layout for fixed position elements relative to a transformed container.
• Fixed layout overflow rectangle overflows interfering with the scrollbar.
• Fixed negative shadow repaint issue.
• Fixed preventing a focus ring from being painted for anonymous block continuations.
• Fixed recalculating intrinsic widths in the old containing block chain when an object goes out of flow.
• Fixed rendering extreme border-radius values.
• Fixed specified hue interpolation method for hues less than 0 or greater than 360.
• Fixed tab handling in right-to-left editing.
• Fixed text selection on flex and grid box items.
• Fixed the position and thickness of underlines to be device pixel aligned.
• Fixed transforms for table sections.
• Fixed transition ellipsis box from “being a display box on the line” to “being an attachment” of the line box.
• Fixed unexpected overlapping selection with tab in right-to-left context.
• Fixed updating table rows during simplified layout.
• Fixed: improved balancing for border, padding, and empty block content.
• Extensions that request the unlimitedStorage permission no longer need to also request storage .
• Fixed browser.declarativeNetRequest namespace is now available when an extension has the declarativeNetRequestWithHostAccess permission.
• Fixed isUrlFilterCaseSensitive declarativeNetRequest rule condition to be false by default.
• Fixed tabs.onUpdated getting called on tabs that were already closed.
• Fixed background service worker failing to import scripts.
• Fixed content scripts not injecting into subframes when extension accesses the page after a navigation.
• Fixed CORS issue when doing fetch requests from a background service worker.
• Fixed declarativeNetRequest errors not appearing correctly in the extension’s pane of Safari Settings.
• Fixed display of extension cookie storage in Web Inspector. Now the extension name is shown instead of a UUID.
• Fixed declarativeNetRequest rules not loading when an extension is turned off and then on.
• Fixed result of getMatchedRules() to match other browsers.
• Fixed browser.webNavigation events firing for hosts where the extension did not have access.
• Removed Keyboard Shortcut conflict warnings for browser.commands when there are multiple commands without keyboard shortcuts assigned.
• Fixed overscroll-behavior: none to prevent overscroll when the page is too small to scroll.
• Fixed <svg:text> to not auto-wrap.
• Fixed preserveAspectRatio to stop accepting defer .
• Fixed SVG.currentScale to only set the page zoom for a standalone SVG.
• Fixed svgElement.setCurrentTime to restrict floats to finite values.
• Fixed applying changes to fill with currentColor to other colors via CSS.
• Fixed changes to the filter property getting ignored.
• Fixed CSS and SVG filters resulting in a low quality, pixelated image.
• Fixed focusability even when tab-to-links is enabled for <svg:a> .
• Fixed handling animation freezes when repeatDur is not a multiple of dur .
• Fixed making sure computed values for baseline-shift CSS property use px unit for lengths.
• Fixed not forcing display: table-cell , display: inline-table , display: table , and float: none on table cell elements when in quirks mode.
• Fixed removing the visual border when the table border attribute is removed.
• Fixed font-optical-sizing: auto having no effect in Safari 16.
• Fixed directionality of the <bdi> and <input> elements to align with HTML specifications.
• Fixed handling an invalid dir attribute to not affect directionality.
• Fixed the default oblique angle from 20deg to 14deg .
• Fixed the handling of <bdo> .
• Fixed the order of how @font-palette-values override-colors are applied.
• Fixed @keyframes rules using an inherit value to update the resolved value when the parent style changes.
• Fixed Animation.commitStyles() triggering a mutation even when the styles are unchanged.
• Fixed Animation.startTime and Animation.currentTime setters support for CSSNumberish values.
• Fixed baseline-shift animation.
• Fixed baselineShift inherited changes.
• Fixed commitStyles() failing to commit a relative line-height value.
• Fixed getKeyframes() serialization of CSS values for an onkeyframe sequence.
• Fixed rotate: x and transform: rotate(x) to yield the same behavior with SVGs.
• Fixed word-spacing to support animating between percentage and fixed values.
• Fixed accounting for non-inherited CSS variables getting interpolated for standard properties on the same element.
• Fixed accumulating and clamping filter values when blending with "none" .
• Fixed accumulation support for the filter property.
• Fixed additivity support for the filter property.
• Fixed animation of color list custom properties with iterationComposite .
• Fixed blend transform when iterationComposite is set to accumulate .
• Fixed blending to account for iterationComposite .
• Fixed Calculating computed keyframes for shorthand properties.
• Fixed composite animations to compute blended additive or accumulative keyframes for in-between keyframes.
• Fixed computing the keyTimes index correctly for discrete values animations.
• Fixed CSS animations participation in the cascade.
• Fixed custom properties to support interpolation with a single keyframe.
• Fixed filter values containing a url() should animate discretely.
• Fixed interpolating custom properties to take iterationComposite into account.
• Fixed jittering when animating a rotated image.
• Fixed keyframes to be recomputed if a custom property registration changes.
• Fixed keyframes to be recomputed if the CSS variable used is changed.
• Fixed keyframes to be recomputed when bolder or lighter is used on a font-weight property.
• Fixed keyframes to be recomputed when a parent element changes value for a custom property set to inherit .
• Fixed keyframes to be recomputed when a parent element changes value for a non-inherited property set to inherit .
• Fixed keyframes to be recomputed when the currentcolor value is used on a custom property.
• Fixed keyframes to be recomputed when the currentcolor value is used.
• Fixed opacity to use unclamped values for from and to keyframes with iterationComposite .
• Fixed running a transition on an inherited CSS variable getting reflected on a standard property using that variable as a value.
• Fixed seamlessly updating the playback rate of an animation.
• Fixed setting iterationComposite should invalidate the effect.
• Fixed setting the transition-property to none does not disassociate the CSS Transition from owning the element.
• Fixed the composite operation of implicit keyframes for CSS Animations to return "replace" .
• Fixed the timing model for updating animations and sending events.
• Fixed updating timing to invalidate the effect.
• Fixed -webkit-user-select: none allowing text to be copied to clipboard.
• Fixed contentEditable caret getting left aligned instead of centered when the :before pseudo-element is used.
• Fixed Cross-Origin-Embedder-Policy incorrectly blocking scripts on cache hit.
• Fixed CSSRule.type to not return values greater than 15.
• Fixed document.open() to abort all loads when the document is navigating.
• Fixed document.open() to remove the initial about:blank -ness of the document.
• Fixed Element.querySelectorAll not obeying element scope with ID.
• Fixed FileSystemSyncAccessHandle write operation to be quota protected.
• Fixed getBoundingClientRect() returning the wrong value for <tr> , <td> , and its descendants for a vertical table.
• Fixed HTMLOutputElement.htmlFor to make it settable.
• Fixed queryCommandValue("stylewithcss") to always return an empty string.
• Fixed StorageEvent.initStorageEvent() to align with HTML specifications.
• Fixed textContent leaving dir=auto content in the wrong direction.
• Fixed -webkit-user-select: initial content within -webkit-user-select: none should be copied
• Fixed WorkerGlobalScope.isSecureContext to be based on the owner’s top URL, not the owner’s URL.
• Fixed a bug where mousedown without mouseup in a frame prevents a click event in another frame.
• Fixed a sometimes incorrect location after exiting mouse hover.
• Fixed accepting image/jpg for compatibility.
• Fixed adding a non-breaking space, instead of a plain space, when it is inserted before an empty text node.
• Fixed behavior of nested click event on a label element with a checkbox.
• Fixed BroadcastChannel in a SharedWorker when hosted in a cross-origin iframe.
• Fixed calculation of direction for text form control elements with dir="auto" .
• Fixed canvas fallback content focusability computation.
• Fixed deleting a button element leaving the button’s style in a contenteditable element.
• Fixed disconnected <fieldset> elements sometimes incorrectly matching :valid or :invalid selectors.
• Fixed dragging the mouse over a -webkit-user-select: none node can begin selection in another node.
• Fixed ensuring nested workers get controlled if matching a service worker registration.
• Fixed errors caught and reported for importScripts() .
• Fixed escaping “&” in JavaScript URLs for innerHTML and outerHTML .
• Fixed EventSource to stop allowing trailing data when parsing a retry delay.
• Fixed Fetch Request object to keep its Blob URL alive.
• Fixed filled text on a canvas with a web font refreshing or disappearing.
• Fixed find on page failing to show results in PDFs.
• Fixed firing an error event when link preload fails synchronously.
• Fixed form submissions to cancel JavaScript URL navigations.
• Fixed handing the onerror content attribute on body and frameset elements.
• Fixed handling opaque origin Blob URLs.
• Fixed handling text documents to align to modern HTML specifications.
• Fixed handling the onerror content attribute on <body> and <frameset> elements.
• Fixed HTMLTemplateElement to have a shadowRootMode attribute.
• Fixed including alternate stylesheets in document.styleSheets .
• Fixed incorrect caret movement in some right-to-left contenteditable elements.
• Fixed incorrect color for videos loaded in a canvas.
• Fixed incorrect image srcset candidate chosen for <img> cloned from <template> .
• Fixed incorrectly ignored X-Frame-Options HTTP headers with an empty value.
• Fixed lazy loading images sometimes not loading.
• Fixed link elements to be able to fire more than one load or error event.
• Fixed loading Blob URLs with a fragment from opaque, unique origins.
• Fixed maintaining the original Content-Type header on a 303 HTTP redirect.
• Fixed module scripts to always decode using UTF-8.
• Fixed MouseEventInit to take movementX and movementY .
• Fixed not dispatching a progress event when reading an empty file or blob using the FileReader API.
• Fixed not replacing the current history item when navigating a cross-origin iframe to the same URL.
• Fixed overriding the mimetype for an XHR.
• Fixed parsing of negative age values in CORS prefetch responses.
• Fixed pasting of the first newline into text area.
• Fixed preventing selection for generated counters in ordered lists.
• Fixed Safari frequently using stale cached resources despite using Reload Page From Origin.
• Fixed scheduling a navigation to a Blob URL to keep the URL alive until the navigation occurs.
• Fixed sending Basic authentication via XHR using setRequestHeader() when there is an existing session.
• Fixed setting style="" to destroy the element’s inline style.
• Fixed setting the tabIndex of a non-focusable HTMLElement.
• Fixed system colors not respecting inherited color-scheme values.
• Fixed textarea placeholder text not disappearing when text is inserted without a user gesture.
• Fixed the event.keyIdentifier value for F10 and F11 keys.
• Fixed the click event to not get suppressed on textarea resize.
• Fixed the computed value for the transform property with SkewY .
• Fixed the initialization of color properties.
• Fixed timing of ResizeObserver and IntersectionObserver to match other browsers.
• Fixed toggling a details element when a summary element receives a click() .
• Fixed updating Text node children of an option element to not reset the selection of the select element.
• Fixed using NFC Security Key on iOS.
• Fixed using WebAuthn credentials registered on iOS 15 if iCloud Keychain is disabled.
• Fixed WebAuthn sending Attestation as None when requested as Direct.
• Fixed XHR aborting to align with standards specification
• Fixed XHR error events to return 0 for loaded and total.
• Fixed: Made all FileSystemSyncAccessHandle methods synchronous.
• Fixed: Removed the precision="float" attribute on <input type="range"> .
• Fixed video textures set to repeat.
• Fixed “Inspect Element” not highlighting the element.
• Fixed capturing async stack traces for queueMicrotask .
• Fixed clicking coalesced events in the timeline selecting the wrong event.
• Fixed event breakpoints to support case-insensitive and RegExp matching.
• Fixed slow search with a lot of files in the Open Resource dialog.
• Fixed sorting prefixed properties below non-prefixed properties in the Computed panel of the Elements Tab.
• Fixed the always empty Attributes section in the Node panel of the Elements Tab.
• Fixed the Computed Tab scrolling to the top when a <style> is added to the page.
• Fixed URL breakpoints to also pause when HTML attributes are set that trigger loads.
• Fixed “Get Element Rect” to not round to integer values.
• Fixed automation sessions terminating during navigation.
• Fixed click element failing on iPad when Stage Manager is disabled.
• Fixed HTTP GET requests with a body failing.
• Fixed the Shift modifier key not applying to typed text.

We love hearing from you. Send a tweet to @webkit to share your thoughts on Safari 16.4. Find us on Mastodon at @[email protected] and @[email protected] . If you run into any issues, we welcome your feedback on Safari UI, or your WebKit bug report about web technology or Web Inspector. Filing issues really does make a difference.

Download the latest Safari Technology Preview to stay at the forefront of the web platform and to use the latest Web Inspector features. You can also read the Safari 16.4 release notes .

• Español – América Latina
• Português – Brasil
• Tiếng Việt

Making Fullscreen Experiences

We have the ability to easily make immersive fullscreen websites and applications, but like anything on the web there are a couple of ways to do it. This is especially important now that more browsers are supporting an "installed web app" experience which launch fullscreen.

Getting your app or site fullscreen

There are several ways that a user or developer can get a web app fullscreen.

• Request the browser go fullscreen in response to a user gesture.
• Install the app to the home screen.
• Fake it: auto-hide the address bar.

Request the browser go fullscreen in response to a user gesture

Not all platforms are equal . iOS Safari doesn't have a fullscreen API, but we do on Chrome on Android, Firefox, and IE 11+. Most applications you build will use a combination of the JS API and the CSS selectors provided by the fullscreen specification. The main JS API's that you need to care about when building a fullscreen experience are:

• element.requestFullscreen() (currently prefixed in Chrome, Firefox, and IE) displays the element in fullscreen mode.
• document.exitFullscreen() (currently prefixed in Chrome, Firefox and IE. Firefox uses cancelFullScreen() instead) cancels fullscreen mode.
• document.fullscreenElement (currently prefixed in Chrome, Firefox, and IE) returns true if any of the elements are in fullscreen mode.

When your app is fullscreen you no longer have the browser's UI controls available to you. This changes the way that users interact with your experience. They don't have the standard navigation controls such as Forwards and Backwards; they don't have their escape hatch that is the Refresh button. It's important to cater for this scenario. You can use some CSS selectors to help you change the style and presentation of your site when the browser enters fullscreen mode.

The above example is a little contrived; I've hidden all the complexity around the use of vendor prefixes.

The actual code is a lot more complex. Mozilla has created a very useful script that you can use to toggle fullscreen. As you can see, the vendor prefix situation it is complex and cumbersome compared to the specified API. Even with the slightly simplified code below, it is still complex.

We web developers hate complexity. A nice high-level abstract API you can use is Sindre Sorhus' Screenfull.js module which unifies the two slightly different JS API's and vendor prefixes into one consistent API.

Fullscreen API Tips

Making the document fullscreen.

It is natural to think that you take the body element fullscreen, but if you are on a WebKit or Blink based rendering engine you will see it has an odd effect of shrinking the body width to the smallest possible size that will contain all the content. (Mozilla Gecko is fine.)

To fix this, use the document element instead of the body element:

Making a video element fullscreen

To make a video element fullscreen is exactly the same as making any other element fullscreen. You call the requestFullscreen method on the video element.

If your <video> element doesn't have the controls attribute defined, there's no way for the user to control the video once they are fullscreen. The recommended way to do this is to have a basic container that wraps the video and the controls that you want the user to see.

This gives you a lot more flexibility because you can combine the container object with the CSS pseudo selector (for example to hide the "goFS" button.)

Using these patterns, you can detect when fullscreen is running and adapt your user interface appropriately, for example:

• By providing a link back to the start page
• By Providing a mechanism to close dialogs or travel backwards

Launching a page fullscreen from home screen

Launching a fullscreen web page when the user navigates to it is not possible. Browser vendors are very aware that a fullscreen experience on every page load is a huge annoyance, therefore a user gesture is required to enter fullscreen. Vendors do allow users to "install" apps though, and the act of installing is a signal to the operating system that the user wants to launch as an app on the platform.

Across the major mobile platforms it is pretty easy to implement using either meta tags, or manifest files as follows.

Since the launch of the iPhone, users have been able to install Web Apps to the home screen and have them launch as full-screen web apps.

If content is set to yes, the web application runs in full-screen mode; otherwise, it does not. The default behavior is to use Safari to display web content. You can determine whether a webpage is displayed in full-screen mode using the window.navigator.standalone read-only Boolean JavaScript property. Apple

Chrome for Android

The Chrome team has recently implemented a feature that tells the browser to launch the page fullscreen when the user has added it to the home screen. It is similar to the iOS Safari model.

You can set up your web app to have an application shortcut icon added to a device's home screen, and have the app launch in full-screen "app mode" using Chrome for Android's "Add to Home screen" menu item. Google Chrome

A better option is to use the Web App Manifest.

Web App Manifest (Chrome, Opera, Firefox, Samsung)

The Manifest for Web applications is a simple JSON file that gives you, the developer, the ability to control how your app appears to the user in the areas that they would expect to see apps (for example the mobile home screen), direct what the user can launch and, more importantly, how they can launch it. In the future the manifest will give you even more control over your app, but right now we are just focusing on how your app can be launched. Specifically:

• Telling the browser about your manifest
• Describing how to launch

Once you have the manifest created and it is hosted on your site, all you need to do is add a link tag from all your pages that encompass your app, as follows:

Chrome has supported Manifests since version 38 for Android (October 2014) and it gives you the control over how your web app appears when it is installed to the home screen (via the short_name , name and icons properties) and how it should be launched when the user clicks on the launch icon (via start_url , display and orientation ).

An example manifest is shown below. It doesn't show everything that can be in a manifest.

This feature is entirely progressive and allows you create better, more integrated experiences for users of a browser that supports the feature.

When a user adds your site or app to the home screen, there is an intent by the user to treat it like an app. This means you should aim to direct the user to the functionality of your app rather than a product landing page. For example, if the user is required to sign-in to your app, then that is a good page to launch.

Utility apps

The majority of utility apps will benefit from this immediately. For those apps you'll likely want them launched standalone just alike every other app on a mobile platform. To tell an app to launch standalone, add this the Web App Manifest:

The majority of games will benefit from a manifest immediately. The vast majority of games will want to launch full-screen and forced a specific orientation.

If you are developing a vertical scroller or a game like Flappy Birds then you will most likely want your game to always be in portrait mode.

If on the other hand you are building a puzzler or a game like X-Com, then you will probably want the game to always use the landscape orientation.

News sites in most cases are pure content-based experiences. Most developers naturally wouldn't think of adding a manifest to a news site. The manifest will let you define what to launch (the front page of your news site) and how to launch it (fullscreen or as a normal browser tab).

The choice is up to you and how you think your users will like to access your experience. If you want your site to have all the browser chrome that you would expect a site to have, you can set the display to browser .

If you want your news site to feel like the majority of news-centric apps treat their experiences as apps and remove all web-like chrome from the UI, you can do this by setting display to standalone .

Fake it: auto-hide the address bar

You can "fake fullscreen" by auto-hiding the address bar as follows:

This is a pretty simple method, the page loads and the browser bar is told to get out of the way. Unfortunately it is not standardized and not well supported. You also have to work around a bunch of quirks.

For example browsers often restore the position on the page when the user navigates back to it. Using window.scrollTo overrides this, which annoys the user. To work around this you have to store the last position in localStorage, and deal with the edge cases (for example, if the user has the page open in multiple windows).

UX guidelines

When you are building a site that takes advantage of full screen there are a number of potential user experience changes that you need to be aware of to be able to build a service your users will love.

Don't rely on navigation controls

iOS does not have a hardware back button or refresh gesture. Therefore you must ensure that users can navigate throughout the app without getting locked in.

You can detect if you are running in a fullscreen mode or an installed mode easily on all the major platforms.

On iOS you can use the navigator.standalone boolean to see if the user has launched from the home screen or not.

Web App Manifest (Chrome, Opera, Samsung)

When launching as an installed app, Chrome is not running in true fullscreen experience so document.fullscreenElement returns null and the CSS selectors don't work.

When the user requests fullscreen via a gesture on your site, the standard fullscreen API's are available including the CSS pseudo selector that lets you adapt your UI to react to the fullscreen state like the following

If the users launches your site from the home screen the display-mode media query will be set to what was defined in the Web App Manifest. In the case of pure fullscreen it will be:

If the user launches the application in standalone mode, the display-mode media query will be standalone :

When the user requests fullscreen via your site or the user launches the app in fullscreen mode all the standard fullscreen API's are available, including the CSS pseudo selector, which lets you adapt your UI to react to the fullscreen state like the following:

Internet Explorer

In IE the CSS pseudo class lacks a hyphen, but otherwise works similarly to Chrome and Firefox.

Specification

The spelling in the specification matches the syntax used by IE.

Keep the user in the fullscreen experience

The fullscreen API can be a little finicky sometimes. Browser vendors don't want to lock users in a fullscreen page so they have developed mechanisms to break out of fullscreen as soon as they possibly can. This means you can't build a fullscreen website that spans multiple pages because:

• Changing the URL programmatically by using window.location = "http://example.com" breaks out of fullscreen.
• A user clicking on an external link inside your page will exit fullscreen.
• Changing the URL via the navigator.pushState API will also break out of the fullscreen experience.

You have two options if you want to keep the user in a fullscreen experience:

• Use the installable web app mechanisms to go fullscreen.
• Manage your UI and app state using the # fragment.

By using the #syntax to update the url (window.location = "#somestate"), and listening to the window.onhashchange event you can use the browser's own history stack to manage changes in the application state, allow the user to use their hardware back buttons, or offer a simple programmatic back button experience by using the history API as follows:

Let the user choose when to go fullscreen

There is nothing more annoying to the user than a website doing something unexpected. When a user navigates to your site don't try and trick them into fullscreen.

Don't intercept the first touch event and call requestFullscreen() .

• It is annoying.
• Browsers may decided to prompt the user at some point in the future about allowing the app to take up the fullscreen.

If you want to launch apps fullscreen think about using the install experiences for each platform.

Don't spam the user to install your app to a home screen

If you plan on offering a fullscreen experience via the installed app mechanisms be considerate to the user.

• Be discreet. Use a banner or footer to let them know they can install the app.
• If they dismiss the prompt, don't show it again.
• On a users first visit they are unlikely to want to install the app unless they are happy with your service. Consider prompting them to install after a positive interaction on your site.
• If a user visits your site regularly and they don't install the app, they are unlikely to install your app in the future. Don't keep spamming them.

While we don't have a fully standardized and implemented API, using some of the guidance presented in this article you can easily build experiences that take advantage of the user's entire screen, irrespective of the client.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2016-10-01 UTC.

• Skip to main content
• Skip to search
• Skip to select language
• Sign up for free

Guide to the Fullscreen API

Limited availability.

This feature is not Baseline because it does not work in some of the most widely-used browsers.

• See full compatibility
• Report feedback

This article demonstrates how to use the Fullscreen API to place a given element into fullscreen mode, as well as how to detect when the browser enters or exits fullscreen mode.

Activating fullscreen mode

Given an element that you'd like to present in fullscreen mode (such as a <video> , for example), you can present it in fullscreen mode by calling its requestFullscreen() method.

Let's consider this <video> element:

We can put that video into fullscreen mode as follows:

This code checks for the existence of the requestFullscreen() method before calling it.

Notification

When fullscreen mode is successfully engaged, the document which contains the element receives a fullscreenchange event. When fullscreen mode is exited, the document again receives a fullscreenchange event. Note that the fullscreenchange event doesn't provide any information itself as to whether the document is entering or exiting fullscreen mode, but if the document has a non null fullscreenElement , you know you're in fullscreen mode.

When a fullscreen request fails

It's not guaranteed that you'll be able to switch into fullscreen mode. For example, <iframe> elements have the allowfullscreen attribute in order to opt-in to allowing their content to be displayed in fullscreen mode. In addition, certain kinds of content, such as windowed plug-ins, cannot be presented in fullscreen mode. Attempting to put an element which can't be displayed in fullscreen mode (or the parent or descendant of such an element) won't work. Instead, the element which requested fullscreen will receive a mozfullscreenerror event. When a fullscreen request fails, Firefox will log an error message to the Web Console explaining why the request failed. In Chrome and newer versions of Opera however, no such warning is generated.

Note: Fullscreen requests need to be called from within an event handler or otherwise they will be denied.

Getting out of full screen mode

The user always has the ability to exit fullscreen mode of their own accord; see Things your users want to know . You can also do so programmatically by calling the Document.exitFullscreen() method.

Other information

The Document provides some additional information that can be useful when developing fullscreen web applications:

The fullscreenElement property tells you the Element that's currently being displayed fullscreen. If this is non-null, the document (or shadow DOM) is in fullscreen mode. If this is null, the document (or shadow DOM) is not in fullscreen mode.

The fullscreenEnabled property tells you whether or not the document is currently in a state that would allow fullscreen mode to be requested.

Viewport scaling in mobile browsers

Some mobile browsers while in fullscreen mode ignore viewport meta-tag settings and block user scaling; for example: a "pinch to zoom" gesture may not work on a page presented in fullscreen mode — even if, when not in fullscreen mode, the page can be scaled using pinch to zoom.

Things your users want to know

You'll want to be sure to let your users know that they can press the Esc key (or F11 ) to exit fullscreen mode.

In addition, navigating to another page, changing tabs, or switching to another application (using, for example, Alt - Tab ) while in fullscreen mode exits fullscreen mode as well.

In this example, a video is presented in a web page. Pressing the Return or Enter key lets the user toggle between windowed and fullscreen presentation of the video.

View Live Examples

Watching for the Enter key

When the page is loaded, this code is run to set up an event listener to watch for the Enter key.

Toggling fullscreen mode

This code is called when the user hits the Enter key, as seen above.

This starts by looking at the value of the fullscreenElement attribute on the document . If it's null , the document is currently in windowed mode, so we need to switch to fullscreen mode. Switching to fullscreen mode is done by calling element.requestFullscreen() .

If fullscreen mode is already active ( fullscreenElement is non- null ), we call document.exitFullscreen() .

Specifications

Browser compatibility, api.document.fullscreenenabled.

BCD tables only load in the browser with JavaScript enabled. Enable JavaScript to view data.

api.Document.fullscreen

• Using fullscreen mode
• Element.requestFullscreen()
• Document.exitFullscreen()
• Document.fullscreen
• Document.fullscreenElement
• :fullscreen , ::backdrop
• allowfullscreen

Can't find "Fullscreen API" in iOS Safari Experimental Settings

I can't find "Fullscreen API" toggle in MobileSafari (iOS 12.2 - Release).

• Safari Developer Tools

Fullscreen API

API for allowing content (like a video or canvas element) to take up the entire screen.

• 4 - 14 : Not supported
• 15 - 19 : Partial support
• 20 - 70 : Partial support
• 71 - 123 : Supported
• 124 : Supported
• 125 - 127 : Supported
• 12 - 18 : Partial support
• 79 - 123 : Supported
• 3.1 - 5 : Not supported
• 5.1 : Partial support
• 6 - 15.3 : Partial support
• 15.4 - 16.3 : Partial support
• 16.4 - 17.3 : Supported
• 17.4 : Supported
• 17.5 - TP : Supported
• 2 - 9 : Not supported
• 10 - 46 : Partial support
• 47 - 63 : Partial support
• 64 - 124 : Supported
• 125 : Supported
• 126 - 128 : Supported
• 9 - 12 : Not supported
• 12.1 : Supported
• 15 - 63 : Partial support
• 64 - 108 : Supported
• 109 : Supported
• 5.5 - 10 : Not supported
• 11 : Partial support

Chrome for Android

Safari on ios.

• 3.2 - 11.4 : Not supported
• 12 - 17.3 : Partial support
• 17.4 : Partial support
• 17.5 : Partial support

Samsung Internet

• 4 - 9.2 : Partial support
• 10.1 - 23 : Supported
• 24 : Supported
• all : Not supported

Opera Mobile

• 10 - 12.1 : Not supported
• 80 : Supported

UC Browser for Android

• 15.5 : Supported

Android Browser

• 2.1 - 4.4.4 : Not supported
• 124 : Not supported

Firefox for Android

• 14.9 : Supported

Baidu Browser

• 13.52 : Supported

KaiOS Browser

• 2.5 : Supported
• 3 : Supported

Advisory boards aren’t only for executives. Join the LogRocket Content Advisory Board today →

• Product Management
• Solve User-Reported Issues
• Find Issues Faster
• Optimize Conversion and Adoption
• Start Monitoring for Free

Experimenting with the FullScreen API

The FullScreen API allows you to make an element on your page have a full-screen view. Normally, you see this in use with different graphical or media resources — for example, videos or images — but you can actually make any element on your page have a full-screen view.

The FullScreen API is currently well supported in Chrome, Firefox, Opera, and Edge. There is supposed to be partial support in Safari using vendor prefixes , but I have not attempted to make that work.

If you need cross-platform support for the FullScreen API, there are a number of them out there, such as fscreen or screenfull . There is also a React Hooks implementation and a higher-order component that makes children into full-screenable areas .

But this article will solely focus on using the specified FullScreen API, so you should be aware that things are only going to work in the listed browsers.

Getting started

To enable a full-screen view on a user’s browser, you will first need to ask for permission to do so with the Element.requestFullScreen function . This is not the same as requesting access to location data — the browser determines if the request is accepted basically by determining whether the user has performed a specific action to approve or deny full-screen access, like clicking an Allow button.

If a user wants to exit the full-screen view, they can use all the ways they normally use to exit a full-screen window, as well as pressing the escape key, assuming they are in an environment that provides them with one.

Now, let’s move on to some examples.

The basic example: A full-screen section

The FullScreen API is most commonly used to embiggen images and videos, but each of them has their own little issues to consider, so I will start us off with something simpler: an HTML5 section with a button to turn the section into a full-screen view.

See the Pen full screen section by Bryan Rasmussen ( @bryanrasmussen ) on CodePen .

My button styling in the example is reused from the LogRocket CSS Reference Guide to button styling.

The page looks sort of like the following:

When you click the Fullscreen button, it toggles the full-screen view for the section with the text “More Info Available in Full Screen Mode …”

The full screen looks like this (the white border is still there, it’s just at the edge of the screen).

The text is different here because we have used the :fullscreen pseudo selector to switch the H2 text that reads “More Info Available in Full Screen Mode …” to display:none with another H2 text that reads “This is the promised full screen mode!” from display:none to display:block .

Take a look at this in the below code snippet:

The thing to note here is that the :fullscreen pseudo selector has to be applied on the element that has been switched to full-screen mode; in this case, it’s the section with the class fullscreenEnabled .

This is used for styling the rest of the content on the page that is not in the :fullscreenEnabled element. Now, you’re probably asking yourself, what? And why?

One potential use is to put a background color on the backdrop, which can then affect the full-screen display. MDN has an example of this with a fullscreen video element .

Another more important usage would be meeting accessibility requirements for the backdrop; however, this does not currently work. We’ll discuss this later in this document, in the section on using the FullScreen API with images .

Expanding the basic example: A full-screen modal

The :fullscreen element is very similar to dialogs and modal windows in that it separates content from the rest of the page to place emphasis on it.

Naturally, it would be logical to make a modal-like use of the technique, and to do so, I will be reusing some of the code from the Pure CSS Lightbox from MDN for the Close button.

First, I will change some of the logic around click handlers, as I will want both a button to open the modal, and a button inside the modal to close it.

Take a look at the code below:

See the Pen full screen Modal by Bryan Rasmussen ( @bryanrasmussen ) on CodePen .

Our changes are mainly small ones, to add the makeFullScreen function to multiple elements (since it closes the :fullscreen element, if there is one, we can use it for our modal closer as well), and to add a keydown handler for the event key, like this:

Then we’ll add some structure in the modal area to enable nicer styling of our modal, including some focus styles for the modal opening button and the close button.

This is what it looks like with the modal closed:

And this is what it looks like when the modal is shown:

For accessibility purposes, it was tested with VoiceOver and keyboard navigation in Firefox. Obviously, as this is a proof of concept, and written inside of CodePen’s nested frames, there may be accessibility issues on other browser/screen reader combinations.

The most common FullScreen uses

As we mentioned before, there are basically two common uses for the :fullscreen element that people focus on, these being the ability to give either a video or an image a full-screen view.

I’ve decided not to make a full-screen video example, as to make a pleasing one would require too many parts for me to do it justice as a minor part of this article. Instead, I will focus on the image, as I believe we can make some interesting additions to it.

Over 200k developers use LogRocket to create better digital experiences

Using the FullScreen API with images

In this example, I have some images laid out in a grid. In order for the images to be worth looking at in a full-screen view, I’ve used some examples from Little Nemo downloaded from the Internet Archive.

Here is the example grid:

See the Pen Images Grid by Bryan Rasmussen ( @bryanrasmussen ) on CodePen .

The first line of images looks something like the following:

We’re doing a similar thing with our makeFullScreen function as we did before: each image is inside a span with a button role for accessibility and the class fullscreenEnabled . We add click and keydown event handlers to our span s and make the span itself full-screen.

The reason for this is in our CSS for the full-screen span and its child image, which allows us to scroll through the image in all its full-screen glory.

This is of course because if the image is full-screen, it will be shrunk to fit into whatever screen you are viewing it on (assuming that the screen area is smaller than the image) whereas if the element wrapping the image is full screen we can allow it overflow and then the user can scroll through the image as they wish.

For accessibility purposes, rather than putting an aria-label attribute on each span and telling the user they can click to view it in full-screen mode, which may seem overly verbose, we added a notice above in a paragraph.

However, this is not the only accessibility problem that you might encounter with this solution. If you are using a screen reader, how does it handle the parts of the page that are not shown in the full screen view, or, in other words, remain in the backdrop ?

In the FullScreen API specification , it says the following about the backdrop:

“The ::backdrop pseudo-element can be used to create a backdrop that hides the underlying document for an element in a top layer (such as an element that is displayed fullscreen).”

This implies that you should be able to do the following:

But that does not work.

In my experience using Chrome, you cannot access the backdrop content with your screen reader. You can get to the browser address bar, but you have to really try to do that.

In Firefox, however, you will end up being able to read all the content that is not in the full screen when you make an element full screen. I have entered a bug about this , but cannot at this time say what the response will be.

Currently, if you make an element full-screen, the solution for accessibility would probably be to set all elements outside of the :fullscreen element to have an aria-hidden element set to true . Hopefully, Firefox will fix this soon.

I have not tested the ::backdrop pseudo selector behavior or the accessibility of a :fullscreen element on other browsers, so be wary.

Full-screen images with SVGs

This starts out looking similar to our last example with the image grid, where you click an image and it opens in full-screen mode. In fact, aside from seeing four items in the grid now, you might think it was the same example. That is because I am using the SVG image element to embed the Little Nemo jpegs inside of the SVG.

The difference looks something like the below. There will be extra code in the final SVG, but this shows us the same image.

More great articles from LogRocket:

• Don't miss a moment with The Replay , a curated newsletter from LogRocket
• Learn how LogRocket's Galileo cuts through the noise to proactively resolve issues in your app
• Use React's useEffect to optimize your application's performance
• Switch between multiple versions of Node
• Discover how to use the React children prop with TypeScript
• Explore creating a custom mouse cursor with CSS
• Advisory boards aren’t just for executives. Join LogRocket’s Content Advisory Board. You’ll help inform the type of content we create and get access to exclusive meetups, social accreditation, and swag.

When you’re playing around with images embedded in SVGs, you have to consider what the actual sizes of those images are (generally, that is, if you want a good visual experience). This is because SVG has a different way of handling images that don’t fit in their container than HTML does.

When I first tried making this, it threw me for a loop because I tried to just guess at the dimensions of the image instead of calculating it, and was very far off. This created a bunch of leading blank space at the top of the SVG because the SVG parser tried to resize the image so the aspect ratios were maintained.

This led me to waste an hour or two, as I was not in the right state of mind to see where I was mistaken — so, it’s a good time to remind ourselves to figure out our dimensions with SVGs first.

The sizes of the images we embedded inside the SVG are width 1738px and height 2378px, so picking a size combination of the same aspect ratio (dropping the decimal places, of course) I chose width 250px and height 345px. So, to make everything look nice in the SVG, we can do:

Then we set the grid-template-columns value to follow our image width:

And, of course, the grid-item-width variable will be used in the grid-template-columns property.

Then, when we enable full-screen mode, we can simply do:

This is because we can change the values of our variables in full-screen mode and have them be inherited the same way we might in any other class or virtual selector.

This can be seen below.

See the Pen Images Grid With SVG by Bryan Rasmussen ( @bryanrasmussen ) on CodePen .

The main benefit of the SVG in the context of the FullScreen API would be that you could then have animations and other effects inside the SVG (at a higher z-index than the image, of course) that would become visible and activated when the .fullscreenEnabled div was actually in the full-screen view.

The Fullscreen API is pretty simple, but with some creativity, you can have interesting results. We’ve seen how we can toggle the full screen for various types of elements, providing a large image view and a full-screen modal. Obviously, these examples could be extended to make full screen slideshows or similar effects.

However, there are definitely drawbacks with the Fullscreen API as currently implemented where accessibility is concerned , and one should take this into account when building a solution using it.

Is your frontend hogging your users' CPU?

As web frontends get increasingly complex, resource-greedy features demand more and more from the browser. If you’re interested in monitoring and tracking client-side CPU usage, memory usage, and more for all of your users in production, try LogRocket .

LogRocket is like a DVR for web and mobile apps, recording everything that happens in your web app, mobile app, or website. Instead of guessing why problems happen, you can aggregate and report on key frontend performance metrics, replay user sessions along with application state, log network requests, and automatically surface all errors.

Modernize how you debug web and mobile apps — start monitoring for free .

Share this:

• Click to share on Twitter (Opens in new window)
• Click to share on Reddit (Opens in new window)
• Click to share on LinkedIn (Opens in new window)
• Click to share on Facebook (Opens in new window)

Stop guessing about your digital experience with LogRocket

Recent posts:.

Using React Shepherd to build a site tour

React Shepherd stands out as a site tour library due to its elegant UI and out-of-the-box, easy-to-use React Context implementation.

A guide to cookies in Next.js

Cookies are crucial to web development. This article will explore how to handle cookies in your Next.js applications.

Handling dates in JavaScript with Tempo

Use the Tempo library to format dates and times in JavaScript while accounting for time zones, daylight saying time, and date internationalization.

A guide to Deno.cron

This guide explores how to use the cron package in Deno, `Deno.cron`, to handle scheduling tasks with specific commands.

Leave a Reply Cancel reply

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

How to use The native iOS Video Player for Ipad os 13?

How to use The native iOS Video Player for Ipad os 13? Before it worked with fullscreen api off, but now not

iPad Pro 10.5-inch, Wi-Fi

Posted on Sep 25, 2019 5:34 AM

Posted on Oct 9, 2019 8:33 PM

No, the OP is talking about videos on web pages in Safari. There used to be an option in Safari settings to “Disable Fullscreen API” so that websites would use the native iOS video player instead of any custom video players. That option has been finally removed in iOS 13. Now videos on websites play using custom video players which means that they are incredibly buggy, hard to navigate, and constantly have ads and pop ups. Custom video players cause a pretty terrible video experience and it is a huge negative regression for Apple to force users to use custom video players when the native iOS player was so much better.

I don’t have a fix for this but I hope someone does.

Similar questions

• How i will download video player in 5.1.1 vrsion of i pad How i will downlaod video player in 5.1.1 version of ipad 575 2
• Make VLC default video player on iPad Running iOS 15.1 on iPad Mini. I keep trying, but do not understand how to use VLC player to play movies on my iPad. Not just use it, but make it the default player. The existing default player is very unsatisfactory. Thanks! 5188 1
• I need Flash Player 8, what app do I download on my mini iPad? What app do I download on my mini iPad: I need flash player 8 to take a course [Re-Titled by Moderator] 881 7

Loading page content

Page content loaded

Oct 9, 2019 8:33 PM in response to QuickPost

Oct 23, 2019 4:38 PM in response to Gi T

Potential solution to this issue: turn off Request Desktop Website in Settings —> Safari and force restart Safari.

Oct 16, 2019 8:59 PM in response to andriy258

Using safari in ios 13 on my ipad no longer allows me to use the native video player. This caused issues when streaming over to my apple tv via screen mirroring. I could no longer expand to full screen and watch on my whole tv screen. Tv screen would try to match the tablet aspect ratio causing smaller picture and lots of void on the edges.

solution: stream via iPhone or use Google Chrome for ipad. Both still use the native video player while in full screen and allow full screen while mirroring via apple tv.

Nov 22, 2019 5:32 PM in response to eashc

This doesn’t help as most sites have their own way of how its displayed for this device/resolution, which for the most part over rides whatever safari’s default/requested is. PLEASE someone help us get back to a position where we could turn off the use the full screen API option, or somehow get the same result...

Nov 22, 2019 5:45 PM in response to Gi T

Thank you so much for being the only person to provide a real solution to this major disappointment!! Feels like apple’s support consists of people like “....errrrr umm cycle the power maybe..., if not you gotta take your device to the store and do a factory reset”.....like they hire people off the street in 3rd world countries and pay them in peanuts... It’s been a over 2 MONTHS guys!! NO SOLUTIONS??!

Dec 13, 2019 4:57 PM in response to eashc

iPad Pro 13.2.3 I just turned it off as suggested and reloaded web page and it worked....thank you

new update just released think I’ll leave it last two have been a disaster seems Apple have their head in the sand !!

Dec 19, 2019 1:51 PM in response to Vsmisli

Here is the answer: Because of IPad OS and apple’s push to make ipad feel more like a desktop environment.

same here... works like before on iphone with os13.3. No native video player on my ipad running 13.3.

https://thevoice.bg/stream

Sep 25, 2019 7:42 AM in response to andriy258

Are you referring to playing YouTube videos in Safari in Apple's system video player?

Sep 25, 2019 6:19 PM in response to QuickPost

Yes, I have the same issue

Sep 27, 2019 12:59 PM in response to QuickPost

No, i mean other videos in other resources

Sep 27, 2019 1:04 PM in response to andriy258

Do you mean you wish to use iPad’s system video player in 3rd party applications? You will not be able to unless the application explicitly supports the system video player.

Nov 26, 2019 4:35 AM in response to andriy258

This problem still exists

Dec 13, 2019 8:49 PM in response to Inbits

May I know your settings that make the native iOS video player works?

Dec 14, 2019 3:25 PM in response to mh290

Settings- safari and turn off “request desktop website “

Dec 19, 2019 1:15 PM in response to andriy258

Navigation Menu

Search code, repositories, users, issues, pull requests..., provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement . We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iOS Safari fullscreen API support #6928

lukewarlow commented Dec 23, 2023

jensimmons commented Dec 26, 2023

• 👍 2 reactions

Sorry, something went wrong.

Successfully merging a pull request may close this issue.