Bug 126721
| Summary: | JavaScriptCore Obj-C API gives incorrect behavior for CGFloat properties on ARM64 | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Mark Rowe (bdash) <mrowe> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | bfulgham, mhahnenberg, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://github.com/iamdavidhart/JSObjCBridge64BitTest | ||
Mark Rowe (bdash)
From <https://github.com/iamdavidhart/JSObjCBridge64BitTest>:
> The new Javascript-ObjC bridge on iOS7 is broken on 64bit iOS ARM devices when using an exported property declared as a CGFloat from javascript. When accessing the CGFloat property of a bridged ObjC object, the value set or get is wrong, always a (very nearly) zero value.
The linked GitHub repository contains a test case that claims to give correct results in 32-bit while demonstrating the bug in 64-bit.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/15786582>