On Mon, Dec 15, 2008 at 10:12 AM, Peter Kasting <[email protected]> wrote:
> The status bubble is overkill for this; it was a separate window mainly so > it could move outside the main browser bounds as needed. > Bah, I was wrong. Another issue is that the content area has its own HWND. If you want to draw above this, you need to have your own HWND too. There are two ways to do all this. You can do something like the status bubble, which will put all the code in one place and basically just work, at the cost of being a bit heavyweight. Perhaps we can refactor the status bubble code here (it would be nice to make use of it in the popup blocker UI as well). Or you can let WebKit draw the resize corner in some cases, and create a View to draw in the other cases (like when you're over the download shelf). Assuming the WebKit code "just works", this is perhaps less code overall (unless we refactor the status bubble), at the expense of more design complexity (though maybe not much more, as either way you have to calculate the right rect to give WebKit). Ben may share more detailed thoughts; I think he supports the latter plan while I lean a bit more toward the former. Experimentation with both solutions will of course be the most informative :) PK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
