Element.innerHTML
Content-Security-Policy: require-trusted-types-for 'script'; report-uri //my-csp-endpoint.example
Cross-Origin-Embedder-Policy
Cross-Origin-Opener-Policy
Performance.measureMemory()
document.domain
Scheduler.postTask()
user-blocking
user-visible
background
TaskController
MediaStreamTrack
RTCPeerConnection
<mark>
-webkit-appearance
auto
appearance
<image>
<video>
<canvas>
prefers-color-scheme
display
inline-grid
grid
inline-flex
flex
<button>
module
font-display
optional
font-display: optional
IDBDatabase.transaction()
durability
"default"
"strict"
"relaxed"
IDBTransaction.durability
const iDBTransaction = database.transaction( [ "storeName" ], "readwrite", { durability: "relaxed" } );
<input>
type
time
@supports
@supports selector(::before) { div { background: green }; }
canTrickleIceCandidates
RTCRtpSender.setParameters()
RTCRtpEncodingParameters.maxFramerate
maxFramerate
RTCRtpSendParameters
degradationPreference
"maintain-framerate"
"maintain-resolution"
"balanced"
fractionalSecondDigits
Intl.DateTimeFormat
DateTimeFormat
'allow-downloads'
We previously paused upcoming releases for Chrome and Chrome OS. Today we’re sharing an update as we’re now resuming releases with an adjusted schedule:
We continue to closely monitor that Chrome and Chrome OS are stable, secure, and work reliably. We’ll keep everyone informed of any changes on our schedule on our release blog and will share additional details on the schedule in the Chromium Developers group, as needed. You can also check our schedule page for specific dates for each milestone at any time.
Thanks everyone for the help and patience during this time.
Posted by the Chrome Release Team
Due to adjusted work schedules at this time, we are pausing upcoming Chrome and Chrome OS releases. Our primary objectives are to ensure Chrome continues to be stable, secure, and work reliably for anyone who depends on them. We’ll continue to prioritize any updates related to security, which will be included in Chrome 80.