Bug 149612

Summary: Transformed text turns blue
Product: WebKit Reporter: Joshua Bell <jsbell>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: RESOLVED MOVED    
Severity: Normal CC: bfulgham, simon.fraser, webkit-bug-importer, zalan
Priority: P2 Keywords: InRadar
Version: Safari 9   
Hardware: iPhone / iPad   
OS: iOS 9.0   
See Also: https://bugs.webkit.org/show_bug.cgi?id=147235
Attachments:
Description Flags
screenshot showing blue text none

Joshua Bell
Reported 2015-09-28 18:51:34 PDT
Created attachment 262037 [details] screenshot showing blue text Safari on iOS 9.0.1, iPhone 5s, portrait orientation. This is reliable for me, but not minimized - sorry! 1. Navigate to http://travellermap.com 2. Add to Home Screen 3. Go to Home Screen, launch shortcut 4. Click "route" button (zig-zag, top left, to right of search box) 5. Click close button (the "x" in the upper right) Expected: SPINWARD and TRAILING vertical labels on left/right side of page stay red Actual: SPINWARD and TRAILING vertical labels on left/right side of page turn blue Once these labels turn blue they stay blue until a reload. There's no blue in the CSS. Other global style recalcs can also trigger this (e.g. the labels may change color at step 4), but these repro steps are 100% reliable for me. This didn't repro under iOS8, does not repro in desktop Safari or other browsers.
Attachments
screenshot showing blue text (314.23 KB, image/png)
2015-09-28 18:51 PDT, Joshua Bell
no flags
Joshua Bell
Comment 1 2015-09-28 18:53:43 PDT
With inspector connected from desktop Safari, it claims the computed color is red. Poking any style via the inspector causes the text to actually become red on the device.
Timothy Hatcher
Comment 2 2015-09-29 09:11:18 PDT
This sounds similar to bug 147235.
Radar WebKit Bug Importer
Comment 3 2015-09-29 11:32:21 PDT
Brent Fulgham
Comment 4 2022-02-10 14:22:38 PST
The fix for this issue was needed outside the WebKit project, therefore this is being resolved as 'Moved'. This should now be fixed in shipping software.
Note You need to log in before you can comment on or make changes to this bug.