Rebase to master #1
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Add async iterators. https://www.chromestatus.com/features/5727385018171392 * Async iterations are implemented in Fx57 (bug 1352312)
…i-invalid pseudo-classes (mdn#2829) * Add compat data for :-moz-ui-valid pseudo-class. * Add compat data for :-moz-ui-invalid pseudo-class. * Add compat data for :-moz-submit-invalid pseudo-class.
* Update scroll-snap-type.json https://caniuse.com/#feat=css-snappoints * add scroll-snap-type support in Android and Opera
Adds compatibility information for the load() method on HTMLMediaElement.
…dn#2874) * Add compat data for CSS -webkit-border-before * Add compat data for CSS -webkit-box-reflect * Add compat data for CSS -webkit-mask-composite * Add compat data for CSS -webkit- selectors: autofill, inner/outer-spin-button * Add compat data for CSS -moz-color-swatch * Add compat data for CSS -webkit-file-upload-button
We do not support allow-top-navigation-by-user-activation https://bugzilla.mozilla.org/show_bug.cgi?id=1359867 We've supported allow-presentation since Firefox 50 https://bugzilla.mozilla.org/show_bug.cgi?id=1268758
* lint: make output less verbose * Uses ora to display a spinner with succeed/fail feedback. * Removes `console.log` calls for succeeding checks. * lint: make ora use stdout + stderr * lint: use console.warn for error summary
* Feature-Policy: change animations to layout-animations * Remove Chrome/Opera info for layout-animations
Adds inputmode to the global attributes list. Currently supported only by Chrome that I can find. This comes from looking at Chrome source, caniuse data, and this Chrome bug: https://bugs.chromium.org/p/chromium/issues/detail?id=244688
* Add options parameter to Element.requestFullscreen() This adds information about the options parameter to requestFullscreen's entry. Supported on Chrome 71; Firefox doesn't support it yet.. Other browsers are unknown. * requestFullScreen() options supported in Firefox 64 The `requestFullScreen()` method's `options` parameter is added in Firefox 64, actually. * "supports" isn't needed in identifiers and descriptions
This includes updates for the Fullscreen API, including: * Adding missing data for "returns_a_promise" on Document.exitFullScreen() * Changing some incorrect "experimental" values to false * Adding missing onfullscreenchange and onfullscreenerror to Element.json * Adding new FullscreenOptions dictionary The version number updates were all done previously by @ExE-Boss. I've submitted a previous PR to add the options parameter to Document.requestFullScreen(). Together all of this work completes updates for the Fullscreen API at this time.
* Origin Header: Firefox sent it for POST requests since v59 * Update Fx59 support info
…#2994) * updating sandbox sub-items to hopefully make them easier to read * updating sandbox attribute values data according to conversation with wbamberg and fscholz
* fullscreen api on IE11: https://msdn.microsoft.com/en-us/ie/dn312066\(v\=vs.94\), https://msdn.microsoft.com/en-us/ie/dn312067\(v\=vs.94\) * fullscreen api on IE11, fix schema error
* Bug 1496617: Unprefix `image-rendering: crisp-edges` # External links: - https://bugzil.la/1496617 * Address review comments
* added information for update properties highlighted. * added information for highlight method. * Use strings * Added the compat data for highlightInfo as it was in PR #mdn#2987
ExE-Boss
pushed a commit
that referenced
this pull request
May 6, 2019
* Add browser engine to schema * Add engines for IE (Trident) and Edge (EdgeHTML) * Add Chrome WebKit data * Add Chrome Blink data * Add engine for Chrome Android * Update Opera versions * Add release notes and date for Opera 60 * Add Opera (Presto & Blink) data * Add Opera Android (Presto & Blink) data * Add Safari (WebKit) data * Add Safari iOS (WebKit) data * Update current Safari iOS version * Add Firefox (Gecko) data * Add Firefox Android (Gecko) data * Add Webview (Blink) data * Add Node.js (V8) data * Add Samsung Internet (Blink) data * Add release date for Samsung Internet 8.2 * Add Samsung Internet 9.2 * 8.2 is retired * 7.4 is retired * Add 8.0 and 9.0 * Add engine version for Samsung Internet 8.0 * Add Samsung Internet 9.0/9.2 engines based upon manual testing * Replace 4.4 and 4.4.3 with 30 and 33, add 36 * Update data for 4.4.3 -> 33 * Update data for 4.4 -> 30 * Fix remaining files * Fix version numbers set to 37 * Add WebView data for non-Chromium versions * Revert version numbers of WebView 4.4 and 4.4.3 * Fix version numbers in all files * Add engines to WebView 4.4, 4.4.3, and 36 * Add documentation regarding engine fields * Add enum validation of known engines * Remove WebView 36 * Update files to remove WebView 36 * Fix typos via @ExE-Boss' suggestion Co-Authored-By: vinyldarkscratch <[email protected]> * Add engines to browsers in TypeScript (#1) * Revert "Add engines to browsers in TypeScript (#1)" This reverts commit ac1fe4c. * Remove Opera and WebView as engines * Add browser engine data to TypeScript * Add engines for Android Webview 2.x/3.x/4.0/4.1/4.2 Information Source: https://developers.whatismybrowser.com/useragents/explore/software_name/android-browser * Add Safari iOS 1.0 engine version * Update engines based upon user agent strings * Fix Safari iOS engine versions * Fix syntax error during merge * Add engine to Node.js 12.0.0 * Update Internet Explorer engines * Remove engines from IE 1-6 for now
ExE-Boss
pushed a commit
that referenced
this pull request
May 26, 2021
* Added in manifest info - Used https://caniuse.com/?search=manifest * Fixes for samsung * Corrected theme_color data from https://chromestatus.com/features/5709006190411776 * Add scope data From chromium/chromium@c099a89 * Update display.json chromium/chromium@f607208 * Update start_url.json chromium/chromium@c267d1e * Update orientation.json chromium/chromium@96297a7 * Update name.json chromium/chromium@161ea5d * Update short_name.json chromium/chromium@161ea5d * Update icons.json chromium/chromium@c00b78f * Remove other data (#1) * Update display.json * Update icons.json * Update name.json * Update short_name.json * Update theme_color.json * Update name.json https://medium.com/@firt/pwas-are-coming-to-ios-11-3-cupertino-we-have-a-problem-2ff49fd7d6ea WebKit/WebKit@ca1e8ed * Update description.json https://medium.com/@firt/pwas-are-coming-to-ios-11-3-cupertino-we-have-a-problem-2ff49fd7d6ea WebKit/WebKit@ca1e8ed * Update scope.json
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.