![]() 39% of the feedback relates to functional issues – specific sites where scrolling doesn’t work as expected, or general issues with wheel, touch, touchpad, keyboard or scrollbar-based scrolling.This bucket can overlap with performance, which also impacts the “feel” of scrolling. 41% of the feedback relates to what we call scroll “personality” – the way scrolling feels, and how it matches underlying operating system conventions and character, etc. ![]() Since releasing the first Canary builds of the new Microsoft Edge, we’ve received over 1000 feedback items ranging from positive encouragement to constructive feedback on various aspects of scrolling.Īnalyzing all the issues allowed us to notice common themes in the feedback: Instead, together with the Chromium community, we are working to deliver meaningful user experience and performance improvements that will be more sustainable over time.īefore we dive into what’s new, let’s look at what you’ve told us about the scrolling so far. One thing is clear from the outset: simply replicating the same Windows OS dependencies (with all its pros and cons) is not feasible, given the high bar for compatibility and cross-platform requirements for Microsoft Edge and other Chromium-based browsers. ![]() With the new Microsoft Edge, we’re working to learn from our past experiences to improve scrolling for both Microsoft Edge and all Chromium-based browsers. In those cases, our users could experience missing or incorrectly clipped content, leading to non-interoperable experiences between browsers – broken sites. Even worse, while processing input and output independently from the browsers main thread improved the responsiveness and allowed for a stable frame rate, it didn’t work great for script that performed updates based on frame updates, leading to jitter, one of the most common pieces of feedback we received at the time.Īs time went on and features were added to the rendering pipeline, some features were incredibly hard to support in this model due to the dependency on the OS compositor – fixed position content with clipping ancestors, content with negative z-index, some z-index: auto scenarios, and CSS filters. However, tight operating system integration meant that we couldn’t bring the experience to other OSes, including previous versions of Windows. This allowed our browsers to introduce class leading smooth scrolling at the time and effortlessly match Windows personality – motion, interaction, looks and feel. In previous releases of Microsoft Edge, we enabled smooth scrolling through tight integration with the operating system Compositor ( DirectComposition) and input APIs ( Direct Manipulation). ![]() In a future post we will describe some of the performance and functional improvements we’ve been working on. In this post, we’ll cover how we’ve improved scrolling personality in Microsoft Edge – scroll animation and how it reacts to your interactions, looks and feel of scrolling.Īdditionally, we’ll summarize themes we’ve observed in your feedback, and outline some of the next steps on our journey. Whether you’re using a touchpad, touch screen, mouse wheel, keyboard, or scroll bars, you want your scrolling experience to be fast and responsive. Scrolling is one of the most common user interactions in a browser, and it’s central to how we experience the web. ![]()
0 Comments
Leave a Reply. |