w3c/webplatformwg

Web Platform Working Group pages

webplatformwg's Issues

Promote BackButton MediaQuery to WICG

The back button media query is a proposal to allow web applications to determine what UI controls are being displayed by the user agent.

This API is being proposed as a way to eliminate the "double back button" problem (seen here, on Twitters PWA in the Microsoft store). This problem arises because developers of "standalone", "fullscreen", and "minimal-ui" apps have no way of determining whether a back button will be provided by the user agent (the browser, OS, or hardware) but are forced to implement their own, to ensure that their app is functional without the browser's UI.

Microsoft has expressed interest in experimenting with this API (@mustjab), so I'd like to move it to WICG and get some broader feedback. @marcoscaceres @aliams @hober do you have any thoughts?

There's a (newly opened) discourse thread here.

CFC: Collect CFC responses on Github

Hello WebPlat,

This is a Call For Consensus (CFC) on the proposal to collect responses to WebPlat CFCs on Github.

We have experimented with collecting responses to WebPlat CFCs on Github, by opening an issue on the repo for the specification in question. The experiment proved successful, and at TPAC the people present at the WebPlat meeting agreed it was a good approach.

The approach would be to open a CFC issue on the Github repo for the specification, and send a notification to [email protected]. Responses on Github would be strongly encouraged, although responses sent by email would not be excluded from the CFC.

If this CFC passes we will update the WebPlat work mode accordingly.

Please respond to this CFC by end of day on Friday 7th October 2016. Positive responses (+1 on Github) are strongly preferred, but silence will be taken as implicit consent to the proposal.

CFC: Make previous versions of HTML and XHTML obsoleteCFC: Make previous versions of HTML and XHTML obsolete

This is a Call For Consensus (CFC) on the proposal to mark previous versions of HTML and XHTML obsolete.

The definition of an obsolete specification is found in section 6.1.2 of the W3C Process

"An Obsolete Recommendation is a specification that W3C does not believe has sufficient market relevance to continue recommending that the community implement it, but does not consider that there are fundamental problems that require the Recommendation be Rescinded. It is possible for an Obsolete Recommendation to receive sufficient market uptake that W3C decides to restore it to Recommendation status. An Obsolete Recommendation has the same status as a W3C Recommendation with regards to W3C Royalty-Free IPR licenses granted under the Patent Policy.">

The reason for this proposal is that these specifications are no longer recommended for implementation or use on the web platform. As older versions are superceded by new versions (as HTML5.0 has been superceeded by HTML5.1), the W3C should communicate this as clearly as possible to the web community.

The rationale for including both HTML and XHTML specifications in this CFC is that the WebPlat WG maintains specifications that include XHTML as well as HTML.

The specifications covered by this proposal are:

• HTML 3.2
• HTML 4.0
• HTML 4.0 Revised
• HTML 4.01
• HTML 5.0
• XHTML Basic
• XHTML 1.0
• Modularization of XHTML
• Module Based XHTML
• XHTML 1.0 2nd edition
• XHTML Print
• XHTML Basic 1.1
• XHTML Modularization 1.1
• XHTML Basic 1.1 2nd edition
• XHTML Modularization 1.1 2nd edition
• XHTML Print 2nd edition
• XHTML Module Based 1.1 2nd edition

Please respond to this CFC by end of day on Tuesday 18th July 2017. If you choose not to respond to this CFC it will be taken as implicit support for the proposal. Your opinion is important though, so please take time to actively respond.

TPAC agenda: Fri Nov 10 (Web Components)

This is a draft agenda. If you're a member of the WebPlat WG/Web Components, please add specific items based on the available time slots.

Please indicate attendance by adding a thumbs up to this comment.

• 9.30am: Web Components
• 10.30am: Break
• 11am: Meeting with ARIA WG:
  • Web Components + ARIA 2.0
• 12.30pm: Lunch
• 2pm: Web Components
• 3.30pm: Break
• 4pm: Web Components
• 5.30pm: Close

For Remote Participants (WebEx meeting) please see below
For IRC, use #webplat
Other WebPlat WG meetings:

• Tue Nov 7 (Editing TF): #93
• Thu Nov 9 (WebPlat general): #94

Mark ElementTraversal Rec as obsolete

As far as I can tell, https://www.w3.org/TR/ElementTraversal/ has been incorporated into newer versions of the DOM specs. Can we make it so that the TR page reflects this? (I'm not sure if this means going through the Obsolescence process or something else)

Add Web Share and Web Share Target APIs to charter

Hi,

Spinning off from w3c/das-charter#58, we would like Web Platform WG to consider adopting Web Share and Web Share Target APIs into the charter.

The Web Share API has been in WICG for a long time now, and is fairly mature. While it only has one implementation (Chrome), it had a lot of interest from other vendors, and we would like to move it onto a standards track. This adds a single new method, navigator.share, which allows a web page to trigger a share event to an arbitrary destination of the user's choice. It is up to the implementation what choices are available; typically it would go into the host OS's share system.

The companion API, Web Share Target, Web Share Target, allows sites to register to receive shared data, from Web Share but also from the host OS's share system. This API is not as far along, with a number of outstanding issues on the spec draft, and while there are prototype implementations in Chrome, nothing has been released. There is more controversy over the syntax and nature of the API, and it's generally a bit more complex. Eventually, it makes sense for WST to become part of the Manifest API, and the spec has been written with that in mind.

Therefore, I think both of these APIs are a good fit for the Web Platform WG (which also hosts the Manifest API).

Workmode document contains some formatting errors

Looks like an HTML to MD import - a few little bugs, including bolded sections, block quote sections, bullet points.

PR incoming :-)

Add Keyboard Lock and Keyboard Map to charter

Request from @garykac to add Keyboard Lock and Keyboard Map to the WebPlat WG charter.

CFC: Publish WebIDL Level 2 as a FPWD

This Call For Consensus (CFC) is to publish a First Public Working Draft (FPWD) of WebIDL Level 2, based on this draft FPWD.

Changes between WebIDL Level 1 and WebIDL Level 2 are shown in the Status section of the draft FPWD.

The intention is to point w3.org/tr/webidl to the FPWD when it is published.

Please respond to this CFC by the end of day on Friday 11th August 2017. Add a thumbs up/thumbs down, or a comment to this issue. If you choose not to respond it will be taken as silent consent to publish the FPWD of WebIDL Level 2. Your opinions are important though, so please take a minute to actively respond.

If you have technical comments on this specification, please file a Github issue.

to-be-deprecated standards market share and support in next-gen engines

Is there a comprehensive research on market share of the HTML 3.2, 4.0, 4.01 и 5.0 HTML standards?

Also current web browsers have a compatibility layer which allows rendering of non-strict documents with violations of the standard, so these renderers will be aimed to handle such violations in any mid-future HTML engine.
Of course the aim of W3C is to provide us with the specifications, but how are those specifications implemented is also has to be considered.

For the reasons mentioned, it would be great if a special document covering the differences, and limited implementation recommendation of the standards which are going to be deprecated to the current web standards would be created.

Some minor issues in index.html

In the <aside> part of index.html[1], there are some minor word wrap issues:

• "inter\nface" should be "interface"
• "speci\nal" should be "special"
• "dev\nelops" should be "develops"
• "us\ner" should be "user"

BTW, s/WebApps/WebPlatform/ in the last sentence :-)

[1]

WebPlatformWG/index.html

Lines 116 to 121 in 685a393

	<p>An Application Programming Interface (API) is a software inter
	face that exposes access to some internal functionality of a piece of software
	for use by programmers, to get access to specific information, to trigger speci
	al behavior, or to perform some other action. The APIs that the WebApps WG dev
	elops are typically client-side script APIs, for use in browsers and similar us
	er agents (as opposed to server-side APIs, for example).</p>

TPAC agenda: Tue Nov 7 (Editing TF)

This is a draft agenda. If you're a member of the WebPlat WG/Editing TF, please add specific items based on the available time slots.

If you plan to attend, please add a thumbs up to this comment.

• 9.30am:
  • Input Events level 2 vs. hidden textarea based approach as only way to handle IME [1]
  • What input events can we make cancelable also in level 1 of the Input Events spec? (a higher number of cancelable events is proposed both in Input Events level 2 and teaxtarea-approach proposal [1] point E.
  • Should we continue with plan of alternative contenteditable types? If yes, we need to figure out what to do about enabling disabling features? (see [2])
  • What attribute name should we use for feature-disabling/enabling?
• 10.30am: Break
• 11:00am:
  • inputmode [3] and inputmode-action [4] (Dave Tapuska)
  • Yoichi: Selections with mutiple ranges (non-contiguous DOM Ranges) / Alexandre: Selections with mutiple ranges (one selection in hidden textarea and another onscreen aka "Splitting apart the text selection singleton")
• 12.30pm: Lunch
• 2pm: Meeting with APA WG:
  • Input Events
• 3pm: Clipboard API:
  • Async API for images (to allow the generation of clipboard content to be delayed)
  • Image formats for API (see clipboard/44)
  • other mimetypes
• 3.30pm: Break
• 4pm:
  • Alexandre: Touch text selection “blue handles”
  • Alexandre: Floating action bar
  • Alexandre: Onscreen keyboard show/hide
  • Alexandre: Spellcheck and composition underlines
  • Alexandre: IME dropdown menu positioning
• 6.00pm: Close

For Remote Participants (WebEx meeting) see below

Other WebPlat meetings:

• Thu Nov 9 (WebPlat general): #94
• Fri Nov 10 (Web Components): #95

[1] https://docs.google.com/document/d/10qltJUVg1-Rlnbjc6RH8WnngpJptMEj-tyrvIZBPSfY/edit
[2] https://www.w3.org/2016/09/22-webapps-minutes.html#item16
[3] https://cdn.rawgit.com/dtapuska/inputmode/HEAD/index.html
[4] https://cdn.rawgit.com/dtapuska/action-hint/HEAD/index.html

Need PAG for "Web Components vs Extract Widget patent"?

This is a placeholder for W3C staff (@ylafon @siusin @plehegar @wseltzer) re the "Web Components vs Extract Widget patent" issue that was first raised in public-webapps in May 2015 https://lists.w3.org/Archives/Public/public-webapps/2015AprJun/0692.html

Is a Patent Advisory Group needed for this? If yes, when will it be created?

TPAC agenda: Thu Nov 9 (WebPlat general)

This is a draft agenda. If you're a member of Web Platform please request changes by posting a comment.

Please indicate attendance by adding a thumbs up to this comment.

• 9.30am: HTML (45 mins)
• 10.15am: Workers (15 mins)
• 10.30am: Break
• 11am: Meeting with WICG (60 mins):
  • Asynchronous JavaScript Cookies API and Cookie Change Events
  • Accessibility Object Model (AOM)
  • File/Directory Entries API
• 12pm: Screen Orientation API (15 mins)
• 12.15pm: IndexedDB API (15 mins)
• 12.30pm: Lunch
• 2pm: Intersection Observer (30 mins)
• 2.30pm: Pointer Lock 2.0 (30 mins)
• 3pm: UI Events (30 mins)
• 3.30pm: Break
• 4pm: Web App Manifest (15 mins)
• 4.15pm: WebIDL Level 2 (15 mins)
• 4.30pm: Gamepad API (30 mins)
• 5pm: TBC
• 5.30pm: Close

For Remote Participants (WebEx meeting) please see below

Other WebPlat meetings:

• Tue Nov 7 (Editing TF): #93
• Fri Nov 10 (Web Components): #95

Update work mode

We might want to update the work mode to encourage a "not tests, not merge" policy.

F2F Agenda Item - Dragging and dropping

What should the order of the events be and in what spec should this be placed?

Move uievents meeting minutes data from w3c wiki to Github

The uievents/D3E group maintains a meeting minutes wiki at the W3C and since WPWG doesn't use that wiki, the relevant data should be moved to the uievents repo.

@garykac @travisleithead - please take care of this or let us know what you want done and we'll find someone to do it.

Add the User Input of Mathematics to Charter

Web Platform Working Group,

For your consideration, I would like to indicate an opportunity to add the user input of mathematics as a new Working Group deliverable.

As envisioned, group discussion topics would include: (1) hypertext document markup for providing users with mathematical and notational user input, (2) mathematical and notational user input scenarios pertaining to forms and to contenteditable content, (3) a JavaScript API for utilization of and interoperation with mathematical and notational user input controls provided by websites, browsers, operating system platforms and third-party software vendors.

Input modalities of mathematical and notational user input controls include keyboard and mouse, handwriting recognition and speech recognition. The JavaScript API envisioned would encompass providing such user input controls with contextual recognition hints and obtaining resultant data, expressions and graphics.

In the course of our discussion at the WICG, we considered that implementers included the implementers of such user input controls. One such implementer, Wiris, presented some issues which were addressed throughout the remainder of the discussion.

The user input of mathematics is an important topic. The user input of mathematics facilitates scholarly and scientific communication as well as education, providing for new varieties of science, technology, engineering and mathematics exercises and activities.

Thank you for considering the user input of mathematics as a new Working Group deliverable.

Retire HTML Imports WD

HTML Imports was last published as Working Draft in 2016, and support for it was removed in Chrome in February 2020. This suggests the spec should be retired and republished as a WG Note.

Make XPathResult (returned by document.evaluate(...)) iterable

This will make for (let x of document.evaluate(...)) possible instead of the current pseudo old-school non-ECMAScript-compatible iterator that XPathResult currently is.

A basic and probably incomplete polyfill -
https://github.com/phistuck/monorail-enhancer-extension/blob/9e6b0b645d2df97b2e6717a35712a0d6b6229532/injector.js#L12-L29

CFC: Mark View-Mode Media Feature Obsolete

This is a Call For Consensus (CFC) to mark View-Mode Media Feature Obsolete.

The View-Mode specification is maintained by the Web Platform WG. It was not implemented in browsers, only in widget engines. View-Mode Media Feature is part of the Widget Specs, which the TAG has marked for Obsoletion.

The term "Obsolete" is defined in the W3C Process:

"W3C may obsolete a Recommendation, for example if the W3C Community decides that the Recommendation no longer represents best practices, or is not adopted and is not apparently likely to be adopted. An Obsolete Recommendation may be restored to normal Recommendation, for example because despite marking it Obsolete the specification is later more broadly adopted.">

If you agree that View-Mode Media Feature should be marked Obsolete, please post a "thumbs up" reaction to this comment. If you disagree, please post a "thumbs down" reaction to this comment, and give your reasons in the comments.

If you do not respond, it will be taken as silent agreement with the proposal to mark View-Mode Media Feature Obsolete. Actual responses are preferred however.

Please respond to this CFC by the end of day on Friday 3rd August 2018.

Different ways to run a CFC?

Calls For Consensus (CFC) are traditionally handled on the official email for the WG in question. It is possible that other ways to run a CFC are more efficient/easier/preferable/delete as applicable... Thoughts?

Agendas: TPAC 2018

Agendas for the Web Platform WG meetings at TPAC 2018, on Monday 22 and Friday 26 October, plus the Editing TF (Task Force) meeting on Tuesday 23 October and Web Components meeting on Thursday 25 October.

Monday October 22

Room: Rhône 2, Level 1 - Rhône Pasteur
Web Platform WG Day 1 minutes

• 9.30AM: Welcome and housekeeping
• 9:45AM: Intersection Observer (Stefan Zager):
  • w3c/IntersectionObserver#95
• 10.00AM: UI Events (Gary Kacmarcik):
  • I18n issues
  • Merging WICG - Keyboard Map and Keyboard Lock
  • Dividing Keyboard Events Code Values and Keyboard Events Key Values into Levels
  • Updating UI Events to include procedural algorithms
  • Special handling for AltGraph on Windows
• 11AM: Break
• 11.30AM: DOM Parsing and Serialization (Travis Leithead)
• 12PM: IndexedDB 3.0 (Daniel Murphy):
  • IndexedDB.databases()
  • Transaction commit()
  • IndexedDB Observers
  • WICG - lifecycle integration
  • async local storage
• 12:45PM: Lunch
• 2.15PM: Meeting with APA WG (Janina Sajka):
  • Personalization Semantics
• 3PM: WICG - Cookie Store (Marijn Kruisselbrink)
• 3.30PM: WICG - Web Locks API (Ben Kelly)
• 4PM: Break
• 4.30PM: Web Locks overflow
• 5.00 PM: requestAnimationFrame timing
• 5.30PM: Meeting ends

Tuesday October 23 (Editing TF)

Room: Saint Clair 3A, Level 2 - Saint-Clair
Editing TF minutes

• 9.30AM: Welcome and housekeeping
• 9.45AM: Clipboard API and Events (Gary Kacmarcik):
  • Additional clipboard mime types
  • Mime types to support directly
  • Image and delayed content generation proposal
  • DataTransfer for clipboard data
  • "Pickled" format for browsers
• 11AM: Break
• 11.30AM: Input Events I18n issues
• 12PM: contenteditable-disabled DOM API attribute (johannes Wilm):
  • w3c/editing#176
• 12.45PM: Deprecate document.designMode (Johannes Wilm):
  • w3c/editing#177
• 1PM: Lunch
• 2.30PM: Apply text transformation on copy (Johannes Wilm):
  • w3c/editing#178
• 3PM: Adding custom menu items to editing context menus (Johannes Wilm):
  • w3c/editing#176
• 3.45PM: Editing UI on mobile (Piotr Koszulinski).
• 4PM: Break
• 4.30PM: Range plus selection decorations (Piotr Koszulinski):
  • w3c/editing#166
• 5PM: Accessibility Object Model (AOM) (Gary Kacmarcik):
  • AOM input event types
  • Where should the AOM input event types spec live?
  • Moving the IDL (and only the IDL) for inputType from Input Events into UI Events
• 5.30PM: Meeting ends

Thursday October 25 (Web Components)

Room: Lumière Lounge, Level -1 - Lumière |   | 1
Web Components Contributors minutes

• 9.30AM: Welcome and housekeeping
• 9.45AM: Web Components TBC
• 11AM: Break
• 11.30AM: Web Components TBC
• 1.30PM: Meeting ends

Friday October 26

Room: Forum 2, Level -2 - Forums
Web Platform WG Day 2 minutes

• 9.30AM: Welcome and housekeeping

• 9.45AM: Push API (Peter Beverloo)

• 10AM: Web App Manifest - agenda (Matt Giuca)

• 10:15AM: WebPlat WG:

  • Test driven spec develoPMent
  • Working better together

• 11AM: Break

• 11.30AM: WICG - Writable Files (Marijn Kruisselbrink)

• 12PM: WICG - Web Share and WICG - Web Share Target (Eric Willigers, Matt Giuca)

• 12.30PM: WICG - Badging Web API (Matt Giuca)

• 1PM: Lunch

• 2PM: Gamepad API (Steve Agoston):

  • Taking v1 to Recommendation
  • v2 roadmap and extensions

• 2.30PM: Web Components (Ryosuke Niwa):

• 4PM: Break

• 4.30PM: Web Components (continued) (Ryosuke Niwa):

• 5.30PM: Meeting ends

Meeting logisttics

IRC channel: #webplat on the irc.w3.org webserver. There is a web-based client at https://irc.w3.org

Remote dial-in info (W3C member-only. Ping on IRC for help getting it)

I support the proposal to mark previous versions of HTML as obsolete.

This is an important accessibility issue, because of the improvements with each version.

[Feature Request] pause/resume webdriver

From this issue in Selenium: SeleniumHQ/selenium#5269
@p0deje said that it has to be implemented in drivers and is outside of Selenium, and that the right place to file the issue was in the wevdriver specs. But then I saw that IndieUI is deprecated now and WebPlataformWG has taken the role of IndieUI Events, so I think that the right place to file the issue is here.

So we need to add a Event to pause/resume the execution of the website, everything from JS to HTML requests, to DOM loading.

Update some links

Hi,

It seems that the revised charter has been approved.

So, (at least) links to the charter in these files needs updating:

• https://github.com/w3c/WebPlatformWG/blame/33ff3b2f335d94afdb46ae83d433be8bf4098643/README.md#L3
• https://github.com/w3c/WebPlatformWG/blob/c11c65abb14d207a013332518e5ba5b65f0c39a3/WorkMode.md

Moreover, the FindText API was removed from the charter, so the following section can be removed: https://github.com/w3c/WebPlatformWG/blob/e1149040e6fd8d39899220ed7ca2fdda698ea90a/Coordination.md#web-annotations-wg

BTW, the "Git repositories" link in WorkMode.md[1] seems to be 404. (Or perhaps it is only visible to Group Members?)

[1] https://github.com/w3c/WebPlatformWG/blob/c11c65abb14d207a013332518e5ba5b65f0c39a3/WorkMode.md#bugs-issues-and-actions

Promote File Handling to WICG

The File Handling proposal was briefly discussed at TPAC.

The proposal would be useful for online image manipulations tools, computer aided design tools and document editors.

We would like to refine this proposal in the context of WICG. Contributions and feedback from other browser vendors would be much appreciated (e.g. @marcoscaceres @aliams @hober do you have any thoughts?).

Publish First Public Working Draft for HTML 5.2?

This is (part of) a Call for Consensus, on the proposition:
Publish the current editors draft of HTML 5.2 as a W3C First Public Working Draft.

Feel free to add a thumbs-up here, or leave a comment, especially if you object to the proposal, up to and including 14 July 2016.

CFC to publish WebIDL-1 as a Proposed Recommendation

This is a Call For Consensus (CFC) to publish WebIDL-1 as a Proposed Recommendation (PR) [1].

Some editorial changes were made to the specification during the Candidate Recommendation (CR) period, but none that affects conformance. The CR implementation
report has the detail.

We are still exploring different ways of responding to a CFC. Please choose one of the following methods:

1. Reply by email to the thread (on [email protected]).
2. +1/-1 or comment on this issue.

There is no need to use more than one method. The WP chairs will collate the results across all channels.

Please respond by end of day on Monday 22nd August. Positive responses are encouraged, but silence will be taken as consent with the proposal.

Broken Link on Web Platform Publication Status (PubStatus) web page

The "Latest TR Publication" link for HTML5.2 is broken on the PubStatus.html page.

Specifically, line # 77 reads as:

<td><a href=https://www.w3.org/TR/html52/">2017-01-17</a></td>

and should be changed to:

<td><a href="https://www.w3.org/TR/html52/">2017-01-17</a></td>

Gamepad-Lock API

Edge is coming to Xbox One. The gamepad-API supports gamepads (and other HIDs) in browsers.

Ordinarily there are no browser actions assigned to gamepads, and so users of the gamepad API are free to use all inputs on these devices.

But on platforms that primarily interact with the browser trough gamepads, there is a problem, most of the inputs are assigned to browser actions (clicking, navigation, back, forward, etc.). In that situation, the gamepad API could not sensibly be supported because most inputs on a gamepad couldn't be used (and this conflict would probably lead UA-vendors to skip on that API).

Should there be a gamepad-lock api analogous to how there is a pointerlock-api?