Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need to figure plan for browser support matrix for launch and going forward #84

Closed
lmclister opened this issue Sep 9, 2014 · 10 comments

Comments

@lmclister
Copy link
Member

No description provided.

@betravis
Copy link
Contributor

I would recommend including some static support tables at the bottom of each relevant page. We could still link to a qunit test suite if people would like to test their own browser, however, test suite and browserscope maintenance tend to degrade pretty quickly over my opinion. Updating a static table is that much simpler, and provides users at-a-glance information rather than requiring them to jump to another page.

Something along the lines of caniuse.com or webplatform docs seems appropriate.

An example of webplatform docs for shape-outside.
shape-outside-compat-table

@bemjb
Copy link
Contributor

bemjb commented Sep 11, 2014

Fixing this might be related to fixing issue #65, since they really should be using the same data source.

@lmclister lmclister modified the milestones: After initial launch, Initial Announce of webplatform.adobe.com Sep 11, 2014
@rhauck rhauck modified the milestone: MAX Release Sep 23, 2014
@betravis
Copy link
Contributor

betravis commented Oct 2, 2014

Did two quick mockups, one with images, one without.
Figured we should iterate while it's easy to do.

With Images

browser-support

Without Images

browser-support-text

@rhauck
Copy link
Collaborator

rhauck commented Oct 2, 2014

@betravis I love the images, so that'd be what I'd vote for. However, the Y / N seem a too weak. maybe some sort of color or icon to to make them visually easier?

@lmclister
Copy link
Member Author

What @rhauck said ^

@betravis
Copy link
Contributor

betravis commented Oct 2, 2014

A couple more variations, with colors. I think the boxes need some method of demarcation.
@rhauck, @lmclister Thoughts? I think I like the last one best, but it makes the images slightly smaller.

With border line

browser-support-colors

With alternating background on heading row

browser-support-background

With alternating background and transparent border

browser-support-white-border

@rhauck
Copy link
Collaborator

rhauck commented Oct 2, 2014

@betravis I like the alternating bg & transparent border (the third one). The red/green/yellow colors look a little rich though. can they be toned down a bit? Or maybe the don't need to be as big?
/cc @lmclister

@betravis
Copy link
Contributor

betravis commented Oct 2, 2014

Sass has these lovely color manipulation functions, so there's no reason we can't do both :)
Bringing down the saturation on the colors and decreasing the vertical padding a bit on the items.

I think I'll invert the opera logo (red circle, white 'o') for the final design.

Toned down

desaturate-depad

@rhauck
Copy link
Collaborator

rhauck commented Oct 2, 2014

@betravis Looks much better. Ship it! /cc @lmclister

@rhauck
Copy link
Collaborator

rhauck commented Oct 3, 2014

fixed in #149

@rhauck rhauck closed this as completed Oct 3, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants