| { | |
| "x-send-defaults": true, | |
| "openapi": "3.0.0", | |
| "x-api-id": "json-rpc-example", | |
| "info": { | |
| "title": "JSON-RPC OpenAPI", | |
| "version": "1.0.0", | |
| "description": "Example of how to describe a JSON-RPC 2 API in OpenAPI" | |
| }, | |
| "servers": [ |
Your Service Worker script will need to import in Workbox and initialize it before calling any of the routes documented in this write-up, similar to the below:
importScripts('workbox-sw.prod.v1.3.0.js');
const workbox = new WorkboxSW();
// Placeholder array populated automatically by workboxBuild.injectManifest()
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
| { | |
| "name": "simple-node-d3", | |
| "version": "1.0.0", | |
| "description": "Serverside SVG via D3 & jsdom", | |
| "main": "index.js", | |
| "scripts": { | |
| "test": "echo \"Error: no test specified\" && exit 1" | |
| }, | |
| "author": "tom.g.pearson@gmail.com", | |
| "license": "ISC", |
| /** | |
| * Подборка багов CSS Анимаций и их решений | |
| */ | |
| /*1*/ | |
| .no_sec {transition: opacity 1s, box-shadow 0; box-shadow: 0 0 5px 5px #000;} | |
| .no_sec:hover {opacity: 0; box-shadow: none;} | |
| /*2*/ | |
| .pseudo {position: relative; transition: opacity 1s;} |