Speed Up Scroll Events with Passive Event Listeners | DigitalOcean
Okay, let me get this out of the way real quick. I hate websites that attach wheel (or touchstart and touchmove) events to a page. Utterly hate them. The main reason is the horrid resulting performance, especially on mobile. You see, the browser has to wait to redraw the page until the event listener finishes execution, as the event is able to be canceled. If your event runs on every single scroll
Aligned input events | Blog | Chrome for Developers
TL;DR Chrome 60 reduces jank by lowering event frequency, thereby improving the consistency of frame timing. The getCoalescedEvents() method, introduced in Chrome 58 provides the same wealth of event information you've had all along. Providing a smooth user experience is important for the web. The time between receiving an input event and when the visuals actually update is important and generally
Making touch scrolling fast by default | Blog | Chrome for Developers
We know that scrolling responsiveness is critical to the user's engagement with a website on mobile, yet touch event listeners often cause serious scrolling performance problems. Chrome has been addressing this by allowing touch event listeners to be passive (passing the {passive: true} option to addEventListener()) and shipping the pointer events API. These are great features to drive new content
Don't lose user and app state, use Page Visibility - igvita.com
Great applications do not lose user's progress and app state. They automatically save the necessary data without interrupting the user and transparently restore themselves as and when necessary - e.g. after coming back from a background state or an unexpected shutdown. Unfortunately, many web applications get this wrong because they fail to account for the mobile lifecycle: they're listening for t
Slide decks of JSConf 2014
berlin-jsconf-2014.md Jake Archibald (@jaffathecake): The ServiceWorker is coming; look busy https://speakerdeck.com/jaffathecake/the-serviceworker-is-coming-look-busy https://github.com/jakearchibald/trained-to-thrill/ https://www.youtube.com/watch?v=SmZ9XcTpMS4 Hunter Loftis (@hunterloftis): We Will All Be Game Progmrammers http://wwabgp.herokuapp.com/s http://youtu.be/QX0eauXBKwc CarterRabasa (
GeckoのDOMイベント処理の実装
Storytelling For The Web: Integrate Storytelling in your Design Process
Lesser-Known JavaScript Debugging Techniques
After I prototype an app I'm building, my time is split between the editor and the browser with the console open. I try to debug as I go to avoid creating a complete mess. Moreover, when I get a bug report for a production app the first thing that I do is try to debug using Chrome devtools, and I usually find the bug without touching my editor. To be effective at that, I had to learn a great deal
ホイール系イベント2014年版クロスブラウザ
Updated 2014.10.15 / Published 2014.03.04 ホイール系のイベントは各ブラウザの実装がバラバラでクロスブラウザ対策に苦労するイベントのひとつとして知られているでしょうが、Document Object Model Level 3 Eventsにより標準化されたwheelイベントが多くのブラウザで実装されてきています。本エントリーでは現状のホイール操作時の各イベントについて、クロスブラウザでフォールバックしながら用いる方法を解説していきます。 ホイール系イベント比較 DOMMouseScroll, MozMousePixelScroll DOMMouseScrollイベントとMozMousePixelScrollイベントはどちらもGecko 固有のため、現存ではFirefoxしかサポートしていないイベントです。DOMMouseScrollはスクロールする
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Page 1 | PageLifecycle.js Demo
Proposal: self.queueMicrotask(f) · Issue #512 · whatwg/html
Event: defaultPrevented property - Web APIs | MDN
GitHub - WICG/EventListenerOptions: An extension to the DOM event pattern to allow authors to disable support for preventDefault
JavaScriptでTouchEvents(Level-2)を擬似発火する - Qiita
GitHub - sroucheray/event-class: An event / channel JavaScript (ES6) class
用 Composition Event 改進 CodeMirror 對輸入法的支援 « The Front Row
javascript - フロントエンドjavascriptのpubsubパターンとカスタムイベントの違い・使い分け - スタック・オーバーフロー
Pointer Events is a W3C Recommendation
GitHub - pluma/axn: Listenable actions.
GitHub - facebookarchive/emitter: A JS EventEmitter foundation for evented code
GitHub - fat/bean: an events api for javascript
