並び順

ブックマーク数

期間指定

  • から
  • まで

161 - 192 件 / 192件

新着順 人気順

WHATWGの検索結果161 - 192 件 / 192件

  • ES6/WhatWG Loader & Node

    ES6/WhatWG Loader & Node @BradleyMeck Node proposal Youtube video

      ES6/WhatWG Loader & Node
    • Abort controller by jakearchibald · Pull Request #437 · 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

        Abort controller by jakearchibald · Pull Request #437 · whatwg/dom
      • The WHATWG Blog — WHATWG Weekly: Simplifying the DOM

        Please leave your sense of logic at the door, thanks! WHATWG Weekly: Simplifying the DOM October 5th, 2011 by Anne van Kesteren in Weekly Review Odin Hørthe Omdal brought up cross-origin image loading via CORS as Gecko and WebKit have different implementations. Julien Chaffraix considers the relation between the disabled and sheet IDL attributes of the link element to be insufficiently defined. We

        • GitHub - Ethan-Arrowood/undici-fetch: A WHATWG Fetch implementation based on @nodejs/undici

          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 - Ethan-Arrowood/undici-fetch: A WHATWG Fetch implementation based on @nodejs/undici
          • A request data -> request hook (e.g. module specifiers -> module request) · Issue #2640 · whatwg/html

            (Note: OP edited by @domenic to add some more context) A request that often comes up in the context of modules, but is also applicable to other resources, is the ability to map resource specifiers (e.g. import "x" or <img src="x">) to different URLs than the one that would be naively computed. @guybedford closed #2547 where we discussed possible alternatives to the Loader API and what role service

              A request data -> request hook (e.g. module specifiers -> module request) · Issue #2640 · whatwg/html
            • Add module workers · whatwg/html@e3a5bb7

              Closes #550. The Worker and SharedWorker constructors now get an options object, which can be specified as { type: "module", credentials }, where credentials specifies the credentials mode used for the initial fetch and for subsequent imports. (This only applies to module workers; in the future we could extend it to classic workers if we wished.) importScripts will always throw a TypeError in modu

                Add module workers · whatwg/html@e3a5bb7
              • Allow constructing and subclassing EventTarget · whatwg/dom@c4c1c8b

                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

                  Allow constructing and subclassing EventTarget · whatwg/dom@c4c1c8b
                • GitHub - mysticatea/abort-controller: An implementation of WHATWG AbortController interface.

                  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.

                    GitHub - mysticatea/abort-controller: An implementation of WHATWG AbortController interface.
                  • Expose `history.index` in addition to `history.length` · Issue #2710 · whatwg/html

                    An integer history.index < history.length would be a big simplification for many history-based routers. Currently, many of these push/replace a "fake" first state when the app starts up only to record such an index. There might be some privacy/security concerns, but I can't think of any negatives that are not already possible with history.length, history.back(), etc. History state is used often fo

                      Expose `history.index` in addition to `history.length` · Issue #2710 · whatwg/html
                    • [whatwg] <img srcset> for responsive bitmapped content images

                      [whatwg] <img srcset> for responsive bitmapped content images Edward O'Connor eoconnor at apple.com Thu May 10 00:58:17 PDT 2012 Previous message: [whatwg] Proposal: Add window.getLastError (or modify invocation arguments of window.onerror) Next message: [whatwg] <img srcset> for responsive bitmapped content images Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Hi, When authors ada

                      • The WHATWG Blog — WHATWG Weekly: Is XBL still alive? And what are Web Intents?

                        Please leave your sense of logic at the door, thanks! WHATWG Weekly: Is XBL still alive? And what are Web Intents? September 22nd, 2011 by Anne van Kesteren in Weekly Review In commit 6559 CanvasPixelArray was destroyed in favor of Uint8ClampedArray from the Typed Arrays specification. DOM Core is now known as DOM4. Welcome to another WHATWG Weekly. On the mailing list of the W3C WebApps WG James

                        • FAQ - 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 WHATWG Blog — The state of fieldset interoperability

                            As part of my work at Bocoup, I recently started working with browser implementers to improve the state of fieldset, the 21 year old feature in HTML, that provides form accessibility benefits to assistive technologies like screen readers. It suffers from a number of interoperability bugs that make it difficult for web developers to use. Here is an example form grouped with a <legend> caption in a

                            • Add first-class support for differential script loading · Issue #4432 · 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

                                Add first-class support for differential script loading · Issue #4432 · whatwg/html
                              • JSIDL vs WebIDL · Issue #45 · whatwg/streams

                                So, if Streams are supposed to be a ES-level thing, then using the non-existent JS IDL may be ok (though the TC39 crowd will likely raise some eyebrows). However, I think it should be dumped in preference for a reference implementation of some sort, as is commonly the case for ES features (at least, that's what I've seen in their Wiki). If this is supposed to be a browser API, then I don't think w

                                  JSIDL vs WebIDL · Issue #45 · whatwg/streams
                                • The WHATWG Blog — WHATWG Weekly: Microdata, WebSocket protocol, Web IDL

                                  Please leave your sense of logic at the door, thanks! WHATWG Weekly: Microdata, WebSocket protocol, Web IDL July 11th, 2011 by Anne van Kesteren in Weekly Review The debate on what to do with mutation events is still ongoing, Web IDL and the WebSocket protocol are heading towards Last Call, HTML5 still is in Last Call, and Karl is still providing an alternative view on things in the Open Web Platf

                                  • The WHATWG Blog — First set of Review Drafts published

                                    (If you’re interested in the IPR status of WHATWG standards this post is for you; otherwise, feel free to skip.) One aspect of last year's working mode changes is the periodic publication of a Review Draft for each WHATWG Living Standard, as per the IPR Policy. The WHATWG published an initial five of these just now: Compatibility Console DOM Encoding Fetch To get notified of future Review Draft pu

                                    • The WHATWG Blog — Relationship update on HTML Living Standard and W3C HTML5

                                      Please leave your sense of logic at the door, thanks! Relationship update on HTML Living Standard and W3C HTML5 July 20th, 2012 by Anne van Kesteren in W3C, WHATWG In an email to the WHATWG mailing list Ian Hickson explained how the relationship between the WHATWG and W3C effort around HTML has evolved. It is recommended reading if you want to know the details. In summary, we will remain focused o

                                      • The WHATWG Blog — This Week in HTML5 – Episode 35

                                        Please leave your sense of logic at the door, thanks! This Week in HTML5 – Episode 35 September 16th, 2009 by Mark Pilgrim, Google in Weekly Review On August 7, 2009, Adrian Bateman did what no man or woman had ever done before: he gave substantive feedback on the current editor's draft of HTML5 on behalf of Microsoft. His feedback was detailed and well-reasoned, and it spawned much discussion. Se

                                        • Declarative Shadow DOM · Issue #510 · whatwg/dom

                                          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

                                            Declarative Shadow DOM · Issue #510 · whatwg/dom
                                          • W3Cで現在公開されているHTMLとDOM仕様、将来的にWHATWGのものに一本化する方針へ | スラド IT

                                            2012年以降、HTML5規格の策定においてWHATWGとW3Cが個別に規格をリリースする状況になっていたが(過去記事)、これが解消されるようだ(水底の血)。 これによると、規格の策定についてはWHATWGが行い、W3Cがそれを承認してW3C勧告にする、という流れになるという。

                                            • The WHATWG Blog — WHATWG Weekly: New canvas API goodies

                                              Please leave your sense of logic at the door, thanks! WHATWG Weekly: New canvas API goodies February 29th, 2012 by Anne van Kesteren in Weekly Review A draft for the SPDY protocol has been submitted, the W3C HTML WG mailing list goes crazy over media DRM. This is the WHATWG Weekly. In response to feedback Adam Barth changed the getRandomValues() method to return the array the method modifies. The

                                              • GitHub - zerkalica/fetch-builder: RequestOptions builder for 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 - zerkalica/fetch-builder: RequestOptions builder for whatwg-fetch
                                                • GitHub - whatwg/urlpattern: URL Pattern Standard

                                                  Folks notice minor and larger issues with the URL Pattern Standard all the time and we'd love your help fixing those. Pull requests for typographical and grammar errors are also most welcome. Issues labeled "good first issue" are a good place to get a taste for editing the URL Pattern Standard. Note that we don't assign issues and there's no reason to ask for availability either, just provide a pu

                                                    GitHub - whatwg/urlpattern: URL Pattern Standard
                                                  • The WHATWG Blog — WHATWG Weekly: End of HTML5 Last Call

                                                    Please leave your sense of logic at the door, thanks! WHATWG Weekly: End of HTML5 Last Call July 25th, 2011 by Anne van Kesteren in WHATWG Next week Wednesday, August 3, the W3C HTML5 Last Call review period ends. Consider taking another look and giving some feedback! Here is a quick rundown of what happened last week: The proposed download attribute made it into the HTML specification. Specify it

                                                    • [whatwg] Annotating structured data that HTML has no semantics for

                                                      [whatwg] Annotating structured data that HTML has no semantics for Ian Hickson ian at hixie.ch Sun May 10 03:32:34 PDT 2009 Previous message: [whatwg] request for clarification: aside, figure Next message: [whatwg] Annotating structured data that HTML has no semantics for Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] One of the more elaborate use cases I collected from the e-mails

                                                      • The WHATWG Blog — The Road to HTML 5 – Episode 1: the section element

                                                        Please leave your sense of logic at the door, thanks! The Road to HTML 5 – Episode 1: the section element November 5th, 2008 by Mark Pilgrim, Google in Tutorials, Weekly Review Welcome to a new 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 element of the day is the <section> el

                                                        • ES6/WhatWG Loader & Node

                                                          ES6/WhatWG Loader & Node @BradleyMeck Node proposal Youtube video

                                                            ES6/WhatWG Loader & Node
                                                          • Video type parameters - 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 <video> element allows UA capability-based fallback with multiple alternative video resources designated by multiple <source> elements. The UA is expected to pick t

                                                            • GitHub - whatwg/streams: Streams 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. Dismiss alert

                                                                GitHub - whatwg/streams: Streams Standard
                                                              • Add goal parameter checks to JavaScript by bmeck · Pull Request #3205 · 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

                                                                  Add goal parameter checks to JavaScript by bmeck · Pull Request #3205 · whatwg/html
                                                                • The WHATWG Blog — This Week in HTML5 – Episode 36

                                                                  Please leave your sense of logic at the door, thanks! This Week in HTML5 – Episode 36 September 27th, 2009 by Mark Pilgrim, Google in Weekly Review Since I started publishing these weekly summaries over a year ago, I've watched the HTML5 specification grow up. In episode 1, the big news of the week was the birth of an entirely new specification (Web Workers). Slowly, steadily, and sometimes painst