w3ctag / extensible-web-report-card

Documenting the state of the extensible web

The Extensible Web Report Card

Edit index.md, and when it gets pushed it will auto-update the website.

Testing Locally

Install RubyGems, bundler, and stuff. Then do bundle install.

Then do bundle exec jekyll serve.

extensible-web-report-card's Issues

Shadow Dom Movement?

In discussion with @bkardell he feels there is positive movement on this - do we need to reflect this in the Report Card? @slightlyoff @travisleithead

More detail on things like CSP

@wseltzer @slightlyoff

Give more background

E.g. a link to the EWM at the very least

mention storage

The work at https://storage.spec.whatwg.org/ may be worth mentioning (along with the other things that it is attempting to describe).

SRI?

SRI is CR and appears to have support in chrome 45, ff 43 and opera 32 - TAG discussed this a while back IIRC because I brought it up. Should we toss it on here with comment? Might be decent to do while @diracdeltas is still on TAG?

Show that this is no longer updated

Make more pretty

Time to transition off this?

Discussed at Melbourne F2F.

@torgo to weigh in

@slightlyoff to pull out the issues that we still need to watch, as the TAG, and put them in GitHub.

Add some idea of trend - what the trend has been

raised by @chaals.

Restructure report card?

from f2f: Should we reschedule it by layer?

Add WebASM

Need to discuss and agree how WebASM fits into this.

Add sidebar table of contents/listing

focus styling is disruptive in class.

I realize that I am biased as a co-author of a proposed solution to the problem described here, but it seems that most of the standards community both understands and agrees that the problem described is real and problematic: Browsers have since 2007 (at least) been styling the focus ring with "secret information" not currently exposed to users and the :focus pseudo-class does not consult the same source of truth creating a bad conflict of benefit/reward/ability to comprehend the problem and this is currently hurting a whole lot of sites a11y.

Described in more detail http://radar.oreilly.com/2015/08/proposing-css-input-modailty.html

We need broader community involvement in this document

/cc @bkardell @wycats @domenic

Object.observe mentions?

Object.observe() is mentioned a few times on the report card, but it would appear to have fallen out of favor before it got wide implementation. I think that requires discussion/comment (or perhaps at least removal of existing comments?)

Web RTC?

It has wider implementations than some other things on the report card already... Could probably use an evaluation.

http://caniuse.com/#search=webrtc

SVG?

Considering the new SVG charter under consideration it seems like we should consider where SVG sits and what we'd like to see happen to make it more extensible.

Flesh out parts that are pretty sparse

Especially with more links, but in general certain parts are "telegraphic" as @torgo puts it.

Make it clear who the audience is

raised by @travisleithead

Needs a design refresh

make it clear what it is - that it's a review of existing specs

raised by @hadleybeeman

Private state with Weakmaps?

"Explaining the DOM via JavaScript"

Are weakmaps really the way of expressing private state?

In General, how can we show positive movement?

How can we indicate visually somehow when a particular spec or technology has improved and that it's on a good track? @bkardell

Add permissions API

@slightlyoff

Better contribution explanation

Also in discussion with @bkardell – We need to have a clearer explanation to would-be contributors of how to get involved here. How can you submit a suggested addition to the report? Etc... Assigning this to me to try to write something up.

New category: expelled from school

for eg. appcache

Add webappsec specs into this...

Need a freshness date on the document.

@plinss