Status: Untriaged Owner: jcam...@chromium.org CC: jor...@chromium.org Labels: Type-Bug Pri-1 OS-All Area-WebKit Size-Medium Regression Mstone-3
New issue 15777 by jor...@chromium.org: Need to update how we handle focusing to match new WebKit code http://code.google.com/p/chromium/issues/detail?id=15777 https://lists.webkit.org/pipermail/webkit-dev/2009-July/008635.html """ In order to get focus memory for tabs working properly, we need a notion of whether or not the underlying Page is focused. We need this since Web pages should be able to shift around programmatic focus in background tabs and have the new focused frame and focused node be remembered if you switch back to that tab. Our current code was relying only on the window being active plus the frame being focused to decide that it should draw focus rings and blink carets. However this isn't good enough in the case described above. I have just added a new boolean to FocusController that indicates whether or not the Page is focused. The Mac and Windows ports have been patched to update the Page focused state properly (I hope). Other ports will need to call page->focusController()->setFocused(true) or setFocused(false) now in order for everything to work properly. """ I'll update this bug once I roll deps -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
