News for hackers. Stuff that matters.
Re:Firefox 46 supports some -webkit prefixed CSS properties by nerdy on Wednesday April 27, 2016 @07:34AM (#11579432)
Very interesting considering WebKit is moving away from prefixes: https://webkit.org/blog/6131/updating-our-prefixing-policy/
Re:Firefox 46 supports some -webkit prefixed CSS properties by TazeTSchnitzel on Wednesday April 27, 2016 @07:49AM (#11579516)
It's the kind of mess that got Firefox to have to implement other browsers' prefixes that led to Blink, Gecko and WebKit ceasing to use them for new features. Unfortunately, that doesn't clean up the existing problems, but it should prevent creating more.
Re:Firefox 46 supports some -webkit prefixed CSS properties by mccr8 on Wednesday April 27, 2016 @10:20AM (#11580632)
From that article: "We expect to significantly reduce the number of prefixed properties supported over time but Web compatibility will require us to keep around prefixed versions of some features."

The features WebKit needs to keep around to continue to work with many websites are presumably about the same as those Firefox felt it had to implement to work with many websites.

(Disclaimer: I work on Firefox.)

Re:Firefox 46 supports some -webkit prefixed CSS properties by gcb0 on Wednesday April 27, 2016 @11:19AM (#11581160)
this is bad.

remember when Microsoft was the first to ship a browser shipped by default and dictated the standards by releasing it as they saw fit in that monopolistic browser? (for the kids of today, devs from that day loved ie just like you love chrome today. IE invented the developer panel and ajax request, both things you live by today)

well, Google (the irony) sued and won. Microsoft had to remove IE from Windows, and browser vendors agreed to not force standards themselves. that is the only reason we have prefixes. it send the message "we think it's cool, but wait for everyone to agree on the best way to implement this".

without prefixes, Google, having the browser monopoly (since Android is the new windows) can dictate the direction as it see fits. just like Microsoft when they sued them.

Re:Firefox 46 supports some -webkit prefixed CSS properties by miketaylr on Wednesday April 27, 2016 @12:10PM (#11581709)
...what.

I don't think you understand how prefixes are used in the wild. Vendor prefixes re-inforce monoculture, they don't prevent it.

Re:Firefox 46 supports some -webkit prefixed CSS properties by magicalist on Wednesday April 27, 2016 @01:42PM (#11582653)
> well, Google (the irony) sued and won. Microsoft had to remove IE from Windows, and browser vendors agreed to not force standards themselves.

What on earth are you talking about? This is not a thing that ever happened.

Re:Firefox 46 supports some -webkit prefixed CSS properties by gcb0 on Saturday April 30, 2016 @07:35PM (#11604137)
are you too young to remember the browser wars and how Google sued ms for giving internet explorer for free with msn as the honepage?
Re:Firefox 46 supports some -webkit prefixed CSS properties by cpeterso on Wednesday April 27, 2016 @12:53PM (#11582170)
The modern "no prefixes" approach is to hide the new features behind a runtime flag or in a pre-release beta channel. Web developers can test the feature but not use it in production websites until browser vendors standardize it.
Re:Firefox 46 supports some -webkit prefixed CSS properties by ddebernardy on Wednesday April 27, 2016 @07:50AM (#11579520)
And one of the reasons mentioned in there, incidentally, is browser vendors feeling compelled to become compatible with each other's prefixes.
Re:Firefox 46 supports some -webkit prefixed CSS properties by nerdy on Wednesday April 27, 2016 @08:10AM (#11579631)
It seems they agree the existing state of affairs isn't acceptable, but don't agree about how to proceed.

Consider Mozilla's perspective... they're trying to refocus on Firefox[1] and immediately after they find a suitable place for Thunderbird[2] they release support for WebKit prefixes while Apple announces dropping the same prefixes. Not only does this mean Mozilla arguably wasted time, it also means they'll have this prefix code as an artifact for some time while it becomes increasingly irrelevant. At the same time, it makes Firefox seem antiquated while the floor falls out from under its user base[3].

1. http://news.softpedia.com/news/mozilla-wants-to-ditch-thunde... 2. http://news.softpedia.com/news/two-foundations-are-willing-t... 3. http://www.w3schools.com/browsers/browsers_stats.asp

Re:Firefox 46 supports some -webkit prefixed CSS properties by masklinn on Wednesday April 27, 2016 @08:21AM (#11579707)
> It seems they agree the existing state of affairs isn't acceptable, but don't agree about how to proceed.

They completely agree how to proceed, Firefox and Chrome both moved to using feature flags instead of vendor prefixes a while back, but there are so many -webkit- prefixed "advanced" properties in the wild, and developers only testing their site in Chrome (which hasn't removed the old prefixed properties for compatibility reasons) that Mozilla felt compelled to add support for these. Incidentally, they're following Opera[0] and Microsoft[1] in doing so.

> while Apple announces dropping the same prefixes

Apple didn't announce dropping support for existing prefixed properties (at best they noted that they may remove some over time depending on compatibility needs), only that new features will be gated instead of prefixed going forwards.

> it also means they'll have this prefix code as an artifact for some time while it becomes increasingly irrelevant.

Prefixed properties are just specific names, the vendor prefix is incidental, Mozilla implemented and enabled a bunch of properties named -webkit-{something} instead of {something}.

[0] http://www.sitepoint.com/opera-css3-webkit-prefix/

[1] https://msdn.microsoft.com/en-us/library/mt270097%28v=vs.85%...

Re:Firefox 46 supports some -webkit prefixed CSS properties by nerdy on Wednesday April 27, 2016 @08:26AM (#11579739)
As I understand it, WebKit's feature flags will not include the webkit prefix:

"WebKit’s new policy is to implement experimental features unprefixed"

But Mozilla still plans for experimental features to be prefixed:

"Mozilla supports a number of extensions to CSS that are prefixed with -moz-.

Some of these properties have been included in draft CSS specification for inclusion in the final recommendation, but are still experimental... Once standardized, and the support for the un-prefixed variant added, the prefixed properties are dropped."

Re:Firefox 46 supports some -webkit prefixed CSS properties by masklinn on Wednesday April 27, 2016 @08:39AM (#11579820)
I'm not sure what you're trying to say. The webkit quote indicates that new experimental features will be unprefixed and behind flags, which is already the policy at Mozilla. For instance as of Firefox 46 (release channel) "grid" is unprefixed (there is no -moz-grid[0]) but behind a flag (layout.css.grid.enabled).

> But Mozilla still plans for experimental features to be prefixed:

The quote doesn't support your interpretation, it only indicates that there are -moz-prefixed experimental properties, just as there are -webkit-prefixed experimental properties.

[0] well there is a display: -moz-grid value for display but it's a historical XUL property unrelated to the CSS Grid Layout module: https://bugzilla.mozilla.org/show_bug.cgi?id=616605#c10

Re:Firefox 46 supports some -webkit prefixed CSS properties by ape4 on Wednesday April 27, 2016 @09:24AM (#11580158)
Obviously the solution is vendor-specific suffixes! /joke attempt
Re:Firefox 46 supports some -webkit prefixed CSS properties by petecox on Wednesday April 27, 2016 @10:12AM (#11580571)
Abso-bloomin'-lutely not. :) Vendor-specific infixes...