A good place to start is to see if the same problem occurs with Safari. If it does, then it's likely a WebKit bug; otherwise, it's more likely ours.
On Tue, Sep 23, 2008 at 1:18 PM, HLS <[EMAIL PROTECTED]> wrote: > > Hi, > > After loosing a swab of hair, I finally been able to recompile > Chrome. I want to fix a few things, and of course, following "other > peoples" code is a daunting task. > > But a little pointing of whether to look and analyze for a correction > would be all I need. > > For this bug, for our Windows HTML help system (*.CHM files) when > updated, we also move the source *.HTM files to our online support > system. > > These include <OBJECT> blocks that include keywords. What happens when > viewing via CHROME, it is rendering the object as a fixed blank area, > so this is what you see: > > http://www.winserver.com/public/aup/aupindex.htm > > You can reproduce this with any simple web page with an <object> > block. > > It appears that the default CSS stytle width and height is not > initialized and uses I believe the location of </object> tag. > > The workaround is to use a explicit style display:none. > > Anyway, where in chrome do I make this correction? What files should > I look at? > > Thanks > > --- > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
