My thoughts exactly! But speculation doesn't really do the issue much justice. To eventually have someone debug the problem would be ideal. I created a bug report about this issue a couple of days ago here: http://code.google.com/p/chromium/issues/detail?id=9013
2009/3/23 PhistucK <[email protected]> > *On the other hand, there is already a known issue with Chrome and > checkboxes or scrollbar arrows not appearing.**( > http://code.google.com/p/chromium/issues/detail?id=3543)* > Which, in my opinion, probably relates to a core issue with the form > controls implementation. > > * > *☆PhistucK > > > On Sun, Mar 22, 2009 at 21:03, Amanda Walker <[email protected]> wrote: > >> >> On Sun, Mar 22, 2009 at 2:36 PM, Robert Dailey <[email protected]> >> wrote: >> > If this was a DLL specific issue, wouldn't this problem occur in other >> > applications as well? The fact that this issue does not exist in Firefox >> 3 >> > must mean this is an application-specific issue. >> >> No, it just means that Firefox doesn't trigger it. I've tried various >> Windows theming products over the years, and in my experience they all >> cause problems in some applications. WindowBlinds was pretty well >> behaved the last time I tried it, but even it caused weird problems in >> some applications. >> >> > I have no other way to apply visual themes in MS Windows. >> >> I understand--but since Windows does not support an API for theme >> switching, it all depends on how well the theme switcher authors have >> reverse engineered internal Windows interfaces. It's hard to get this >> perfect. >> >> > In addition, this only occurs on certain google websites. For example, >> edit >> > boxes draw fine in GMail (The search edit box at the top) while the edit >> > boxes when creating a new post on the google group page for this group >> do >> > not. Can you explain this very specific behavior? >> >> Not off hand--both work fine on my unpatched Windows boxes... >> >> > Also keep in mind that not everyone who uses Chromium has the knowledge >> nor >> > the time to develop it. The best I can do for the community is report >> the >> > issue and hope that it gets backlogged and hopefully fixed in the >> future. >> >> That's fine. I was just trying to set realistic expectations; getting >> it fixed may have to wait until someone who runs a patched system can >> take the time to track down the problem and come up with a fix. >> Making sure things work correctly in XP and Vista is a high priority, >> and we have dedicated resources for testing and verifying that they >> do. Making sure everything works on patched systems is by nature a >> much lower priority, but nothing's stopping someone from tracking it >> down and submitting a fix. I'm not saying it's *not* a bug in >> Chromium, but unless it happens with the standard vesion of >> uxtheme.dll, it seems more likely that the theme patch is what's at >> fault. >> >> --Amanda >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
