Platform/Features/WebsocketsUnprefix

From MozillaWiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Please use "Edit with form" above to edit this page.

Status

Unprefixing WebSockets
Stage Complete
Status Complete
Release target `
Health OK
Status note Lots of small stuff left to do here.

{{#set:Feature name=Unprefixing WebSockets

|Feature stage=Complete |Feature status=Complete |Feature version=` |Feature health=OK |Feature status note=Lots of small stuff left to do here. }}

Team

Product manager Christopher Blizzard
Directly Responsible Individual Christopher Blizzard
Lead engineer Jason Duell
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead `
UX lead `
Product marketing lead `
Operations lead `
Additional members `

{{#set:Feature product manager=Christopher Blizzard

|Feature feature manager=Christopher Blizzard |Feature lead engineer=Jason Duell |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

`

Stage 1: Definition

1. Feature overview

There's a list of things left to do to get WebSockets across the finish line. Some minor API changes, protocol fixes, etc.

2. Users & use cases

`

3. Dependencies

`

4. Requirements

`

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

`

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

Must Have:

May be required:

Nice to have:

  • 668948 Websockets events happen out of order if client handlers do Sync XHR
  • 677000 Intermittent test_websocket.html - onerror called on test 37!
  • 677316 Intermittent test_websocket.html - test 35b closed cleanly followed by - test 35 custom server code and - test 35 custom server reason sometimes started by - onerror called on test 35
  • 677840 Intermittent TEST-UNEXPECTED-FAIL - /tests/content/base/test/test_websocket.html - application timed out after 330 seconds with no output
  • 684169 Intermittent test_websocket.html - onerror called on test 2!
  • 684290 Intermittent failure in content/base/test/test_websocket_basic.html - Connection closed cleanly
  • 688716 Intermittent test_websocket.html - the ws connection in test 8 should be closed cleanly

Needs info:

  • 691038 Websocket: message not processed on close
  • 691040 Websocket: Improperly constructed message frames

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=` |Feature overview=There's a list of things left to do to get WebSockets across the finish line. Some minor API changes, protocol fixes, etc. |Feature users and use cases=` |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=Must Have:

May be required:

Nice to have:

  • 668948 Websockets events happen out of order if client handlers do Sync XHR
  • 677000 Intermittent test_websocket.html - onerror called on test 37!
  • 677316 Intermittent test_websocket.html - test 35b closed cleanly followed by - test 35 custom server code and - test 35 custom server reason sometimes started by - onerror called on test 35
  • 677840 Intermittent TEST-UNEXPECTED-FAIL - /tests/content/base/test/test_websocket.html - application timed out after 330 seconds with no output
  • 684169 Intermittent test_websocket.html - onerror called on test 2!
  • 684290 Intermittent failure in content/base/test/test_websocket_basic.html - Connection closed cleanly
  • 688716 Intermittent test_websocket.html - the ws connection in test 8 should be closed cleanly

Needs info:

  • 691038 Websocket: message not processed on close
  • 691040 Websocket: Improperly constructed message frames

|Feature landing criteria=` }}

Feature details

Priority P1
Rank 999
Theme / Goal `
Roadmap Platform
Secondary roadmap `
Feature list Platform
Project `
Engineering team Networking

{{#set:Feature priority=P1

|Feature rank=999 |Feature theme=` |Feature roadmap=Platform |Feature secondary roadmap=` |Feature list=Platform |Feature project=` |Feature engineering team=Networking }}

Team status notes

  status notes
Products ` `
Engineering ` `
Security ` `
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}