3 ms·
> How do you know? It's was unprefixed already ~3 months ago, so why should it happen with the next release? It was unprefixed ~6 months ago. Their latest Saf
by sirn 12y ago
> How do you know? It's was unprefixed already ~3 months ago, so why should it happen with the next release?
It was unprefixed ~6 months ago.
Their latest Safari release tracks WebKit release 600 which contains all changes until July 2014[1]. The latest WebKit release is 601, which contains all changes until September 2014[2], including the flexbox unprefixing. Safari normally update WebKit to the latest release in a non-maintenance update (e.g. Safari 8.1) so it should be available with the next release.
Another thing to note is that their Web Inspector (which is built with HTML+CSS+JS) already uses the unprefixed flexbox in trunk, so if they want to ship the updated Inspector, they will eventually have to ship the feature anyway.
[1]: http://trac.webkit.org/export/180623/tags/Safari-600.1.1/ChangeLog http://trac.webkit.org/export/180623/tags/Safari-600.1.1/Cha...
[2]: http://trac.webkit.org/export/180623/tags/Safari-601.1.1/Source/WebCore/ChangeLog http://trac.webkit.org/export/180623/tags/Safari-601.1.1/Sou...
- technojunkie 12y agoThe first link you referenced contains a chromium dev stating the flexbox spec was stable as of summer 2012. This is an example of a secretive Apple not being transparent about why they lag behind the rest of the industry. This behavior helps no one.
- sirn 12y agoSorry, I'm not sure I get your point, are you referring to this comment: 2012-08-31 Tony Chang <tony@chromium.org> Remove ENABLE_CSS3_FLEXBOX compile time flag https://bugs.webkit.org/show_bug.cgi?id=95382 [..snip..] Everyone is already enabling this by default and the spec has stablized. If so, as a honest question, I'm not sure how is this comment related to, or why should it be an example for Apple not being transparent about why they lag behind. Can you clarify?