The WHATWG Blog

本頁 50 篇

• Staged proposals at the WHATWG

  • #WHATWG

  The WHATWG's living standards incorporate new features on an ongoing basis. The default process is to propose an idea on the relevant standard's issue tracker, hash out the details and gather implementer interest, and then work together with the editors to land a pull request. However, we've found that for larger features, or for community […]

  2025/4/28 13:45Domenic Denicolahttps://blog.whatwg.org/staged-proposals-at-the-whatwg

• The URL Pattern Standard

  • #WHATWG
  • #What's Next

  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 […]

  2023/10/25 13:30Domenic Denicolahttps://blog.whatwg.org/url-pattern-standard

• Retro-specifying fetch/performance

  • #Processing Model

  In the last year or so, my main task was to tackle some of the "specification technical debt" that had been accumulating over a few years, specifically at the crossroads of Fetch, performance APIs, and the HTML Standard. Monkey patching and hand waving When starting this work, the behaviors of some of the features relating […]

  2022/3/18 00:07Noam Rosenthalhttps://blog.whatwg.org/retro-specifying-fetch-performance

• New Living Standards

  • #WHATWG
  • #What's Next

  The last time we introduced a new Living Standard was Infra, in 2016. This year has seen a flurry of activity, with four new standards joining the WHATWG! The Web IDL Standard defines the interface language and JavaScript mapping for all web platform APIs. It migrated to the WHATWG from its old location, on the […]

  2021/12/2 03:25Domenic Denicolahttps://blog.whatwg.org/new-living-standards-2021

• Newline normalizations in form submission

  • #forms
  • #Browsers
  • #WHATWG

  In form submissions, form values containing newlines get normalized to CRLF. But that newline normalization runs deeper than might be thought. Here is a deep dive on the recent spec changes on that area.

  2021/5/27 23:05Andreu Botellahttps://blog.whatwg.org/newline-normalizations-in-form-submission

• Update from the Steering Group

  • #WHATWG

  A couple things the Steering Group has been working on recently reached a new milestone and seemed noteworthy enough to highlight to the wider WHATWG community. As you may know the WHATWG formally collaborates with W3C on the DOM and HTML standards. In practice there is also a significant overlap in membership and sharing of […]

  2021/4/29 14:41Anne van Kesterenhttps://blog.whatwg.org/update-from-the-steering-group

• Considering accessibility

  • #Accessibility
  • #Elements
  • #aria

  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 […]

  2020/1/22 05:00Carolyn MacLeodhttps://blog.whatwg.org/considering-accessibility

• Focusing on focus

  • #forms
  • #Processing Model
  • #Browser API
  • #DOM

  Focus behavior in HTML had been under-specified for the past few years, and it was also quite confusing due to a variety of subtle differences between focusing methods, UA-specific behaviors, relation to the tabindex attribute, relations to shadow DOM, etc. A few months ago Domenic filed a meta-bug that contains a list of things to […]

  2019/10/16 16:09Rakina Zata Amnihttps://blog.whatwg.org/focusing-on-focus

• The state of fieldset interoperability

  • #forms
  • #Browsers
  • #WHATWG

  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. […]

  2018/9/19 22:00Simon Pietershttps://blog.whatwg.org/the-state-of-fieldset-interoperability

• First set of Review Drafts published

  • #WHATWG

  (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 […]

  2018/6/22 00:59Domenic Denicolahttps://blog.whatwg.org/first-review-drafts

• Changing the copyright license for Living Standards

  The recent changes to the WHATWG are designed to help the web-standards development community work together across the broadest possible spectrum of developers, implementers, and end-users. As part of this change, we decided to move our standards from being licensed under the CC0 public domain dedication to the CC BY license. This decision was not […]

  2017/12/14 01:00Anne van Kesterenhttps://blog.whatwg.org/copyright-license-change

• Further working mode changes

  The WHATWG has been going great since it began in 2004, but without participation from all the browser engine implementers, was only partially meeting its goals. Over the last year, engineers and attorneys from the organizations behind Blink, Edge, Gecko, and WebKit have worked together to find a way forward that works for all the […]

  2017/12/12 00:00Anne van Kesterenhttps://blog.whatwg.org/working-mode-changes

• Progressing Streams

  Back in 2014 we announced the Streams Standard. It's about time for an update on where we are and what's coming up. Streaming the response to fetch() via the response.body attribute was standardized last year and is now implemented in several major browsers. Recently streaming uploads have been added to the Fetch Standard. fetch(url, {method: […]

  2017/7/5 22:00Adam Ricehttps://blog.whatwg.org/progressing-streams

• The Developer’s Edition of HTML makes a comeback

  Back in 2011, Ben Schwarz took on the ambitious project of curating an edition of the HTML Standard specifically for web developers. It omitted details aimed specifically at browser vendors, and had several additional features to make the experience more pleasant to read. Ben did an amazing job maintaining this for many years, but some […]

  2017/6/28 08:20Domenic Denicolahttps://blog.whatwg.org/developers-edition-comeback

• HTML and shared memory

  You’d think that the HTML Standard would be pretty far removed from shared memory considerations, but as it happens HTML defines a parser for HTML which is intertwined with script execution, defines a way to instantiate new global objects through the iframe element, defines a way to instantiate new threads (and even processes, depending on […]

  2017/4/28 17:20Anne van Kesterenhttps://blog.whatwg.org/html-and-shared-memory

• Working mode

  In a previous post we’ve already explained how interoperability is important to the WHATWG. Without it, we’re writing fiction, and in the world of standards that is no good. From a similar perspective, we’ve now more clearly documented how the WHATWG creates standards. The Working Mode document describes what is expected of editors and contributors, […]

  2017/4/25 17:30Anne van Kesterenhttps://blog.whatwg.org/working-mode

• Improving interoperability

  The goal of the WHATWG’s Living Standards is to achieve interoperable implementations. With an ever-evolving web platform, we want changes to our standards to reach all implementations quickly and reliably, but from time to time there have been mishaps: Two table-related interfaces were ignored by implementers for a decade, but when finally removed from the […]

  2017/1/30 22:50Philip Jägenstedthttps://blog.whatwg.org/improving-interoperability

• Infra

  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 the low-level functionality and put it one place. […]

  2016/11/17 01:21Anne van Kesterenhttps://blog.whatwg.org/infra

• DRM and Web security

  For a few years now, the W3C has been working on a specification that extends the HTML standard to add a feature that literally, and intentionally, does nothing but limit the potential of the Web. They call this specification "Encrypted Media Extensions" (EME). It's essentially a plug-in mechanism for proprietary DRM modules. Much has been […]

  2016/9/22 06:55Ian Hicksonhttps://blog.whatwg.org/drm-and-web-security

• Sunsetting the JavaScript Standard

  Back in 2012, the WHATWG set out to document the differences between the ECMAScript 5.1 specification and the compatibility and interoperability requirements for ECMAScript implementations in web browsers. A specification draft was first published under the name of “Web ECMAScript”, but later renamed to just “JavaScript”. As such, the JavaScript Standard was born. Our work […]

  2016/8/16 03:21Mathias Bynenshttps://blog.whatwg.org/javascript

• Defining the WindowProxy, Window, and Location objects

  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 specifying previously-unspecified behavior, reverse-engineering and precisely documenting the de-facto requirements for a web-compatible browser. Nevertheless, there are […]

  2016/5/12 23:10Anne van Kesterenhttps://blog.whatwg.org/windowproxy-window-and-location

• Adding JavaScript modules to the web platform

  One thing we’ve been meaning to do more of is tell our blog readers more about new features we’ve been working on across WHATWG standards. We have quite a backlog of exciting things that have happened, and I’ve been nominated to start off by telling you the story of

  2016/4/14 00:23Domenic Denicolahttps://blog.whatwg.org/js-modules

• Standards development happening on GitHub

  (This post is a rough copy of an email I sent to the mailing list.) I wanted to remind the community that currently all WHATWG standards are being developed on GitHub. This enables everyone to directly change standards through pull requests and start topic-based discussion through issues. GitHub is especially useful now that the WHATWG […]

  2016/2/1 20:14Anne van Kesterenhttps://blog.whatwg.org/github

• HTML Standard now more community-driven

  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 have landed one or more patches, and have merged over 250 pull requests in total. That’s almost […]

  2016/1/25 22:35Anne van Kesterenhttps://blog.whatwg.org/html-standard-now-more-community-driven

• Streams

  We're happy to announce the addition of the Streams Standard to the list of specs maintained by the WHATWG! Streaming data shows up all over the web platform, and this new spec gives us a set of APIs for creating and interfacing with that data. We hope that streams will be a unifying primitive for […]

  2014/10/31 01:04Domenic Denicolahttps://blog.whatwg.org/streams

• Rolling out TLS and HSTS

  All whatwg.org and html5.org domains, including subdomains, are now available over TLS. We are also enabling HSTS though this is not done everywhere just yet. If you find Mixed Content issues be sure to let us know or provide a pull request on GitHub. Update: TLS and HSTS are now deployed everywhere on both domains. […]

  2014/9/15 16:54Anne van Kesterenhttps://blog.whatwg.org/rolling-out-tls-and-hsts

• Make patent commitments for the URL standard

  The WHATWG is starting down the road of getting patent commitments for its standards. You can be part of this! First, create an account with the W3C's community group system. Then, join the WHATWG community group. Then make the patent commitment by following the instructions on this page (pick the first radio button, then click […]

  2014/9/3 00:01Ian Hicksonhttps://blog.whatwg.org/make-patent-commitments

• CSS Books & CSS Figures

  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, and most other things needed to present books on screen or […]

  2013/10/14 09:03Håkon Wium Liehttps://blog.whatwg.org/css-books-css-figures

• Relationship update on HTML Living Standard and W3C HTML5

  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 on improving HTML and related technologies to address the needs of users, developers, and […]

  2012/7/20 16:03Anne van Kesterenhttps://blog.whatwg.org/html-and-html5

• Validator.nu HTML Parser 1.4 Available

  A new release of the Validator.nu HTML Parser is available. The new version 1.4 contains minor adjustments to spec compliance and fixes for notable Java-specific problems (of the crash and infinite loop sort). Also, the parser is again available from the Maven Central Repository (groupId: nu.validator.htmlparser, artifactId: htmlparser, version: 1.4). Upgrading to the newest version […]

  2012/6/8 21:14Henri Sivonenhttps://blog.whatwg.org/vnu-parser-1-4

• The Future of the Web: My Vision (May 23, 2012)

  I apologize for the longer than expected wait for this article, but now, we may continue. The article below will pick up where Part 1 left off. Article 1: Websites and SectioningPart 2: Styling Warning: This article discusses the topic of semantics As we began with previously, we now have the basics down as to […]

  2012/5/24 04:48Christopher Brighthttps://blog.whatwg.org/the-future-of-the-web-my-vision-may-23-2012

• The Future of the Web: My Vision (May 1, 2012)

  Like probably many others who read this blog, I am a web design enthusiast, web standards advocate, and web designer by trade. I have been working with HTML since the early 2000s, and have enjoyed it ever since. Over the years, the web has evolved around me. I have watched it grow and adapt. And […]

  2012/5/2 02:15Christopher Brighthttps://blog.whatwg.org/the-future-of-the-web-my-vision-may-1-2012

• Patent Policy

  The WHATWG now has a patent policy, the WHATCG. We will keep using the same mailing list, the same IRC channel, the same web sites, but now sometimes we will publish through the WHATCG as well for patent policy purposes per the W3C Community Final Specification Agreement. If you could previously not join the WHATWG […]

  2012/4/24 15:03Anne van Kesterenhttps://blog.whatwg.org/patent-policy

• WHATWG Weekly: Fullscreen dialog

  Ian Hickson made a proposal to unify Web Intents with registerProtocolHandler() and registerContentHandler(). The Encoding Standard now has all its decoders defined. This is the WHATWG Weekly. The big news this week is the new dialog element. Introduced in revision 7050, along with a new global attribute called inert, a new form element method attribute […]

  2012/4/11 21:53Anne van Kesterenhttps://blog.whatwg.org/weekly-fullscreen-dialog

• WHATWG Weekly: HTML canvas version 5 has arrived

  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 may turn out that the web platform will only work on little-endian devices, as […]

  2012/3/29 23:20Anne van Kesterenhttps://blog.whatwg.org/weekly-canvas-v5

• WHATWG Weekly: Path objects for canvas and creating paths through SVG syntax

  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-March WHATWG Weekly. Revision 7023 added the Path object to HTML for use with the canvas element, and the next revision made it possible […]

  2012/3/14 20:09Anne van Kesterenhttps://blog.whatwg.org/weekly-canvas-path

• WHATWG Weekly: http+aes URL scheme, control Referer, …

  Apple's Safari team provided feedback to the Web Notifications Working Group. That group, incidentally, is looking for an active editor to address that and other feedback. Opera Mobile shipped with WebGL support. This is March's first WHATWG Weekly. Simon Pieters overhauled much of HTML5 differences from HTML4 and the document now provides information on added/changed […]

  2012/3/7 19:42Anne van Kesterenhttps://blog.whatwg.org/httpaes-url-scheme

• WHATWG Weekly: New canvas API goodies

  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 method is part of the window.crypto proposal. Ian Hickson has been busy […]

  2012/3/1 00:01Anne van Kesterenhttps://blog.whatwg.org/weekly-canvas-goodies

• WHATWG Weekly: Unicode for the platform?

  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) and the WebApps WG to coordinate development of JavaScript, IDL, and APIs, Brendan Eich launched a […]

  2012/2/22 19:24Anne van Kesterenhttps://blog.whatwg.org/weekly-platform-unicode

• WHATWG Weekly: Quirks Mode and Error Recovery for XML

  Quirks Mode has its first public draft and a group working on XML Error Recovery just started. This is the WHATWG Weekly. Simon Pieters published a first draft of the Quirks Mode Standard. This should help align implementations of quirks mode and reduce the overall number of quirks implementations currently have. In other words, making […]

  2012/2/15 19:41Anne van Kesterenhttps://blog.whatwg.org/weekly-quirks-mode-xml

• WHATWG Weekly: translate attribute and other changes to HTML

  Since the last WHATWG Weekly, almost a month ago now, over a hundred changes have been committed to the HTML standard. This is the WHATWG Weekly and it will cover those changes so you don’t have to. Also, remember kids, that fancy email regular expression is non-normative. translate attribute To aid translators and automated translation […]

  2012/2/7 22:26Anne van Kesterenhttps://blog.whatwg.org/weekly-translate-attribute

• WHATWG Weekly: Happy New Year!

  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. I will be taking the remainder of the month off […]

  2012/1/9 23:52Anne van Kesterenhttps://blog.whatwg.org/happy-2012

• WHATWG Weekly: Shadow DOM and more encoding fun!

  You might have missed this. Because of this lengthy thread on throwing for atob() space characters will no longer cause the method to throw from revision>6874 onwards. This is the WHATWG Weekly, with some standards related updates just before the world slacks off to feast and watch reindeer on Google Earth. Shadow DOM Dimitri Glazkov […]

  2011/12/21 21:33Anne van Kesterenhttps://blog.whatwg.org/weekly-shadow-encoding-fun

• WHATWG Weekly: Stream API and better autocomplete

  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 appeared on the WHATWG Wiki, apparently already experimentally implemented in Chrome (prefixed). It proposes a new autocompletetype […]

  2011/12/15 17:44Anne van Kesterenhttps://blog.whatwg.org/weekly-stream-autocomplete

• WHATWG Weekly: Encoding woes and WebVTT

  If you want to contribute to the WHATWG Blog or Wiki, join IRC (#whatwg on Freenode). We had to shut down user registration unfortunately due to excessive spam. Welcome to another WHATWG Weekly. If it were themed, this would be about Sinterklaas. Encoding problem In response to Faruk Ate?' plea for defaulting to UTF-8, David […]

  2011/12/5 19:58Anne van Kesterenhttps://blog.whatwg.org/weekly-encoding-woes

• WHATWG Weekly: Subscribe to the specification & XMLHttpRequest merger

  Next to @WHATWG, we now have +WHATWG. Hopefully ?WHATWG is next. Not to dispair, WHATWG Weekly will remain right here, without funny characters preceding it. HTML is big, so follow what interests you! Ian Hickson announced a new system on the mailing list that allows people to subscribe to specific sub-topics in the HTML specification, […]

  2011/11/30 20:04Anne van Kesterenhttps://blog.whatwg.org/weekly-xmlhttprequest-merger

• WHATWG Weekly: <time> police!

  You can now put a fullscreen in your fullscreen. Brought to you by Fullscreen. This is the WHATWG Weekly, not quite weekly, but you are still welcome. police Revision 6827 introduced the new time element. The one that also allows for years, yearless dates, durations, and so on. It is based on extensive research […]

  2011/11/21 19:25Anne van Kesterenhttps://blog.whatwg.org/weekly-time-police

• WHATWG Weekly: TPAC 2011

  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. and again The time element comes back and its new design […]

  2011/11/11 00:49Anne van Kesterenhttps://blog.whatwg.org/weekly-tpac-2011

• WHATWG Weekly: Now it’s <time> for <data>

  Revision 6695 made HTML attribute values match in a case-sensitive manner as far as Selectors are concerned. This approach was favored over having a hardcoded list of HTML attributes whose values had to be matched case-insensitively. Revision 6701 removed selectedOptions from the input element, a vestige from the Web Forms 2.0 era. Welcome to the […]

  2011/10/29 15:25Anne van Kesterenhttps://blog.whatwg.org/weekly-time-data

• WHATWG Weekly: Fullscreen

  Should we introduce an isWhiteSpace attribute for Text nodes, and if we do, what would you use it for? Anyway, WHATWG Weekly, brief one this week. Fullscreen The big news last week was renewed activity on Gecko:FullScreenAPI, a proposal by Robert O'Callahan to make fullscreen work for the platform. Yours truly made an initial attempt […]

  2011/10/18 16:45Anne van Kesterenhttps://blog.whatwg.org/weekly-fullscreen