strange problem with content.document.documentElement

[Alex Iskold]

Hi all,

We are running into a strange problem with both FF 1.5 and 2.0
We have the following listener:

// Browser Listener
var browserListener =
{
QueryInterface: function(aIID)
{
if (aIID.equals(Components.interfaces.nsIWebProgressListener) ||
aIID.equals(Components.interfaces.nsISupportsWeakReference) ||
aIID.equals(Components.interfaces.nsISupports))
return this;
throw Components.results.NS_NOINTERFACE;
},

onStateChange: function(aProgress, aRequest, aFlag, aStatus)
{
if(aFlag & Components.interfaces.nsIWebProgressListener.STATE_STOP)
{
// do something that accesses content.document.documentElement
}
return 0;
},

onLocationChange: function(aProgress, aRequest, aURI)
{
// do something that accesses content.document.documentElement
return 0;
},

// For definitions of the remaining functions see XulPlanet.com
onProgressChange: function() {return 0;},
onStatusChange: function() {return 0;},
onSecurityChange: function() {return 0;},
onLinkIconAvailable: function() {return 0;}
}

The problem we are seeing is that if we access
[content.document.documentElement] then
on some sites, the fonts and layout becomes crooked. It is as if we manually
did FONT++.
What is strange is that we are only accessing the element, not calling
functions on it.

Any ideas and leads would be appreciated.

Thanks in advance,

Alex
--
alex iskold
founder & cto
http://www.adaptiveblue.com

[Nickolay Ponomarev]

On 10/25/06, Alex Iskold <alex....@adaptiveblue.com> wrote:
> The problem we are seeing is that if we access
> [content.document.documentElement] then
> on some sites, the fonts and layout becomes crooked. It is as if we manually
> did FONT++.

Is the problem reproducible? On what sites?

Nickolay

[Alex Iskold]

Yes, all the time.

We see it on:

http://www.widgetbox.com
http://www.pageflakes.com
http://www.netvibes.com

Alex

--
alex iskold
founder & cto
http://www.adaptiveblue.com

"Nickolay Ponomarev" <asqu...@gmail.com> wrote in message
news:mailman.7986.11618030...@lists.mozilla.org...

[Nickolay Ponomarev]

On 10/25/06, Alex Iskold <alex....@adaptiveblue.com> wrote:
> Yes, all the time.
>
> We see it on:
>
> http://www.widgetbox.com

Thanks, I filed https://bugzilla.mozilla.org/show_bug.cgi?id=358072

As a workaround, try setTimeout(...,0)

Nickolay

[Alex Iskold]

Thanks, we tried that - it does not seem to work.
Any other ideas for workaround?

Thanks again,

Alex

--
alex iskold
founder & cto
http://www.adaptiveblue.com

"Nickolay Ponomarev" <asqu...@gmail.com> wrote in message

news:mailman.7997.11618097...@lists.mozilla.org...

[Nickolay Ponomarev]

On 10/26/06, Alex Iskold <alex....@adaptiveblue.com> wrote:
> Thanks, we tried that - it does not seem to work.
> Any other ideas for workaround?
>

Works fine here. Maybe increase the timeout? I haven't investigated
the actual bug, so can't give you a good suggestion on a workaround.

Nickolay

> Thanks again,
>
> Alex
>
> --
> alex iskold
> founder & cto
> http://www.adaptiveblue.com
>
>
> "Nickolay Ponomarev" <asqu...@gmail.com> wrote in message
> news:mailman.7997.11618097...@lists.mozilla.org...
> > On 10/25/06, Alex Iskold <alex....@adaptiveblue.com> wrote:
> >> Yes, all the time.
> >>
> >> We see it on:
> >>
> >> http://www.widgetbox.com
> >
> > Thanks, I filed https://bugzilla.mozilla.org/show_bug.cgi?id=358072
> >
> > As a workaround, try setTimeout(...,0)
> >
> > Nickolay
>
>

> _______________________________________________
> dev-extensions mailing list
> dev-ext...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-extensions
>

[Alex Iskold]

FYI, the delay of 1 second works.

Alex

--
alex iskold
founder & cto
http://www.adaptiveblue.com

"Nickolay Ponomarev" <asqu...@gmail.com> wrote in message

news:mailman.7999.11618110...@lists.mozilla.org...