You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Aborting a fetch: The Next Generation · Issue #447 · whatwg/fetch
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Improving ergonomics of events with Observable · Issue #544 · whatwg/dom · GitHub
Observable has been at stage 1 in the TC-39 for over a year now. Under the circumstances we are considering standardizing Observable in the WHATWG. We believe that standardizing Observable in the WHATWG may have the following advantages: Get Observable to web developers more quickly. Allow for a more full-featured proposal that will address more developer pain points. Address concerns raised in th
W3C vs. WHATWG HTML5 Specs - The Differences Documented - Telerik Blogs
A few weeks ago, HTML5 became an official W3C Recommendation. I took advantage of this event to discuss 5 interesting but now obsolete features on SitePoint. The problem is that the W3C specifications are only one side of the same coin. Starting from this version of HTML, developers and browser vendors can choose between two different flavors of the same markup language: the specifications develop
Please leave your sense of logic at the door, thanks! CSS Books & CSS Figures October 14th, 2013 by Håkon Wium Lie in WHATWG Today we're happy to add two more specs to the WHATWG stable, Books and Figures! These are specifications focused on CSS features. Books provides ways to turn HTML document into books, either on screen or on paper. Using Books, authors can style cross-references, footnotes,
WHATWG
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Responsive image element proposed by the WHATWG | Responsive Images Community Group
After months of discussing possible solutions for responsive images on the WHATWG mailing list, I discovered yesterday that another, different syntax was proposed on the WHATWG IRC channel. Additionally, when I joined the discussion, it became apparent that the majority of the WHATWG leads present in IRC weren’t aware of the proposed picture element—or, in fact, this Community Group. Thankfully, a
Sometimes, new authors need a gentle reminder to think about accessibility when designing and writing web pages and apps. Experienced authors need a quick way to look up the allowed ARIA roles, states and properties for each HTML element. Browser and Assistive Technology (AT) implementers need quick access from an HTML element to its platform accessibility API. For a look at how these needs transl
url: expose the WHATWG URL API globally by targos · Pull Request #18281 · nodejs/node
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
WHATWGがWebストリームを標準化
Spring BootによるAPIバックエンド構築実践ガイド 第2版 何千人もの開発者が、InfoQのミニブック「Practical Guide to Building an API Back End with Spring Boot」から、Spring Bootを使ったREST API構築の基礎を学んだ。この本では、出版時に新しくリリースされたバージョンである Spring Boot 2 を使用している。しかし、Spring Boot3が最近リリースされ、重要な変...
Allow <div> around each <dt><dd> group in <dl> (#1945) · whatwg/html@5454d70
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Last Update: May 28, 2019 Memorandum of Understanding Between W3C and WHATWG This Memorandum of Understanding (“MOU ”) is entered into this __May 28, 2019, between the World Wide Web Consortium (“W3C”), with its principal place of business located at 32 Vassar Street, Room 32-386, Cambridge, MA, 02139 USA; and the WHATWG. Whereas W3C is an international community where Member organizations, a full
Welcome to the newest standard maintained by the WHATWG: the URL Pattern Standard! The URL Pattern Standard gives a generic pattern syntax for matching URLs, and extracting the parts from them. It is inspired by the path-to-regexp library, although it extends beyond paths to encompass all the parts of a URL. You can read more about the API on MDN. The URL Pattern Standard joins us as a graduation
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Please leave your sense of logic at the door, thanks! Spelling HTML5 September 10th, 2009 by Henri Sivonen in WHATWG What’s the right way to spell “HTML5”? The short answer is: “HTML5” (without a space). People in the WHATWG community have commonly referred to HTML5 as “HTML5” for quite a while. However, when the W3C HTML WG voted on adopting “Web Applications 1.0” the question about the title sai
JSer.info #352 - Mocha 4.0.0がリリースされました。 Mocha v4 Nears Release Release v4.0.0 · mochajs/mocha Node.jsの古いバージョンやIE8以下などのサポート終了、--no-exitがデフォルトの動作になっています。また、4.0.0では--compilersコマンドライン引数が非推奨となり--requireに動作を寄せていくようです。 compilers deprecation · mochajs/mocha Wiki npm 5.5.0が公開されています。 Release v5.5.0 · npm/npm このリリースには2要素認証のサポートが含まれています。 また、npmにおいてreadonly tokenが発行できるようになっています。 詳細は次の記事やスライドで解説されています。 The npm
HTML vs. XHTML - WHATWG Wiki
It is the MIME type (which may or may not be determined by file extension) that determines what type of document you are using. Any document served as text/html, including a document authored with the intention of being XHTML, is technically an HTML document. Note that XHTML 1.0 previously defined that documents adhering to the compatibility guidelines were allowed to be served as text/html, but H
MetaExtensions - WHATWG Wiki
A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam. To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members). This page lists extension values for the name="" attribute of the HTML <meta> element. You may add your own values to this list. For assistance in preparing a specifica
GitHub - inikulin/parse5: HTML parsing/serialization toolset for Node.js. WHATWG HTML Living Standard (aka HTML5)-compliant.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
HTML5 General canvas with some limitation implemented in Firefox, Opera, Safari, and Konqueror 4, with ExplorerCanvas emulated in Internet Explorer getElementsByClassName implemented in Firefox 3, Safari 3.1, Opera 9.5 localStorage and sessionStorage implemented in Firefox 2, IE 8, Safari 4 Database storageimplemented in Safari 3.1 and iPhone Safari 2.0 Custom content handlers partially implemente
Please leave your sense of logic at the door, thanks! HTML Standard now more community-driven January 25th, 2016 by Anne van Kesteren in WHATWG It’s been several months now since maintenance of the HTML Standard moved from a mostly-private Subversion repository to the whatwg/html GitHub repository. This move has been even more successful than we hoped: We now have thirty-seven contributors who hav
Require utf-8 when specifying character encoding by sideshowbarker · Pull Request #3091 · whatwg/html
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
The demos and segments of this talk are: <video> (00:35) postMessage() (05:40) localStorage (15:20) sessionStorage (21:00) Drag and Drop API (29:05) onhashchange (37:30) Form Controls (40:50) <canvas> (56:55) Validation (1:07:20) Questions and Answers (1:09:35) The notes were: HTML5 DEMOS =========== This is a series of demos intended for showing implementations of HTML5 in (non-final) browsers av
bouzuya/whatwg-streams-fns および bouzuya/whatwg-streams-b をつくった - bouzuya.hatenablog.com
bouzuya/whatwg-streams-fns および bouzuya/whatwg-streams-b をつくった。つくっている。 bouzuya/whatwg-streams-fns は WHATWG Streams 向けの utility library 。map や filter などの RxJS / xstream などにありそうな operator を提供する。ReadableStream や TransformStream などを生成する factory になるはず。まだ個数が不足しているのと RxJS などとは Model が違う点を考慮して増やさないといけない。 bouzuya/whatwg-streams-b は非公式な WHATWG Streams 実装。参考実装を勝手に npm package として公開したもの。whatwg-streams-fns をつくる
The WHATWG Blog — WHATWG Weekly: Path objects for canvas and creating paths through SVG syntax
Please leave your sense of logic at the door, thanks! WHATWG Weekly: Path objects for canvas and creating paths through SVG syntax March 14th, 2012 by Anne van Kesteren in Weekly Review Jonas Sicking proposed an API for decoding ArrayBuffer objects as strings, and encoding strings as ArrayBuffer objects. The thread also touched on a proposal mentioned here earlier, StringEncoding. This is the mid-
Add promise rejection tracking events · whatwg/html@61ccc05
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
WHATWG - HTML5 Working Draft 『4.10 クライアント側のキー/値ペアーのセッションと永続ストレージ』日本語訳 - HTML5.JP
WHATWG - HTML5 Working Draft 日本語訳 4.10 クライアント側のキー/値ペアーのセッションと永続ストレージ 一部、直訳ではなく意訳した部分がございます。原文と表現が異なることがございますので、ご了承ください。この日本語訳は、私が理解を深めるために、自分なりに日本語化したものです。本日本語訳には、翻訳上の誤りがある可能性があります。したがって、内容について一切保証をするものではありません。正確さを求める場合には、必ず原文を参照してください。当方は、この文書によって利用者が被るいかなる損害の責任を負いません。もし誤りなどを見つけたら、当サイトのお問い合わせより連絡いただければ幸いです。 原題：HTML 5 Working Draft - 27 October 2007 4.10 Client-side session and persistent storage
The WHATWG Blog — WHATWG Weekly: Sniffing, Peer-to-Peer, and hgroup
Please leave your sense of logic at the door, thanks! WHATWG Weekly: Sniffing, Peer-to-Peer, and hgroup January 31st, 2011 by Anne van Kesteren in Weekly Review Another week, another WHATWG Weekly. While the change of name continues to excite the wider world — be sure to read HTML5 vs. HTML by Jeffrey Zeldman for some perspective — standards development marches on. Media Type Sniffing At the start
[giow] (2) Make appcache no longer check for the MIME type. · whatwg/html@854c7d2
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
![[giow] (2) Make appcache no longer check for the MIME type. · whatwg/html@854c7d2](https://cdn-ak-scissors.b.st-hatena.com/image/square/cc924b9456992ce8975d1548ffc5f7f57b8faf6c/height=288;version=1;width=512/https%3A%2F%2Fopengraph.githubassets.com%2Fe9ba0ead8e9e0ebbdc66c799dee9729d7ff48995182d933d6ad69b1874a59d9b%2Fwhatwg%2Fhtml%2Fcommit%2F854c7d289af128df85bee46bdd66d7b276229b55)
Why not conneg - WHATWG Wiki
A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam. To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members). The purpose of this page is to explain what's wrong with HTTP content negotiation and why you should not suggest HTTP content negotiation as a solution to a problem. HT
IDPFのEPUBはHTML5を利用している。HTML5はHTMLの最新仕様で あり、広く関心を集めている。しかし、HTML5とはどの団体のど の仕様書によって定められているのだろうか？ おそらく、HTML5といえばW3Cが定めているものと理解されてい るだろう。しかし、ことはそう簡単ではない。HTML5はWHATWGと いう団体が定めており、W3Cは単に追認しているだけだとという 見解も存在する。そして、私の見るところでは、どちらが正しいと も簡単には言えない。 まず、2012年あたりまでの経緯は、以下の記事にある。 「HTML5仕様をめぐるW3CとWHATWGについて、Ian Hickson氏がメーリングリストに書いたこと」 簡単にいうと、W3CとWHATWGは協力しており、WHATWGは最新版を やるところであって、W3Cが安定版を作るところだという切り分 けである。 W3CのMic
Please leave your sense of logic at the door, thanks! Supporting New Elements in IE January 7th, 2009 by Lachlan Hunt in Browsers, DOM, Elements, Events, Syntax Internet Explorer poses a small challenge when it comes to making use of the new elements introduced in HTML5. Among others, these include elements like section, article, header and footer. The problem is that due to the way parsing works
GitHub - radiosilence/xr: Ultra-lightweight wrapper around XMLHttpRequest. You should probably use fetch (whatwg-fetch) or RxJS, though.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
The WHATWG Blog — Infra
Please leave your sense of logic at the door, thanks! Infra November 16th, 2016 by Anne van Kesteren in What's Next, WHATWG Welcome to the newest standard maintained by the WHATWG: the Infra Standard! Standards such as DOM, Fetch, HTML, and URL have a lot of common low-level infrastructure and primitives. As we go about defining things in more detail we realized it would be useful to gather all th
[whatwg] Administrivia: Update on the relationship between the WHATWG HTML living standard and the W3C HTML5 specification from Ian Hickson on 2012-07-19 (public-whatwg-archive@w3.org from July 2012)
[whatwg] Administrivia: Update on the relationship between the WHATWG HTML living standard and the W3C HTML5 specification From: Ian Hickson <ian@hixie.ch> Date: Thu, 19 Jul 2012 22:48:37 +0000 (UTC) To: whatwg@whatwg.org Message-ID: <Pine.LNX.4.64.1207192151540.27616@ps20323.dreamhostps.com> If you've been happily ignoring the W3C's involvement with HTML these past few years, you can stop reading
[e] (0) Revamp how we refer to XHTML, the HTML syntax, and DOM5 HTML … · whatwg/html@a096505
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
![[e] (0) Revamp how we refer to XHTML, the HTML syntax, and DOM5 HTML … · whatwg/html@a096505](https://cdn-ak-scissors.b.st-hatena.com/image/square/2d9b9c1e913b3c6492d23777b841037f3e5bc5d6/height=288;version=1;width=512/https%3A%2F%2Fopengraph.githubassets.com%2F7a21965de7c77d6db1a0057c6dfa9af83b383243b280fcd089ef99f506d49b54%2Fwhatwg%2Fhtml%2Fcommit%2Fa096505b130ed7832b9fe3f213f55a00abc56942)
Provides more control over how canvases are rendered. This is a follow-on to the WorkerCanvas proposal and will be merged once agreement is reached. Use Case Description Feedback from web application authors using canvases have shown the need for the following controls: (From ShaderToy, Sketchfab, Verold): need to be able to render to multiple regions on the page efficiently using a single canvas
The WHATWG Blog — WHATWG Weekly: Stream API and better autocomplete
Please leave your sense of logic at the door, thanks! WHATWG Weekly: Stream API and better autocomplete December 15th, 2011 by Anne van Kesteren in Weekly Review James Hawkins proposed the intent element in a way that brings back memories of HTML4. Happy to be reminded we are over SGML now. This is the WHATWG Weekly. Better autocomplete Overnight a complete proposal for better autocomplete appeare
[task] milestone 0: <script type="module"> · Issue #83 · whatwg/loader
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
![[task] milestone 0: <script type="module"> · Issue #83 · whatwg/loader](https://cdn-ak-scissors.b.st-hatena.com/image/square/4991a4d88d9ca9052bacc09991410e1ccd80985c/height=288;version=1;width=512/https%3A%2F%2Fopengraph.githubassets.com%2F930dfa42c06ca70e6bdf8a290ae7c663fa41f007eb9993b4175935e7e1282fc3%2Fwhatwg%2Floader%2Fissues%2F83)
Aborting fetch by jakearchibald · Pull Request #523 · whatwg/fetch
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
W3C and the WHATWG signed an agreement to collaborate on a single version of HTML and DOM
W3C and the WHATWG signed an agreement to collaborate on a single version of HTML and DOM Today W3C and the WHATWG signed an agreement to collaborate on the development of a single version of the HTML and DOM specifications. The Memorandum of Understanding jointly published as the WHATWG/W3C Joint Working Mode gives the specifics of this collaboration. This is the culmination of a careful explorat
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
The WHATWG Blog — CSS Books & CSS Figures
The WHATWG Blog — Considering accessibility
Memorandum of Understanding Between W3C and WHATWG
The WHATWG Blog — The URL Pattern Standard
Remove <style scoped> · Issue #552 · whatwg/html
The WHATWG Blog — Spelling HTML5
2017-10-10のJS: Mocha 4.0.0、npm 2要素認証、WHATWG Stream - JSer.info
Implementations in Web browsers - WHATWG Wiki
The WHATWG Blog — HTML Standard now more community-driven
Demos from September 2008 — WHATWG
HTML5: W3CとWHATWGとIDPF - 村田真のXMLブログ
The WHATWG Blog — Supporting New Elements in IE
OffscreenCanvas - WHATWG Wiki