| await new Promise(function (resolve) { | |
| setTimeout(function () { | |
| resolve(); | |
| }, 1000); | |
| }); | |
| // ... Can be shortened to: | |
| await new Promise(function (resolve) { | |
| setTimeout(resolve, 1000); |
| navigator.serviceWorker.getRegistrations().then(function (registrations) { | |
| if (!registrations.length) { | |
| console.log('No serviceWorker registrations found.') | |
| return | |
| } | |
| for(let registration of registrations) { | |
| registration.unregister().then(function (boolean) { | |
| console.log( | |
| (boolean ? 'Successfully unregistered' : 'Failed to unregister'), 'ServiceWorkerRegistration\n' + | |
| (registration.installing ? ' .installing.scriptURL = ' + registration.installing.scriptURL + '\n' : '') + |
| -- https://gist.github.com/mrienstra/8330528 | |
| -- Based on http://www.tuaw.com/2012/12/24/applescript-desktop-icon-race/ | |
| -- Inspired by http://namesakecomic.com/comic/happy-new-year-from-namesake/#comment-1182035013 | |
| -- Rearranges Desktop icons to flow from left to right, top to bottom. | |
| -- To have this run automatically every time files are added or removed from the Desktop, set this script to run as a Desktop "Folder Action". (See https://developer.apple.com/library/mac/documentation/applescript/conceptual/applescriptlangguide/reference/ASLR_folder_actions.html ) | |
| -- This is currently a rough proof-of-concept. It has only been tested with OS X 10.8.5 (Mountain Lion). |
Based on https://nadnosliw.wordpress.com/unicode-characters/
Entering text substitutions is tedious, whether done using iOS, iPadOS, or macOS. Fortunately it's possible to import text substitutions using a .plist file, using the instructions provided here:
| /* empty css */ function L() {} | |
| function nt(t, e) { | |
| for (const n in e) t[n] = e[n]; | |
| return t; | |
| } | |
| function Q(t) { | |
| return t(); | |
| } | |
| function z() { | |
| return Object.create(null); |
| const colors = { | |
| grey: 90, | |
| red: 31, | |
| yellow: 33, | |
| blue: 34, | |
| purple: 35, | |
| cyan: 36, | |
| white: 37, | |
| }; |
| // preview controller | |
| (() => { | |
| interface MarkdownConfig { | |
| scrollSync?: boolean; | |
| } | |
| class PreviewController { | |
| /** | |
| * Scroll map that maps buffer line to scrollTops of html elements | |
| */ |
Count: 65, not including /test/, /pages/ (inside examples), /.changeset/ & CHANGELOG.md files. 61 are README.md files (well, 60, 1 is a readme.md).
(used VS Code "files to exclude" .changeset,CHANGELOG.md,pages,test)
CONTRIBUTING.md README.md SECURITY.md STYLE_GUIDE.md .github/PULL_REQUEST_TEMPLATE.md examples/README.md
| The first approach use several layers. It takes advantage of the fact that you cannot trigger a "back" unless BODY's "scrollLeft" is 0. The disadvantage to this approach is the appearance of an additional horizontal scrollbar. There may also be some subtle side-effects to using "position: fixed". | |
| 1. The HTML element acts as a container for the BODY element, and uses "overflow: scroll". | |
| 2. The BODY element is 2 pixels wider than the page, so it can scroll 1px in either direction when its "scrollLeft" is 1 (neutral position). | |
| 3. We bind to the "onscroll" event of the window, and reset BODY's "scrollLeft" to 1. | |
| 4. The content is inside a DIV, which uses "position: fixed" so it doesn't jump around when the BODY is scrolling. | |
| The second approach uses the hash / history stack. Rather than trying to stop a "back" or "forward", we simply "buffer" the history stack so that we can detect any changes and return to our neutral position. | |
| 1. When we load the page, we change the hash to "#previous", then "#neutral", then |
| .17.0-3.2.pre-beta | |
| .17.0-dev.0.0-dev | |
| .17.0-dev.1.0-dev | |
| .17.0-dev.2.0-dev | |
| .17.0-dev.3.0-dev | |
| .17.0-dev.3.1-beta | |
| .17.0-dev.4.0-dev | |
| .17.0-dev.5.0-dev | |
| .18.0-6.0.pre-dev | |
| .18.0-dev.0.0-dev |