WebCompat Summit (2015)

From MozillaWiki
Revision as of 03:04, 12 November 2014 by Karlcow (talk | contribs) (→‎Tentative Agenda: adding some issues about web compatibility)
Jump to navigation Jump to search

What is this?

We will have three session throughout the day, organized by topic. Talks or roundtable sessions, depending on attendee interest or proposals.

Standards & Web Compatibility Session

Discussion related to web standards efforts and how they relate to web compatibility. E.g., specifying legacy features and coordination.

Testing, Tooling & Web Compatibility Session

Discussion related to automated testing, measuring or crawling the web to understand the impact of removing support for certain web platform features, etc.

Outreach & Web Compatibility Session

Discussion related to doing "evangelism" or outreach work as it relates to web compatibility.

When and Where

Date

Tuesday, February 17th, 2015.

Start time: TBD

End time: TBD

Location

Mozilla Mountain View

Mozilla Headquarters
331 E. Evelyn Ave.
Mountain View, CA 94041
  • Phone Number: +1 650 903 0800
  • Access Details: Please check in at reception on the first floor.
  • Map: https://goo.gl/maps/dy6SE

We have the Commons (110), Polaris (109) and Capella (108) rooms reserved.

Tentative Agenda

Location: MTV Commons

Time Topic
9:30am Registration and Coffee
10:00am Welcome and Introductions
10:15am-11:45 Standards & Web Compatibility Session
11:45am-1:30 Lunch (catered in?)
1:30pm-3:00 Testing, Tooling & Web Compatibility Session
3:00pm-3:15 Coffee & Snack Break
3:15pm-4:45 Outreach & Web Compatibility Session
4:45pm-5:00 Closing Remarks


Location: Polaris or Capella

9:30 - 5:00pm Hack/work room available

Location: Polaris or Capella

9:30 - 5:00pm Unconference/breakout room available

Web Compatibility Issues

Outreach

  • Sharing contact information without breaching the privacy of the contact.
  • Contact information will not necessary be valid for a long time. What about continuity? Proxy email addresses?

Web Standards and Regression

  • When a Web browser delivers a new feature which is breaking the Web
  • When a Web browser removes a feature which is breaking the Web

User agent sniffing

  • Legacy detection scripts on the client side
  • Multiple JS all doing a kind of detection
  • Databases with old information about user agents.