2021å¹´ã®ã‚¦ã‚§ãƒ–標準ã¨ãƒ–ラウザ | gihyo.jp
2021å¹´ã«ãªã‚Šã¾ã—ãŸã。 矢倉眞隆（myakura）ã§ã™ã€‚ウェブ標準やブラウザã«èˆˆå‘³ã®ã‚るウェブ開発者ã§ã™ã€‚gihyo.jpã§ã¯2009å¹´ã«ã€ŒWeb標準ã¨ãã®å‘¨è¾ºæŠ€è¡“ã®å¦ã³æ–¹ã€ã¨ã„ã†é€£è¼‰ã‚’ã—ã¦ã„ã¾ã—ãŸã€‚ 今回ã¯æ˜¨å¹´ã®æ³‰æ°´ã•ã‚“ã«ä»£ã‚ã‚Šã€2021å¹´ã®ã‚¦ã‚§ãƒ–標準やブラウザã®å‹•å‘ã‚’å ãŠã†ã¨æ€ã„ã¾ã™ã€‚2020å¹´ã¯ä¸–界もブラウザもãã‚Œãªã‚Šã«å¤§ããªå‡ºæ¥äº‹ãŒã‚ã‚Šã¾ã—ãŸã®ã§ã€2020å¹´ã®å‹•ãã‚’ã¾ãšãŠã•ãˆã€ãã®ã†ãˆã§2021å¹´ã¯ã©ã†ãªã‚‹ã®ã‹ã‚’考ãˆã¦ã¿ã¾ã—ãŸã€‚ W3Cã®ãƒ—ãƒã‚»ã‚¹æ”¹è¨‚ã§Living Standardライクãªä»•æ§˜ã®æ”¹è¨‚ãŒå¢—ãˆã¦ã„ã W3Cã¯2020å¹´9月ã«ã€æ–°ã—ã„プãƒã‚»ã‚¹æ–‡æ›¸ã¨ç‰¹è¨±ãƒãƒªã‚·ãƒ¼ã‚’公開ã—ã¾ã—ãŸã€‚ æ–°ã—ã„文書プãƒã‚»ã‚¹ã¯W3Cã®çµ„ç¹”ã®å®šç¾©ã‚„標準化ã®æµã‚Œã€æ„æ€æ±ºå®šãªã©ã«ã¤ã„ã¦å®šã‚ãŸæ–‡æ›¸ã§ã™ã€‚ã“ã“æ•°å¹´ã¯æ¯Žå¹´æ›´æ–°ã•ã‚Œã¦ã„ã¾ã™ãŒã€2020å¹´ã¯ã“ã‚Œã¾ã§ã¨æ¯”ã¹ã¦æœ€å¤§ç´šã¨ãƒ—レスリリースã§ã‚‚ã†ãŸã‚ã‚Œã¦ã„ã¾ã™
top-level awaitãŒã©ã®ã‚ˆã†ã«ES Modulesã«å½±éŸ¿ã™ã‚‹ã®ã‹å®Œå…¨ã«ç†è§£ã™ã‚‹ - Qiita
先日ã€TypeScript 3.8 RCãŒå…¬é–‹ã•ã‚Œã¾ã—ãŸã€‚TypeScript 3.8ã¯ã‚¯ãƒ©ã‚¹ã®privateフィールド（#nameã¿ãŸã„ãªã‚„ã¤ï¼‰ã‚’始ã‚ã¨ã—ã¦ã€ECMAScriptã®æ–°æ©Ÿèƒ½ã®ã‚µãƒãƒ¼ãƒˆãŒã„ãã¤ã‹è¿½åŠ ã•ã‚Œã¦ã„ã¾ã™ã€‚ã“ã®è¨˜äº‹ã§å–り扱ã†top-level awaitã‚‚ãã®ä¸€ã¤ã§ã™ã€‚ ã“ã®è¨˜äº‹ã§ã¯top-level awaitã«ç„¦ç‚¹ã‚’当ã¦ã¦ã€ãã®æ„味や使ã„æ–¹ã«ã¤ã„ã¦ä½™ã™ã¨ã“ã‚ãªã解説ã—ã¾ã™ã€‚top-level awaitã¯ä¸€è¦‹å˜ç´”ãªæ©Ÿèƒ½ã«è¦‹ãˆã¾ã™ãŒã€å®Ÿã¯ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ« (ES Modules) ã¨æ·±ã„関係ãŒã‚ã‚Šã€ãã“ãŒtop-level awaitã®ç‰¹ã«é›£ã—ã„点ã§ã™ã€‚ãã“ã§ã€ã“ã®è¨˜äº‹ã§ã¯ECMAScriptã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã«ã¤ã„ã¦ã‚‚詳ã—ã解説ã—ã¾ã™ã€‚ã“ã®è¨˜äº‹ã‚’èªã‚“ã§top-level awaitを完全ã«ç†è§£ã—ã¦å‚™ãˆã¾ã—ょã†ã€‚ ※ ã“ã®è¨˜äº‹ã¯3分ã®1ãらã„èªã‚€ã¨ã€Œã¾ã¨ã‚ã€ãŒã‚ã‚Šã€æ®‹ã‚Šã¯ãŠã¾ã‘ã§
HTML Standard
Firefox1+Safari1+Chrome1+Opera4+Edge79+Edge (Legacy)12+Internet Explorer4+Firefox Android?Safari iOS?Chrome Android?WebView Android?Samsung Internet?Opera Android10.1+ Schedules a timeout to run handler after timeout milliseconds. Any arguments are passed straight through to the handler. id = self.setTimeout(code [, timeout ]) Schedules a timeout to compile and run code after timeout milliseconds.
Why isn't it <style src="">? | CSS-Tricks
DigitalOcean provides cloud products for every stage of your journey. Get started with $200 in free credit! The way JavaScript works is we can do scripts as an inline block: <script> let foo = "bar"; </script> Or, if the script should be fetched from the network… <script src="/js/global.js"></script> With CSS, we can do an inline block of styles: <style> .foo { color: red; } </style> So why not <s
auxclick
The new input event type introduced in this document provides web developers a way to listen to the "click" behavior of non-primary buttons, and potentially cancel their effect (eg. opening a new tab when middle clicking on a link). This new input type is needed because the click event is restricted to primary button only. This proposal was first introduced in this discourse . Introduction Traditi
The WHATWG Blog — Defining the WindowProxy, Window, and Location objects
Please leave your sense of logic at the door, thanks! Defining the WindowProxy, Window, and Location objects May 12th, 2016 by Anne van Kesteren in WHATWG The HTML Standard defines how navigation works inside a browser tab, how JavaScript executes, what the overarching web security model is, and how all these intertwine and work together. Over the last decade, we’ve made immense progress in specif
DOM Standard
Participate: GitHub whatwg/dom (new issue, open issues) Chat on Matrix Commits: GitHub whatwg/dom/commits Snapshot as of this commit @thedomstandard Tests: web-platform-tests dom/ (ongoing work) Translations (non-normative): 日本語 简体ä¸æ–‡ Abstract DOM defines a platform-neutral model for events, aborting activities, and node trees. 1. Infrastructure This specification depends on the Infra Standard. [IN
Add <script type="module"> and module resolution/fetching/evaluation by domenic · Pull Request #443 · whatwg/html
This adds support for <script type="module"> for loading JavaScript modules, as well as all the infrastructure necessary for resolving, fetching, parsing, and evaluating module graphs rooted at such <script type="module">s. This was spurred on by a request over in whatwg/loader#83 (comment). This should take care of whatwg/loader#83, whatwg/loader#84, and whatwg/loader#82. There is not much overla
GitHub - rocallahan/innerText-spec: Draft specification for DOM "innerText" property
The intent here seems to be that getting an element's innerText returns its text "as rendered". All browsers seem to have implemented a different set of heuristics for approximating that, typically approximating some subset of CSS processing. We can avoid specifying processing rules that duplicate and approximate some subset of CSS by specifying innerText's getter in terms of the rendered text pro
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Should `onfocusin`/`onfocusout` IDL attributes be added? · Issue #4542 · whatwg/html
"macrotask" isn't a thing by jakearchibald · Pull Request #74 · WICG/scheduling-apis
TAG Review Request: queueMicrotask · Issue #294 · w3ctag/design-reviews
editing/docs/EditContext/explainer.md at gh-pages · alexkeng/editing
A new mode for iframes where they don't add to the joint session history? · Issue #6501 · whatwg/html
Define serialization and deserialization steps for Error by yutakahirano · Pull Request #4665 · whatwg/html
tc39-notes/jan-25.md at master · rwaldron/tc39-notes · GitHub
792108 - Use a class flag to allow objects of that class to act like |undefined| in the == and ToBoolean contexts, and remove JSRESOLVE_DETECTING
Allow removing event listeners by group by domenic · Pull Request #469 · whatwg/dom
GitHub - WICG/aom: Accessibility Object Model
GitHub - WICG/EventListenerOptions: An extension to the DOM event pattern to allow authors to disable support for preventDefault
{{#tags}}- {{label}}
{{/tags}}