From f9390c9cc6d37b98d5f4d43ec45441fef8f6a77f Mon Sep 17 00:00:00 2001 From: "Alex A. Naanou" Date: Fri, 20 May 2016 16:54:51 +0300 Subject: [PATCH] experienting almost done... Signed-off-by: Alex A. Naanou --- ui (gen4)/features/ui.js | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/ui (gen4)/features/ui.js b/ui (gen4)/features/ui.js index 0fd23c72..9347e9bd 100755 --- a/ui (gen4)/features/ui.js +++ b/ui (gen4)/features/ui.js @@ -1823,6 +1823,7 @@ var ControlActions = actions.Actions({ })], // XXX still a bit lagging behind in chrome -- can we go faster?? + // ...appears similar to iScroll on chrome on desktop... // XXX idea: can we use scroll to place ribbons horizontally? // ...the bad side to this is that it will require us to add an // extra container per ribbon and somehow disable the scrollbar @@ -1833,6 +1834,15 @@ var ControlActions = actions.Actions({ // ...the main advantage here is that the browser will do all // the heavy lifting and do it faster than we can ever hope to // do it in JS... + // Experiment result: + // - more uniform and fast across browsers + // (except FF -- can't disable scrollbars, need to cheat) + // - less controllable + // - is affected by scaling in a bad way... + // Conclusion: + // - this again brings us to using code to control the scroll + // which in turn defeats the original purpose of avoiding + // extra complexity... // XXX this is really slow/buggy on IE and odd on FF... toggleRibbonPanHandling: ['Interface/Toggle ribbon pan handling', toggler.Toggler(null,