GoogleChrome /samples
A repo containing samples tied to new functionality in each release of Google Chrome.
★ 5,890⑂ 2,386👁 334⑃ 865● 255▤ 0
More from this author
+1
Daily
5,890
stars
2,386
forks
334
watchers
865
prs
255
issues
0
releases
README
Google Chrome Samples === Samples tied to new functionality in Google Chrome and general samples. Some samples correspond to an entry in https://www.chromestatus.com/features, and using that interface is currently the best way to browse. Contributing a sample for a ChromeStatus feature === Please use SAMPLE_STARTING_POINT as a starting point. While it's possible to simply create a standard set of HTML/JS/CSS files within the new directory, you can take advantage of the Jekyll-based templating system to handle most of the boilerplate. Any files that start with a front matter block will be templated, and any other files will be served verbatim. If you're still unsure, two canonical samples that use templates are: - image-rendering-pixelated - report-validity Follow the Using Jekyll with Pages guide to mimic the production Jekyll environment during local development. Once complete, please file a pull request against the gh-pages branch with your sample. It's ideal when filing a pull request @-mention the relevant engineer who worked on adding the feature into Chrome, to solicit their feedback and ensure that the sample properly describes the functionality. The email address of the engineer who worked on a given feature can be found in the corresponding https://www.chromestatus.com/features entry. If you're unsure of the GitHub username corresponding to the engineer, an alternative is to email them a link to the pull request and ask for feedback directly. Contributing a general sample === Just add all the resources for your sample in a dedicated folder. One example is mkbitmap, which is referenced and embedded in the article Compiling mkbitmap to WebAssembly. Style / Linting / CI === The samples ideally should follow the Google JavaScript Style Guide, and for samples for a ChromeStatus feature that's enforced via ESLint, using the eslint-config-google base configuration, with a few overrides as needed. Linting can be performed via npm run lint (make sure to npm install first). Various IDEs offer real-time ESLint integration, and using those integrations that can help avoid errors before anything gets checked in.
Top issues
#685Is there a working autopictureinpicture sample?30 comments · 2020-05-09#627intrinsicsize conflicting with CSS object-fit20 comments · 2019-01-18#778Presentation API raise crash Chrome with Chrome version 10517 comments · 2022-09-06#384Native app install banner not showing15 comments · 2016-07-06#622how to get MAC Address from paired Bluetooth devices using google chrome API13 comments · 2018-12-16#487Add design to demos.10 comments · 2017-03-03#796No next/previous slide controls on Android for Media Session API9 comments · 2023-03-14#794Bluetooth LE watchAdvertisements doesn't work on Linux Ubuntu + Chrome while it works on Android or Windows8 comments · 2023-02-27