Forum Discussion
Dev channel update to 82.0.446.0 is live
For me the biggest hole at the moment is the lack of History (and currently open tabs) syncing - especially syncing with the Android version. In fact I'm rather astonished that you released a first stable release still without that very fundamental feature. Yet you put all the effort onto collections syncing when the Android version doesn't even do collections. (It's all very ironic at the moment: desktop Edge does collections but Android Edge doesn't, while Android Firefox Preview does collections while desktop Firefox doesn't. Maybe you and Mozilla should look at syncing desktop Edge with Android Firefox and each give up the other platform.
)
The biggest irritation, that makes Edge feel really sloppy (both Dev and Canary) is that if I have a page open that is full width displayed (no horizontal scroll bar) but long, if I quickly scroll vertically - repeated two fingers flips up or down on my laptop touchpad - the page contents WOBBLE from side to side within the tab frame. It does it a bit when scrolling fast down and a LOT when scrolling fast up. Makes it feel like some shoddily made real world object with poor part size tolerances that wobbles and clatters when it should be solid.
There is zero chance of me using it until:
1 History (and open tabs) syncing between desktop and Android Edge.
2 You get rid of the scroll wobble on fast vertical scrolling, which just feels very disconcerting and like desktop Edge has been coded by amateurs.
3 Android Edge gains either (a) the ability to use the Dark Reader extension, or (b) the built in Settings>Themes>Dark>Darken website function that can be enabled (via chrome:flags) in Android Google Chrome. (built in version preferable, but extension OK if it doesn't bog down performance). I've gotten too sensitive to all the acres of white background websites to use a browser that doesn't have an option to 'dark mode' the actual page contents (Android Chrome has the built in option, while Android Firefox can use the Dark Reader extension); and the importance of having desktop and phone browsers sync means the Android browser needs to be acceptable to consider using the desktop browser (and vice versa).
There are other things, but at the moment those are the top ones for me.
Actually, for me you are in a race with Mozilla at the moment. I'm waiting for the ability to darken websites (as described above), built in or able to use the Dark Reader extension, in both Android Edge and Firefox Preview Nightly (currently I use the extension in current Android Firefox, but that makes it clunky and current Android Firefox is due to be supplanted by Preview soon, or the built in function in Android Google Chrome). Whichever of you. Microsoft or Mozilla. does it first will likely get me using your desktop and Android browser for the foreseeable future.
DavidGB we're actively working on both open tabs and history syncing, which is why they both have grayed out switches with "Coming soon!" in the sync settings page. No timeline we can announce right now though.
For the scroll wobbling, I know for a fact this is something we're tracking since I opened the bug for it
This is something that some hardware experiences more than others, so if you and anybody else who experiences it feel comfortable sharing what devices you have, it could help us. For example, I see it a lot on my Surface Laptop's trackpad.
For the website darkening, we're hoping to bring support for the full flags page to mobile, so in theory, if you can get to it via flags in mobile Chrome, you should eventually be able to do so in mobile Edge, assuming we also bring that particular flag over.
- DavidGBMar 13, 2020Iron Contributormadonion josh_bodner
I've found the source of the wobble and how to turn it off!
The side-to-side wobble on fast scrolling, along with the way it will overshoot the top and bottom of the page then bounce back to the actual top and bottom, is all part of something called the 'Microsoft Edge scrolling personality' which I found in edge://flags. I disabled it, re-started, and now Edge scrolling is rock solid - no side-to-side wobble and no more overshoot of top and bottom. (So vague rubbery scrolling is a 'personality'?)
So that's where the problem is. Leaves the question of whether turning it off loses anything. Horizontal overscroll still steps forwards and backwards through the tab's history (which is a feature I hadn't noticed until looking at this).
Frankly the 'personality' scrolling wobble and overshoot-and-bounce is disconcerting enough that unless turning it off loses something significant I suggest having the option in settings rather than make users have to dig into the flags page. And I would have it DISABLED in the stable channel: as I said before, in its current state it makes Edge feel like some cheap shoddily made machine.- josh_bodnerMar 13, 2020Former Employee
DavidGB ah yes, this must be related to our work to bring scrolling back to where it was in Edge Legacy. Obviously, we still have some work to do! That's why it's behind a flag still.
- DavidGBMar 13, 2020Iron Contributor
Yes the scrolling 'personality' is behind a flag, but the default is currently enabled, as it was set at default, I'd certainly never changed it (or even noticed it before) and explicitly disabling it cured the wobbly, rubbery scrolling. I'm suggesting the default should be disabled for the Stable channel at least, and for us mooks on Dev and Canary it would be better in settings where we can see it, realise it's a thing, and can easily turn it off when we find it too disconcerting. I mean up until i found that flag and disabled it, I just thought the scrolling was generally messed up; I really had no reason to suppose it was being caused by an experiment that needs a lot more work.
As I never used Edge Legacy, what exactly is this scrolling 'personality' supposed to do beyond normal, crisp, responsive and not-wobbling-all-over-the-place scrolling as in Firefox, Chrome, and Edge with the 'personality' turned off? If I had some idea what you're trying to do and what benefit it's supposed to provide I'd be more inclined to go through the performance of digging down to the flag and re-enabling it from time to time to test it.