I don't think I have the skills to be able to do that myself, but I'd certainly be willing to help/assist in whatever way I can.
On 1 February 2012 22:35, John J. Foerch <[email protected]> wrote: > The minimal test case that I envision would be a XULRunner app that puts > up a window that contains two tabscrollboxes. The first one would be the > control group, that is, an ordinary tabscrollbox with tabs enough to > overflow the window. The second one would be the experimental group, an > identical tabscrollbox, but with the "ordinal" attribute set on the tabs > such that their display order was altered. The experimenter should > observe that the mouse scrollwheel works on the first group, and fails on > the second. > > --John > > On Wed, Feb 01, 2012 at 09:41:27PM -0600, Benjamin Slade wrote: > Ok, what is involved in attempting (a)? > > ----- > Ok, here is my tree of possibilities: > > Problem: use of a mouse scrollwheel to scroll a tabscrollbox fails when > the XUL 'ordinal' attribute has been used to change the display order of > the tabs. > > * a > > Someone with a scrollwheel write a minimal test case XULRunner app and > send it to mozilla. > > * b > > Rewrite tab-bar and new-tabs to work around the problem (ugly!) > > Involves giving up use of the XUL attribute "ordinal", and going back to > more primitive DOM methods of moving things around. nasty idea imo. > > * c > > Tell affected users that they cannot make use of buffer-moving. >
_______________________________________________ Conkeror mailing list [email protected] https://www.mozdev.org/mailman/listinfo/conkeror
