browsers

Not in terms of making ES2015 code work on old browsers, but making old code work on new browsers.

Schools aren't exactly keeping their browsers up to date nor are they going to install alternative browsers.

It says, for example, that 1 in 1.34 (ie, only about 75%) of all browsers have cookies enabled.

Context: You will be implementing UIs for our stores which are accessible via game clients / web browsers.

Comet was the painful reminder of how little browsers have developed over the last 10 years.

Presumably it's a win for the people who prefer Chrome to the other browsers, yes?

That is, assuming you don't need to support older browsers like ie9 or ie8...

For that matter, just make browsers not allow an iframe within another iframe...

Most sites, almost all, would break if browsers suddenly disallowed third party scripts.

For one, it doesn't take into account that plugins/browsers are constantly getting updated.

I do believe most complaints about CSS is really complaints about missing and buggy implementations in browsers.

My proven theory is that if you don't support users with particular browsers those users will tend to no longer support your website in return.

Maybe there should be a standard to go the other way: a scheme to let web sites communicate monetary requests to browsers in an "official" protocol.

"Also, world's first web site[1] still works in modern browsers".

I really don't want you to become the embedded player for.mpg files in all of my browsers, so I'm stuck with a 1"x1" postage stamp on my 26" monitor and no full-screen option).

Also I think that aside from IE, browsers do a good job of getting standard features done, which is sort of amazing considering they don't have the "benefit" of top-down bureaucratic governance like the "native" platforms.

Browsers are the new bloatware and make Microsoft Office look like vi.