オフラインWebアプリの再到来で今、再び注目されるAPIの本命 ーJavaScript SQL-like database
オフラインWebアプリの再到来で今、再び注目されるAPIの本命 ーJavaScript SQL-like database
HTML5 DOM4 ES5 ES 2015 ES 2016 ES 2017 XHR2 SVG2 We list all new stuff that comes with more recent specifications, relative to the previous version (whatever "version" means nowadays). I will happily receive any request for changes if something is not up-to-date or is inaccurate. Please raise an issue on Github. Ideally, I'd love you to give me proof that what you say is true.
This feature is well established and works across many devices and browser versions. It’s been available across browsers since July 2015. * Some parts of this feature may have varying levels of support. Learn more See full compatibility Report feedback KeyboardEvent objects describe a user interaction with the keyboard; each event describes a single interaction between the user and a key (or combi
Date.now() // 1337376068250 performance.now() // 20303.427000007 You'll notice the two above values are many orders of magnitude different. performance.now() is a measurement of floating point milliseconds since that particular page started to load (the performance.timing.[navigationStart](https://www.w3.org/TR/navigation-timing/#dom-performancetiming-navigationstart) timeStamp to be specific). Yo
Not long ago, I tagged Prototype 1.7.1, an update 18 months in the making. It features an overhaul of our DOM library and better coexistence with ES5 methods, but quite a bit more as well. I’m sure you’re curious about why it’s taken so long. But first let’s look at what’s been done in 1.7.1. When last we spoke, I told you about the plans we had for 1.7.0.1 and 1.7.1 — a bugfix release and a minor
April 12, 2023 New community features for Google Chat and an update on Currents Currents Google Chat Other Note: This blog post outlines upcoming changes to Google Currents for Workspace users. For information on the previous deprecation of Google+ for users with personal Google accounts, please see this post. Last year, we announced plans to wind down Currents, to focus efforts on community exper
ここでは以下の順番でSinonJSとJsTestDriverを使用したJavaScriptのUnitTest Patternsを紹介します。
Lately its getting more and more obvious that web development is indeed a basic human right. And it should be accessible to every developer in the industry. jQuery played its part by making web development easier for designers, CoffeeScript for Rubyists and Pythonistas, Dart for Java devs, ClojureScript for Lispers etc. But what about DBAs? aren't they equally human? Should they be doomed to suffe
Laconic offers an intuitive approach to generating DOM content in JavaScript. The source code is available on GitHub. Consider the code necessary to produce a simple table hierarchy with the standard DOM API: var firstTh = document.createElement('th'); firstTh.appendChild(document.createTextNode('first name')); var secondTh = document.createElement('th'); secondTh.appendChild(document.createTextNo
We're very happy to see that some common DOM operations have just skyrocketed in speed. The changes were at the WebKit level, boosting performance for both Safari (JavaScriptCore) and Chrome (V8). Chrome Engineer Kentaro Hara made seven code optimizations within WebKit; below are the results, which show just how much faster JavaScript DOM access has become: DOM performance boosts summary div.inner
Sorry; your browser does not support svg! Sorry; your browser does not support svg! http://www.meetup.com/framsia/ < 100ms "0.1 second [100ms] is about the limit for having the user feel that the system is reacting instantaneously, meaning that no special feedback is necessary except to display the result." Jakob Nielsen
The Mozilla project has gone through a number of different JS bindings for the DOM in Mozilla. This post is basically a trip down memory lane, walking through how JS running in the SpiderMonkey JavaScript engine in Mozilla has communicated with the C++ DOM throughout the years. But before I get into that, let’s clarify what DOM bindings are. DOM bindings are the pieces of code that sit in between
※ phiary に引っ越しました. 毎日プログラミングやWebに関する情報を発信しています! RSS 登録してたまに覗いたり, tweet やハテブして拡散してもらえると幸いです. JavaScript ライブラリ TMLib を公開しました. ゲームを作る際や, DOM で遊んだりする際にご使用下さい.(α版です. βや正式版にする予定はありません) 動的スクリプトのロードやゲーム制作に必要なスクリプト, Vector, Matrix といったクラスのサポートなど色々やっています. 荒削りですし色々とツッコミどころ満載ですが… 昔作ったやつなので, 温かい目で見てやって下さい. About TMLib とは『JavaScript をより使いやすく, より便利に, そしてより豊かに.』をコンセプトに制作したJavaScript 拡張ライブラリです. jQuery のコードを読んでいて生意
もずはっく日記(2012年2月) 2012年2月28日 Bug-org 730760 laying out and rendering shouldn't halt by <script> accessing another server for src attribute 初回投稿日時: 2012-02-28 12:44:26 最終更新日時: 2012-02-28 15:37:26 カテゴリ: Javascript Mozilla Core バグ原因判明 バグ報告 SNS: Tweet (list) 一部のページにアクセスした時に、別のサーバへの接続を開始すると、レイアウトやレンダリングが一時的に中断する、というバグです。前々からFlashの挙動を確認するのに使っていたページで発生していたのですが、一向に修正される気配がないので、どういうことか調べてもらうために報告しました。 原因は
In an ideal world there would always be a clean way of displaying data supplied by a third party on your site. Two examples would be getting the data in JSON or XML format from a Web Service and having an API to code against. But you don’t always have any of those options. Sometimes the only way of incorporating data from a third party is by loading it in an iframe element. A few examples are fina
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く