we should define standards (browser support, etc) for new additions to sassquatch

[meetuparchive]

we should define standards (browser support, etc) for new additions to sassquatch

[sjhcockrell]

Here is the support chart for mobile (included with the How We Build doc now):

https://docs.google.com/a/meetup.com/spreadsheet/ccc?key=0AsxzEW3cE_a7dC0xSWFEQnltaVpqaEEyQU01RXIxWUE#gid=0

[akdetrick]

tl;dr - everything in sassquatch should work for IE7+. Visual differences should be allowed to degrade in older browsers as long as basic layout isn't completely busted. Let's avoid making the framework do too much in order to avoid this (think "small sharp tool").

two things to note here...

1. Originally, sassquatch supported IE7+. Some additions over time may not work so well in older browsers, but they should be fixed.

2. This is one of the reasons we're planning on moving certain content patterns out of the sassquatch core framework. We need to be able to trust that the foundation we're building on works well down to IE7, and that we're not making frequent changes to the framework to accomodate new patterns/widgets (see the 2.0.0 milestone in the sassquatch roadmap)

[sjhcockrell]

So here's my deal with support for IE7:

It's currently 0.6% of browser share on meetup.com, and it's a browser with enough bugs in basic layout that it can't really be considered "modern" or W3C compliant.

This makes it a bit different from something like FF for Android, which, while it has 0.5% market share, is a modern browser and W3C compliant--meaning that mobile code written for compliant browser should work here, too.

A general (maybe unfounded) worry I have is overly-circuitous/hacky code ending up in the mobile code base for an increasingly marginal, non-compliant browser.

[akdetrick]

i'll add browser support notes to the README

[sjhcockrell]

Has this been resolved?

If not, here's more numbers:

Desktop and Mobile Browsers, Major

3.22% - Chrome 30.X
23.05% - Chrome 29.X
3.38% - Chrome 5.X

4.11% - Safari 7.x (Mavericks, iOS 7)
15.07% - Safari 6.X (Lion/Mountain Lion, iOS 6)
4.73% - Safari 5.X (Tiger/Lion, iOS 5)

10.87% - IE 10 (Win7, Win 8)
4.32% - IE 9 (Win 7, Vista)
4.11% - IE 8 (Win XP)
0.59% - IE 7

13.93% - Firefox 23-26 (current)
0.69% - Firefox 20-22
1.07% - Firefox <=19

Mobile Device Load

22.14% - Mobile Devices [a]

15.68% - iOS [b]
5.87% - Android [b]
0.59% - Other (BB/WP) [b]

8.54% - iPad [a]
7.02% - iPhone [a]

[mattkime]

+1 sjhcockrell

where did you get the numbers? could you share how you got them? i've been told that they're in google analytics but i haven't discovered the magic clickpath.

[sjhcockrell]

I basically got them from Google Analytics and a calculator, so roughly
accurate.

If you're logged in to your work email, you should be able to get to them
through analytics.google.com.

If not, ask WillH or Ivy.

On Thu, Oct 10, 2013 at 6:05 PM, Matthew Kime [email protected]:

+1 sjhcockrell

where did you get the numbers? could you share how you got them? i've been
told that they're in google analytics but i haven't discovered the magic
clickpath.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9#issuecomment-26095760
.

John Cockrell

[email protected]
[phone]
@sjhcockrell

[akdetrick]

I believe Sassquatch should be tested in:

Chrome 29.X or above
Safari Safari 6.X or above
IE 9 or above
Firefox 23-26 (current) or above

If something breaks in an older browser and we trace the bug back to Sassquatch (we'll have some demo pages set up that exclusively rely on sassquatch for styling, so it will be easier to test this sort of thing soon), we should try to fix it. Not everything has to work in IE8 and below on Meetup, but Sassquatch is our CSS foundation. Something like figureset should work down to IE7 without major breakage...

[sjhcockrell]

The only modification I'd suggest is to say

Safari 5.1 and above (OS X Snow Leopard)
Mobile Safari 5.0 and above (iOS 5)

Chrome 27 and above (I remember seeing a ton of people on Desktop using older versions of Chrome when I looked at logs; would be worth checking)

John Cockrell

On Oct 23, 2013, at 16:48, Adam Detrick [email protected] wrote:

I believe Sassquatch should be tested in:

Chrome 29.X or above
Safari Safari 6.X or above
IE 9 or above
Firefox 23-26 (current) or above

If something breaks in an older browser and we trace the bug back to Sassquatch (we'll have some demo pages set up that exclusively rely on sassquatch for styling, so it will be easier to test this sort of thing soon), we should try to fix it. Not everything has to work in IE8 and below on Meetup, but Sassquatch is our CSS foundation. Something like figureset should work down to IE7 without major breakage...

—
Reply to this email directly or view it on GitHub.

[akdetrick]

duplicate of #175