On Thu, Nov 24, 2011 at 01:49:56AM -0500, Jeremy Maitin-Shepard wrote: > What I meant is that setting browser type to content-primary in the late hook > (current default behavior) might not serve any purpose. >
It's a matter of complying with the api.. the xul:browser of the current buffer should always be the one and only type='content-primary' browser in the window. > It seems the problem is the workaround for this problem requires a scrollbar > fix, and from the discussion when I tried to add a scrollbar fix to the > conkeror code it seems that users that intentionally disable the scrollbar may > do it in a number of different ways and the scrollbar fix may interfere with > some of them. > Ah yes, of course. That will prevent us from automating the workaround. > I wonder if these issues affected Firefox and the Firefox developers just > added > workarounds as well. Given that this occurs even when using firefox -app, it > is hard to imagine how firefox could be unaffected. Or is it somehow just due > to us creating the xul elements using JavaScript rather than from an xul > document? The difference could be that firefox uses a xul:tabbrowser while conkeror uses a collection of xul:browsers. -- John Foerch _______________________________________________ Conkeror mailing list [email protected] https://www.mozdev.org/mailman/listinfo/conkeror
