The WHATWG Blog — WHATWG Weekly: HTML canvas version 5 has arrived
Please leave your sense of logic at the door, thanks! WHATWG Weekly: HTML canvas version 5 has arrived March 29th, 2012 by Anne van Kesteren in Weekly Review The StringEncoding proposal is getting closer to consensus. It now consists of a TextEncoder and a TextDecoder object that can be used both for streaming and non-streaming use cases. This is the WHATWG Weekly. Some bad news for a change. It m
概要 WHATWG Streams のことを何回かに分けて書く。Kyoto.js #11 の『 WHATWG Streams をためした 』という発表のために調べたものだ。発表だけで終わらせるのはもったいないので、再整理して共有する。 前回は『 WHATWG Streams の Stream と Pipe chain - Qiita 』。今回は (Underlying) Source と (Underlying) Sink のことを書く。 また Source / Sink については概要に留め、それぞれの使いかたなどの詳細は別途記載する。 データの発生源 ReadableStream に wrap される Push / Pull の 2 種類の違いを吸収し、ひとつの interface で表す Push Source 例: TCP ソケット Pull Source 例: ファイルハンドル
Please leave your sense of logic at the door, thanks! WHATWG Weekly: TPAC 2011 November 10th, 2011 by Anne van Kesteren in Weekly Review A long week Filled with people and meetings WHATWG Weekly Last week the W3C held its yearly TPAC conference. See Unorganization for an impression of the event written by me. Karl wrote down some technical details. What follows is my brief technical takeaway. <tim
Modal prompts - 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). Overview This document describes a proposal for gradually removing modal dialogs and prompts from the platform. Rationale In a tabbed browser, modal dialogs are potenti
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 is intended to formalize the discussion around an important but currently underserved use-case (in both spec and various browser implementations): the need fo
WHATWG では、HTML5 仕様を開発・策定していることはご存知のとおりですが、このたび、HTML のバージョン番号を表す 5 がなくなりました。これまで、みなさんがご覧になっていた WHATWG の HTML5 仕様のタイトルから、すでに HTML のバージョン番号を表す 5 がなくなっています。新たな名前は WHATWG HTML です。 これは HTML5 のエディタである Ian Hickson 氏より、WHATWG のメーリングリストの投稿「Switching to an unversioned development model」にてアナウンスされたものです。 彼は、以前から WHATWG は HTML のバージョン番号を気にして活動していたわけではなく、今後も WHATWGの活動内容が変わるとを意味するものではないと言っています。 ただ、WHATWG の仕様書が、これまで
[whatwg] HTML Cookie API
Adam Barth w3c at adambarth.com Tue Feb 23 20:56:31 PST 2010 Previous message: [whatwg] Web Workers: include simple example for shared workers Next message: [whatwg] HTML Cookie API Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] The document.cookie API is kind of terrible. Web developers shouldn't have to parse a cookie-string or prepare a properly formated set-cookie-string. Here'
Please leave your sense of logic at the door, thanks! Usability testing HTML5 October 4th, 2009 by Ian Hickson in WHATWG Over the past few weeks, Google has been preparing and then running a usability study to test the microdata feature of HTML5. Methodology We first created three different variants based on the original microdata proposal: One based on what the spec said (documentation) One tryin
Standards — WHATWG
Standards The WHATWG works on a number of technologies that are fundamental parts of the web platform. They are organised somewhat arbitrarily based on the preferences of those editing the standard for those technologies. Compatibility (@compatstandard) The Compatibility Standard describes a collection of non-standard (and often vendor-prefixed) CSS properties and DOM APIs that web browsers need t
Firefox1+Safari3+Chrome1+Opera12.1+Edge79+Edge (Legacy)12+Internet Explorer5.5+Firefox Android?Safari iOS1+Chrome Android?WebView Android?Samsung Internet?Opera Android12.1+ Categories:Flow content.Palpable content.Contexts in which this element can be used:Where flow content is expected.Content model:In this order: optionally a caption element, followed by zero or more colgroup elements, followed
Should we block port 10080? · Issue #1191 · 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
GitHub - jsdom/whatwg-mimetype: Parses, serializes, and manipulates MIME types, according to the WHATWG MIME Sniffing Standard
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.
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
Hey All, I'd like to explore support for importing json, similar to how Node.js currently support require('./some.json') Expected behavior: imported json would export an object or array with the content from the provided json file. Why: Currently the was to get JSON is via fetch + import.meta.url... and requires a bit of back and forth... the eventual result is a promise to resolve to the json obj
class: center, middle, first # WHATWG Streams をためした 2016-10-22 Kyoto.js #11 [bouzuya](http://bouzuya.net) --- class: center, middle # ぼく --- class: center, middle, profile  .name[bouzuya] --- class: middle, profile-links - [github.com/**bouzuya**](https://github.com/bouzuya) - [hatena.ne.jp/**bouzuya**](http://hatena.ne.jp/bouzuya) - [t
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
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
[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)
Cross-Origin-Resource-Policy (was: From-Origin) · Issue #687 · whatwg/fetch
Websites should have an explicit way to restrict any kind of cross-origin load to protect themselves against Spectre attacks. Content such as images, video, and audio may be sensitive and websites may be protected solely by virtue of their network position (inside a firewall), relying on the same-origin policy to protect against exfiltration. There's a previous proposal from 2012 called the From-O
Standardize <template> variables and event handlers · Issue #2254 · whatwg/html
Proposal by Apple - https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Template-Instantiation.md Proposal by Google - https://github.com/domenic/template-parts This is a proposal on standardizing <template> parser which would allow developers: put variables, use simple statements and attach event handlers when template Node generated/inserted into DOM Current stage: Open Discussion about
WHATWG FAQ - 日本語訳 - HTML5.JP
一部、直訳ではなく意訳した部分がございます。原文と表現が異なることがございますので、ご了承ください。この日本語訳は、私が理解を深めるために、自分なりに日本語化したものです。本日本語訳には、翻訳上の誤りがある可能性があります。したがって、内容について一切保証をするものではありません。正確さを求める場合には、必ず原文を参照してください。当方は、この文書によって利用者が被るいかなる損害の責任を負いません。もし誤りなどを見つけたら、当サイトのお問い合わせより連絡いただければ幸いです。 原文：http://blog.whatwg.org/faq/ （2011 年 1 月 21 日版） 翻訳日：2011/01/25 最終更新日：2011/01/25 概要 WHATWGが公開しているHTML5のFAQです。HTML5の目的や存在意義といった大枠の話から、要素の記述方法といった細かい話まで、さまざまな方面
Add <img> decoding="" attribute by vmpstr · Pull Request #3221 · whatwg/html
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Pick a username Email Address Password Sign up for GitHub By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails. Already on GitHub? Sign in to your account
Please leave your sense of logic at the door, thanks! This Week in HTML 5 – Episode 12 November 11th, 2008 by Mark Pilgrim, Google in Weekly Review Welcome back to "This Week in HTML 5," where I'll try to summarize the major activity in the ongoing standards process in the WHATWG and W3C HTML Working Group. The primary editor was traveling this week, so there are very few spec changes to discuss.
Proposal: HTML passwordrules attribute · Issue #3518 · whatwg/html
HTML passwordrules attribute Motivation Some user agents offer to generate random per-site passwords on behalf of the user. Safari has built-in support for this, and add-on password managers such as 1Password add this functionality. This feature improves user security by guaranteeing high-entropy passwords and avoiding reuse of the same password on multiple sites. One challenge with this approach
What problem are you trying to solve? 1. Manipulating cookies Historically, manipulating cookies in JavaScript has been tedious. Client-side cookies are represented in a single document.cookie string (requiring parsing), and server-side cookies have no standard representation, to begin with. As a JavaScript developer, I want a standard and straightforward API to 1) create, and 2) manipulate cookie
Allow removing event listeners by group by domenic · Pull Request #469 · whatwg/dom
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
Is requestAnimationFrame called at the right point? · Issue #2569 · 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
Add <script nomodule> to prevent script evaluation by domenic · Pull Request #2261 · 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
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! The Road to HTML 5: character encoding February 13th, 2009 by Mark Pilgrim, Google in Tutorials Welcome back to my semi-regular column, "The Road to HTML 5," where I'll try to explain some of the new elements, attributes, and other features in the upcoming HTML 5 specification. The feature of the day is character encoding, specifically how to d
Here's a good starting point for learning about the component model spec, which is being developed by applying a defined methodology. Introduction The Component Model introduces comprehensive support for creating DOM elements. Examples include layout managers, combinations of Dojo and jQuery widgets, isolated widgets, such as Like/+1 buttons, and built-in HTML elements themselves. Reflecting on th
JSer.info #549 - Node.js 16.5.0がリリースされました。 Node v16.5.0 (Current) | Node.js 16.5.0では試験的に、WHATWGで仕様策定されウェブブラウザに実装されているWHATWG Streams APIが実装されました。(stream/web) Node.jsでは、すでにNode.js Stream APIがありますが、これとは異なる実装です。 Node.js StreamとWHATWG Streamの違いについては次のドキュメントにも書かれています。 streams/FAQ.md at main · whatwg/streams Node.jsでWHATWG Streamを実装している理由としてはQUIC/HTTP3のサポートなどが挙げられています。 HTTP/3 support · Issue #38478 · nod
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
Fetch termination API "meeting" · Issue #455 · 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
Please leave your sense of logic at the door, thanks! WHATWG Weekly: Happy New Year! January 9th, 2012 by Anne van Kesteren in Weekly Review Happy new year everyone! We made great progress in standardizing the platform in 2011 and plan to continue doing just that with your help. You can join our mailing list to discuss issues with web development or join IRC if you prefer more lively interaction.
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! HTML5 conformance checking in Vim May 18th, 2008 by MikeSmith in Conformance Checking Kai Hendry has written an HTML filetype plugin for Vim that allows you to use Henri Sivonen’s Validator.nu conformance checking (validation) service remotely to check the contents of any HTML document you edit in Vim and determine if the document is HTML5-conf
WHATWG - HTML5 Working Draft 『4.11 クライアント側のデータベースストレージ』日本語訳 - HTML5.JP
WHATWG - HTML5 Working Draft 日本語訳 4.11 クライアント側のデータベースストレージ 一部、直訳ではなく意訳した部分がございます。原文と表現が異なることがございますので、ご了承ください。この日本語訳は、私が理解を深めるために、自分なりに日本語化したものです。本日本語訳には、翻訳上の誤りがある可能性があります。したがって、内容について一切保証をするものではありません。正確さを求める場合には、必ず原文を参照してください。当方は、この文書によって利用者が被るいかなる損害の責任を負いません。もし誤りなどを見つけたら、当サイトのお問い合わせより連絡いただければ幸いです。 原題：HTML 5 Working Draft - 3 November 2007 4.11. Client-side database storage 原文：http://www.whatwg.or
The WHATWG Blog — WHATWG Weekly: Unicode for the platform?
Please leave your sense of logic at the door, thanks! WHATWG Weekly: Unicode for the platform? February 22nd, 2012 by Anne van Kesteren in Weekly Review In less than a year we reached another arbitrary milestone. HTML is another thousand revisions further, now over 7000 (not quite 9000). This is the WHATWG Weekly. Over on [email protected], the mailing list used by TC39 (responsible for JavaScript
概要 WHATWG Streams のことを何回かに分けて書く。Kyoto.js #11 の『 WHATWG Streams をためした 』という発表のために調べたものだ。発表だけで終わらせるのはもったいないので、再整理して共有する。 今回は次の 3 つを書く。 WHATWG Streams の提供する Stream クラス それらの Stream でつくる Pipe chain Pipe chain を流れる chunk Stream クラスについては概要に留め、それぞれの詳細は別途記載する。 3 つの Stream クラス WHATWG Streams は次の 3 つの Streams クラスを提供している。 ReadableStream WritableStream TransformStream 今回はあくまでも概要だけを書く。 1. ReadableStream 読み取りのための
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
WHATWG Streams の Source と Sink - Qiita
The WHATWG Blog — WHATWG Weekly: TPAC 2011
Dynamic Script Execution Order - WHATWG Wiki
WHATWGでHTMLのバージョン番号がなくなる？ « HTML5.JP ブログ
The WHATWG Blog — Usability testing HTML5
4.9 Tabular data — WHATWG HTML (Including HTML5)
Remove shared workers? · Issue #315 · whatwg/html
JSON modules · Issue #4315 · whatwg/html
WHATWG Streams をためした - 2016-10-22 Kyoto.js #11 bouzuya
Remove microdata API · Issue #208 · whatwg/html
OffscreenCanvas - WHATWG Wiki
The WHATWG Blog — This Week in HTML 5 – Episode 12
Cookie API · Issue #9935 · whatwg/html
Aborting a fetch · Issue #27 · whatwg/fetch
The WHATWG Blog — The Road to HTML 5: character encoding
Component Model - WHATWG Wiki
2021-07-20のJS: Node.js 16.5.0(WHATWG Stream)、npm 7.20.0(`npm pkg`)、Ember 4のロードマップ
spec innerText · Issue #5 · whatwg/compat
The WHATWG Blog — WHATWG Weekly: Happy New Year!
Add webkitMatchesSelector() 😢 · whatwg/dom@9ac9c15
The WHATWG Blog — HTML5 conformance checking in Vim
WHATWG Streams の Stream と Pipe chain - Qiita