はてなブックマーク

Post-Spectre Web Development Editor’s Draft, 19 July 2021 This version: https://w3c.github.io/webappsec-post-spectre-webdev/ Latest published version: https://www.w3.org/TR/post-spectre-webdev/ Previous Versions: https://www.w3.org/TR/2021/WD-post-spectre-webdev-20210316/ Feedback: public-webappsec@w3.org with subject line “[post-spectre-webdev] … message topic …” (archives) Issue Tracking: GitHub

This document describes requirements for general Japanese layout realized with technologies like CSS, SVG and XSL-FO. The document is mainly based on a standard for Japanese layout, JIS X 4051, however, it also addresses areas which are not covered by JIS X 4051. This version integrates errata and links to related materials. この文書は，CSS，SVGおよびXSL-FOなどの技術で実現が求められる一般的な日本語組版の要件を記述したものです．この文書は，主としてJIS X

This document serves as an official registry for all known global parameters, properties, and values used by the Decentralized Identifier ecosystem. This registry is under active development and implementers are advised against using the registry unless they are directly involved with the W3C DID Working Group. Comments regarding this document are welcome. Please file issues directly on GitHub, or

Decentralized identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity. A DID refers to any subject (e.g., a person, organization, thing, data model, abstract entity, etc.) as determined by the controller of the DID. In contrast to typical, federated identifiers, DIDs have been designed so that they may be decoupled from centralized registries, identi

This specification defines an API for sharing text, links and other content to an arbitrary destination of the user's choice. The available share targets are not specified here; they are provided by the user agent. They could, for example, be apps, websites or contacts. Implementation status The ability to share content is often dependent on the underlying operating system providing a "share" capa

WebDriver W3C Editor's Draft 16 April 2024 More details about this document This version: https://w3c.github.io/webdriver/ Latest published version: https://www.w3.org/TR/webdriver2/ Latest editor's draft:https://w3c.github.io/webdriver/ History: https://www.w3.org/standards/history/webdriver2/ Commit history Test suite:https://wpt.live/webdriver/ Implementation report: https://wpt.fyi/results/web

UI Events Testing Tools Keyboard Event Viewer UserAgent: input element with type="text": Show Options

This document defines a set of ECMAScript APIs in WebIDL to allow data to be sent and received from another browser or device implementing the QUIC protocol. This specification is being developed in conjunction with a protocol specification developed by the IETF QUIC Working Group. Introduction This specification extends the WebRTC [[WEBRTC]], ORTC [[ORTC]] and WebTransport [[WEBTRANSPORT]] specif

Near Field Communication (NFC) enables wireless communication between two devices at close proximity, usually less than a few centimeters. NFC is an international standard (ISO/IEC 18092) defining an interface and protocol for simple wireless interconnection of closely coupled devices operating at 13.56 MHz. The hardware standard is defined in [[[NFC-STANDARDS]]]. This document defines an API to e

This Note provides historical and instructional context for developers working with Cross-Origin Resource Sharing (CORS) and the CORS-mode of Fetch. this whole document needs references and terms linkified 1. Introduction One of the defining characteristics of a Web application is the way in which resources can link and communicate with each other. Over time, as browsers have evolved and become mo

This report outlines known implementations for the features added between HTML 5.0 and HTML 5.1. Implementation information is documented in the relevant Github issue, Pull Request (PR), or documentation for developers. Documented changes New features BlinkFirefox - GeckoEdgeInternet ExplorerSafari - WebkitNotes HTMLInputElement.reportValidity()

SVG is a generalized graphics markup language, which can be used for any purpose from icons to complex images to data visualizations to animated pictures to interactive applications. SVG can be generated by script libraries, by GUI drawing applications, or by hand-coding. Because of this flexibility, SVG does not dictate a structured content model, though it does provide primitives for structure,

Moved to https://immersive-web.github.io/webvr/

Payment Request API This specification standardizes an API to allow merchants (i.e. web sites selling physical or digital goods) to utilize one or more payment methods with minimal integration. User agents (e.g., browsers) facilitate the payment flow between merchant and user. In September 2022 the Web Payments Working Group published a Payment Request Recommendation. Following privacy and interna

Useful links Review comment issues Document issue tracker Open actions Use this page to track projects that we are actively working on. For each work item, the page describes objectives as well as useful links and contact names. Bring together experts, analyse gaps, and document requirements for support of text layout and local conventions. For languages using the scripts listed below, identify an

This document defines how a user's display, or parts thereof, can be used as the source of a media stream using {{MediaDevices/getDisplayMedia}}, an extension to the Media Capture API [[GETUSERMEDIA]]. This document is not complete. It is subject to major changes and, while early experimentations are encouraged, it is therefore not intended for implementation. Introduction This document describes

Authors Tzviya Siegman (Wiley) & Robin Berjon, @robinberjon (science.ai) Bugs & Feedback Issues and PRs welcome! Discussion Group The Scholarly HTML Community Group at W3C (email archives) License CC-BY Abstract Scholarly HTML is a domain-specific rich document format built entirely on open standards that enables the interoperable exchange of scholarly articles in a manner that is compatible with

This version: https://w3c.github.io/webappsec-referrer-policy/ Latest published version: http://www.w3.org/TR/referrer-policy/ Version History: https://github.com/w3c/webappsec-referrer-policy/commits/main/index.src.html Feedback: public-webappsec@w3.org with subject line “[REFERRER-POLICY] … message topic …” (archives) GitHub Inline In Spec Editor: Dominic Farolino (Google Inc.) Former Editors: E

Many W3C work groups conduct their work in Github, but not all. Please, explore our repos, watch, star, contribute. The purpose of this page is to progressively list the resources useful when working on W3C projects using GitHub. The following links should help you find your way. Refer to the FAQ for details about the breadth and scope of W3C projects. Repositories If you are looking for a specifi

Web Editing Working Group Welcome to the GitHub repository of the Web Editing Working Group (formerly Editing Task Force of the Web Apps Working Group). Its mission is to gather and incubate emerging ideas as they pertain to rich text editor development. Details can be found in the Web Editing Working Group Charter. Actively developed ideas/specs Clipboard APIs (Github Repo) Input Events (Github R

Moved to https://w3c.github.io/input-events/