News for hackers. Stuff that matters.
Re:The Mobile Web should just work for everyone by ntakasaki on Monday August 04, 2014 @11:56AM (#8132334)
Edit: The previous title was "Windows Phone's IE starts masquerading as mobile Safari to render pages properly"

Looks like the webkit prefix tags are creating the new IE6. As usual, it's the web developers fault for not updating their CSS prefixes.

http://css.dzone.com/articles/why-webkit-new-ie6-trap-vendor

Mozilla, Opera and Microsoft have been complaining about this and Opera had already implemented support for the webkit prefixes(before switching to webkit/Blink entirely) and Firefox-OS will probably follow.

Re:The Mobile Web should just work for everyone by Cthulhu_ on Monday August 04, 2014 @01:21PM (#8132872)
I disagree that the webkit tags are creating the new IE 6, after all (IIRC) they're prefixed because the standards behind them aren't yet finished.

On the one side I want to make a ramble about why it takes so long for those standards to finish and unprefixed CSS3 and beyond is possible, but on the other hand - without actual real-life use, how can you find all the edge-cases and practical application to create a complete standard?

Re:The Mobile Web should just work for everyone by talmand on Monday August 04, 2014 @04:41PM (#8133897)
Many of these properties no longer require the prefix for most browsers. For these properties having the webkit prefix only, without the non-prefix property to cascade to, is a problem. I recall many demos, examples, and live sites not displaying as expected in Firefox because the developer decided to use only the webkit prefix. If the webkit team were to start removing the webkit prefixed properties then those sites would have even more broken views.
Re:The Mobile Web should just work for everyone by bzbarsky on Tuesday August 05, 2014 @12:00AM (#8135439)
They're initially prefixed because the standard is not finished.

Many of them are _still_ prefixed because WebKit has a policy of never removing prefixed features, even if they implement the unprefixed one. So people feel no compunction about using the prefixed stuff in production, and since they only test in WebKit they don't notice when they're using the -webkit-prefixed version even though every single browser (or every browser except WebKit, in some cases) supports the unprefixed standard version.

Re:The Mobile Web should just work for everyone by matthewmacleod on Monday August 04, 2014 @12:45PM (#8132652)
Yes. This is down to lazy, short-sighted developers, and it makes me insanely irritated.

It's ridiculously easy to make sure you include all appropriate browser-specific and generic prefixes for almost all experimental CSS features. If you use something like Compass, it's even done for you, totally transparently.

Lazy developers ruin it for everybody, again. What a surprise.

Re:The Mobile Web should just work for everyone by afs35mm on Monday August 04, 2014 @12:02PM (#8132385)
I'm not entirely sure this is an accurate analogy. vendor prefixes solved a need. Why should we be developing to the lowest common denominator?

I think we should also watch out for link-bait SEO headlines such as "Why Webkit is the New IE6 (The Trap of Vendor Prefixes)"...

Re:The Mobile Web should just work for everyone by masklinn on Monday August 04, 2014 @12:09PM (#8132440)
> I'm not entirely sure this is an accurate analogy. vendor prefixes solved a need.

No. It tried to solve two different needs: proprietary stable APIs and unstable/in-flux specs. And the abuse of the latter forced browsers to drop the use-case entirely and hide features behind flags because developers could not be trusted to act responsibly, so it definitely didn't solve that problem.

> Why should we be developing to the lowest common denominator?

That's not developing to the LCD, that developers deploying half-specified and unstable APIs in production.

Re:The Mobile Web should just work for everyone by tomjen3 on Monday August 04, 2014 @12:34PM (#8132589)
Why do you blame developers? The fault lies with the standards community for not standardizing much faster (at most a week after the second browser has support for that feature) and for MS for developing a browser at a glacial pace.
Re:The Mobile Web should just work for everyone by masklinn on Monday August 04, 2014 @12:50PM (#8132683)
> Why do you blame developers?

Because the fault lies with them and no one else, no matter how in denial you are.

> The fault lies with the standards community for not standardizing much faster (at most a week after the second browser has support for that feature)

That doesn't even make sense, standards work is not "you shipped some random unspecified and mostly broken pile of shit and some other bloke was convinced to half-implement something which kinda looks similar if you squint so let's just call it standandard :shipit:"

Re:The Mobile Web should just work for everyone by tomjen3 on Monday August 04, 2014 @01:15PM (#8132836)
Do you have any backup for your arguments?
Re:The Mobile Web should just work for everyone by ntakasaki on Monday August 04, 2014 @01:25PM (#8132904)
Re:The Mobile Web should just work for everyone by ntakasaki on Monday August 04, 2014 @12:07PM (#8132420)
The problem isn't that developers should be developing for the lowest common denominator. It is that the prefixes are not being dropped by websites even after other browsers start implementing the feature, or it's that they continue to use the webkit prefix for new websites.
Re:The Mobile Web should just work for everyone by skybrian on Monday August 04, 2014 @12:34PM (#8132591)
It seems to me that vendor prefixes worked as intended. It allowed the HTML specs to be changed (for the unprefixed versions).

True, browsers need to support some pre-standardization variants for now, but this will fade. It doesn't seem like a huge burden for browsers to support older websites for a while, and it doesn't affect new websites.

Re:The Mobile Web should just work for everyone by tomjen3 on Monday August 04, 2014 @12:25PM (#8132544)
I disagree. If the tags had been standalized then we would be using them. Unfortunately the standards commity dropped the ball on this one because they are unable to act fast enough.
Re:The Mobile Web should just work for everyone by masklinn on Monday August 04, 2014 @12:44PM (#8132643)
> Unfortunately the standards commity dropped the ball on this one because they are unable to act fast enough.

These are features which changed semantics and syntax multiple times over the course of their standardisation, it's not like standards guys were slow because they found it fun

> If the tags had been standalized then we would be using them.

Webkit browsers have all supported unprefixed box-sizing since the release of Safari Mobile 5.1 in March 2012. 2 years later… https://github.com/search?l=CSS&o=desc&q=-webkit-box-sizing&...

Re:The Mobile Web should just work for everyone by Smudge on Monday August 04, 2014 @12:49PM (#8132670)
That query means nothing. Most of those results include the non-prefixed version as well. The prefixed one is there for backwards compatibility.
Re:The Mobile Web should just work for everyone by masklinn on Monday August 04, 2014 @12:53PM (#8132703)
> That query means nothing.

That query means developers by and large don't care and just cargo-cult through.

> The prefixed one is there for backwards compatibility.

Backwards compatibility with what, fucking Chrome 6? How many of these sites have been tested for backwards compatibility in Chrome 6? I'd bet it's somewhere around "none whatsoever".

Re:The Mobile Web should just work for everyone by Isofarro on Monday August 04, 2014 @01:23PM (#8132887)
Smudge raises a valid point. The presence of both the webkit prefixed version and the standardised non-prefix version is adequate. The problem IE Mobile are working around are those developers who have the webkit prefixes CSS properties, but not the standard no-prefix version.

Chrome won't remove them because it breaks these sites relying on the webkit prefix remaining - so there's sufficient ground there to indicate developers are failing. But it's not the developers who include the non-prefixed standardised version.

Yes, there are lots of developers who don't care - the ones who rely on the webkit-prefix support remaining. That is contrary to the spirit of vendor prefixes - experimental CSS properties that should not be relied on.

Those using both the webkit prefixed and the standard non-prefixed versions are using the typical graceful fallback - one that doesn't make other browsers "unsupported"

Re:The Mobile Web should just work for everyone by Smudge on Monday August 04, 2014 @02:56PM (#8133403)
Preprocessors often have prefix support baked in. It's not about explicitly testing your site for backwards compatibility. It's about casting that net as far as possible with minimal effort.
Re:The Mobile Web should just work for everyone by tomjen3 on Monday August 04, 2014 @01:16PM (#8132847)
No reason to remove them when they are there.
Re:The Mobile Web should just work for everyone by masklinn on Monday August 04, 2014 @03:49PM (#8133650)
Erm… the query is sorted by most recently indexed, this is code which was just changed, the top hit at this moment is https://github.com/mdilaver/mdilaverins/commits/421298cf9bf1... which is 5 days old.
Re:The Mobile Web should just work for everyone by bzbarsky on Tuesday August 05, 2014 @12:06AM (#8135455)
That's because this CSS is using CSS transforms.

And while IE and Firefox have supported unprefixed CSS transforms for a while now, Chrome and Safari only support the -webkit-prefixed version of CSS transforms so far. So if you want to do transforms, you have to use -webkit prefixes...

Re:The Mobile Web should just work for everyone by masklinn on Tuesday August 05, 2014 @08:44AM (#8136587)
> That's because this CSS is using CSS transforms.

Oh for fuck's sake, the query is specifically looking for -webkit-box-sizing, not for webkit-prefixed properties in general.

Re:The Mobile Web should just work for everyone by bzbarsky on Sunday August 17, 2014 @11:00PM (#8191283)
Ah, I missed that you were specifically talking about -webkit-box-sizing use there!
Re:The Mobile Web should just work for everyone by mikelat on Monday August 04, 2014 @12:53PM (#8132701)
> Looks like the webkit prefix tags are creating the new IE6.

This bothers me. Webkit isn't some ancient browser that is has remained stagnant for years until google/apple decided to do something about it. Nobody spends hours debugging their perfect layouts in webkit. Webkit isn't holding the entire web back. It's just a poor comparison.

I browse mobile web in mostly firefox mobile, and I don't think I've ever seen a mobile site broken on FF but working on Chrome.

In fact at least Google has taken some steps to recitfy it, and they've stated they're putting experimental CSS properties behind developer flags. If we're talking about the fact that old people don't update old browsers then Microsoft is one to talk with IE7, IE8, IE9, and IE10.

Re:The Mobile Web should just work for everyone by wwweston on Monday August 04, 2014 @01:28PM (#8132927)
Most of my professional time these days is spent on mobile/tablet websites for a major automobile manufacturer. And there are days when we absolutely do obsess over layout and other issues introduced by mobile safari itself. On the release of iOS 7, we actually probably burned a month working with a bug that we never found a solution to (which, fortunately, was fixed with iOS 7.1).

That last part underscores that we're fortunate browser makers are issuing regular updates (a big difference from IE). On the other hand, with some of those updates come new bugs and (particularly on Android) fragmentation. Consider that by 2006 there were enough people/resources documenting IE6's quirks that it was pretty rare to run across a bug that someone didn't have a good idea of how to fix/workaround. In 2014 when you run across a mobile bug (particularly one from a recent release, of which there are many), it may well be that nobody knows how to solve your problem, and in some cases nobody seems to even know how to tell you to duplicate it across devices/emulators (http://stackoverflow.com/questions/23142762/how-to-identify-... ).

And of course, like IE, many developers code webkit-only, even iOS only (and I know why: at the level of ambition people often have for mobile websites and with the difficulty involved in testing more than a few devices, it can sometimes seem like the only way to get things out the door).

IE6 was no picnic, but there are times I think to myself I'd rather be working on the 2006 desktop web than the 2014 mobile web....

Re:The Mobile Web should just work for everyone by mikelat on Monday August 04, 2014 @08:57PM (#8134978)
I think you forget how bad it was with 2006 desktop. So many CSS hacks. We take our div layouts for granted but if you dared venture away from the standard table layouts of the early 2000s you were in for a lot of debugging for browser quirks.

Nowadays at least I code responsive layouts to target screen resolution, and its gotten leagues better. Sure there's a few quirks in separate browsers and things aren't necessarily ideal, but it sure beats the days of "I wish I could use xxxx CSS property but I can't because only 2% of my users would be able to render it".

Re:The Mobile Web should just work for everyone by untog on Monday August 04, 2014 @01:21PM (#8132874)
The comparison is apt, just not entirely. It isn't a comparison of IE6 vs Webkit, it's of developer reactions to them.

For a long time, IE6 ruled the roost, so developers used IE6 as their development target. Browsers that moved beyond it, or implemented things differently (often correctly) were ignored.

On mobile, webkit rules the roost. Developers use it as their development target. Browsers that move beyond it or implement things differently (by using non-webkit prefixed CSS) are ignored.

Re:The Mobile Web should just work for everyone by mikelat on Monday August 04, 2014 @08:40PM (#8134911)
I mentioned in another comment that when I think of IE6, I think of the hours spent fiddling with the HTML/CSS that works in FF/Chrome but not in IE6 because of browser bugs that were never fixed and standards not followed. It's why I think it's a bad comparison.
Re:The Mobile Web should just work for everyone by sp332 on Monday August 04, 2014 @02:03PM (#8133124)
No, the new IE6 :) like back when IE6 was king. Meaning that web developers make their site work only in webkit and screw the rest of us.
Re:The Mobile Web should just work for everyone by mikelat on Monday August 04, 2014 @08:36PM (#8134896)
I guess it's a matter of perspective. My experience with IE6 was mostly being a teenage hobbyist webmaster way back when FF vs IE6 was in full spin - I remember being proud of coding standards compliant websites that worked perfectly in FF just to have it completely break in IE6, then having to spend hours fiddling with the HTML/CSS to get it to the point where it worked in IE6. Frustrating times.

That's why I don't really see the comparison. When I think of IE6 I think of the hours I wasted trying to make it work right. I'm not currently coding IE mobile websites, then checking it on a webkit browser, having everything be broken and then spending hours trying to fix it.