Bug 20166 – CSS Perspective Transform works on iPhone but not in Safari

• Component: CSS
• Status: RESOLVED FIXED

[CJ Yetman]

The CSS perspective transform, as described here

http://developer.apple.com/webapps/docs_iphone/documentation/iPhone/Conceptual/SafariCSSTransformGuide/TransformProperties/chapter_5_section_5.html

works handsomely on the new iPhone 2.0 Safari, but it does not on the current nightly WebKit (r35289), Safari 3.1.1 (5525.20), nor the Safari 4 beta (5526.11.2).

I'll attach the example provided in Apple's documentation as a test-case.
-cj

[CJ Yetman]

Created attachment 22472 [details]
css perspective transform example from Apple documentation

[Michael]

Confirmed still broken in nightly r35615 binary for Windows.

[Dave Hyatt]

None of the 3d stuff is implemented on the desktop yet.  It works only on the phone.

[Simon Fraser (smfr)]

As hyatt said, perspective is not supported on desktop WebKit.

[CJ Yetman]

> As hyatt said, perspective is not supported on desktop WebKit.

It will never be supported on the desktop? Really?

May I ask why the disparity?

[Michael]

I request this is reopened and changed to Severity: Enhancement.

[Simon Fraser (smfr)]

Changing to Enhancement.

[Justin French]

Based on the information provided at WWDC09, I'd consider this a bug rather than an enhancement.  These features were demonstrated as part of Safari 4, yet it's obviously shipped without it.

[Simon Fraser (smfr)]

The latest nightly build has 3D transform support, when run on SnowLeopard.

[Michael]

I request this issue is reopened again.

As per previous comments, feature is still missing on Windows and Linux versions of Safari causing a disparity between platforms.  Unless a coherent technical argument can be put forward as to why the 3d features can never be implemented on Windows and Linux platforms, this issue is either a bug or a feature request but either way should not be closed until resolved.

[Simon Fraser (smfr)]

Please file new bugs specific to those platforms.

[CJ Yetman]

(In reply to comment #11)
> Please file new bugs specific to those platforms.


Should I file a bug specifically for Leopard (not Snow Leopard), considering all the PowerPC users out there are apparently being left behind?

[Simon Fraser (smfr)]

Sure, there's no harm in doing so.

[CJ Yetman]

(In reply to comment #13)
> Sure, there's no harm in doing so.

Actually, I am the original reporter of this bug, and it was related to 10.5 not 10.6. I see in the OS parameter above that this is listed as 10.5. So, maybe this bug should be left open since it is related to Leopard, not Snow Leopard?

[CJ Yetman]

Hate to beat a dead horse, but I'm still very interested in this bug being reopened....

1 - Technically speaking, whether or not the CSS Transforms work on Snow Leopard or not is irrelevant to this bug, and therefore the bug should be left open until a fix for 10.5 is in the works or there is an announcement that there is no intention to make it work on 10.5

2 - Though I understand there may be underlining reasons why getting this to work on 10.6 may be a much different process than getting it to work on 10.5, for instance, a new QuickTime or QuickDraw API or whatever layer that is unique to 10.6. But even if that is the case, I find it very strange that the Webkit project would not be interested in making this work on all platforms for which there are Webkit ports.

As I understand it, these CSS functions may currently be Webkit specifc, but they are intended to function much like the standard CSS functions will once they are finalized. If and when those standards are finalized, will the Webkit project continue to ignore that they do not function properly on 10.5, leaving some ports of Webkit non-compliant with CSS standards? What other ports of Webkit will be deemed unnecessary to enable these CSS standards, and how will it be determined which ports are necessary to support and which are not?

[Simon Fraser (smfr)]

We hear you, but continued comments in this bug won't have an impact on our ability to provide this on Leopard.

[Chris Foresman]

(In reply to comment #16)
> We hear you, but continued comments in this bug won't have an impact on our
> ability to provide this on Leopard.

A technical explanation of the problem may enable others to assist in providing the support. Is the implementation currently OS-specific? If so, surely there is a way to tie the transform ability into Leopard, if it can be done with iPhone OS 2.x.

[Simon Fraser (smfr)]

Created attachment 32607 [details]
Patch

There will be some new Leopard-specific pixel results that go along with this.

[Oliver Hunt]

Comment on attachment 32607 [details]
Patch

r=me, are there no leopard tests that need their results updated?

[Simon Fraser (smfr)]

http://trac.webkit.org/changeset/45754

[Michael]

Windows support is being tracked in Bug 27314: "3D CSS Transforms are not implemented in WebKit for Windows".

[Paul Irish]

While I do recall 3D transforms working on 10.5, they are broken now.
Many of the 3d tests in the LayoutTests/transforms/3d/point-mapping , for instance, fail.
I believe this ticket should be reopened.

[Simon Fraser (smfr)]

3D transforms on Leopard were disabled to work around a bug in QuickTime:
http://trac.webkit.org/changeset/55100