Bug 110417

Summary: Disable window occlusion notifications for App Store on Mac.
Product: WebKit Reporter: Kiran Muppala <cmuppala>
Component: WebKit2Assignee: Kiran Muppala <cmuppala>
Status: RESOLVED FIXED    
Severity: Normal CC: simon.fraser, webkit.review.bot
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch none

Kiran Muppala
Reported 2013-02-20 17:33:03 PST
Window occlusion notifications are being received at seemingly incorrect times in the App Store. See <rdar://problem/13157837> for details. This is a temporary fix to disable these notifications just for App Store.
Attachments
Patch (1.76 KB, patch)
2013-02-20 17:49 PST, Kiran Muppala
no flags
Patch (1.61 KB, patch)
2013-02-20 18:10 PST, Kiran Muppala
no flags
Kiran Muppala
Comment 1 2013-02-20 17:34:08 PST
This hack of a fix is for <rdar://problem/13157837>. <rdar://problem/13255270> is for investigating the notifications themselves.
Kiran Muppala
Comment 2 2013-02-20 17:49:02 PST
Simon Fraser (smfr)
Comment 3 2013-02-20 18:04:43 PST
Comment on attachment 189428 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=189428&action=review > Source/WebKit2/ChangeLog:11 > + Window occlusion notifications are being generated at unexpected times > + in the app store, leading to visual glitches. This is a temporary > + fix until the underlying issue with the notifications themselves is > + resolved. I don't think you need quite as much detail here.
Kiran Muppala
Comment 4 2013-02-20 18:10:12 PST
Kiran Muppala
Comment 5 2013-02-20 18:10:49 PST
(In reply to comment #4) > Created an attachment (id=189436) [details] > Patch Simplified ChangeLog.
WebKit Review Bot
Comment 6 2013-02-20 18:43:38 PST
Comment on attachment 189436 [details] Patch Clearing flags on attachment: 189436 Committed r143552: <http://trac.webkit.org/changeset/143552>
WebKit Review Bot
Comment 7 2013-02-20 18:43:41 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.