Teams‎ > ‎Input Team‎ > ‎

Input Objectives

At Google we define and track progress against our goals using "OKRs" (Objectives and Key Results).  Here are most of the OKRs for the input-dev team (a couple minor KRs relating to internal projects such as future Android releases have been omitted for confidentiality reasons).  Note that these are intentionally aggressive and so we will be happy if we deliver 60%-70% of them.

2018 Q1 

Eventing Sub-team

Improve Smoothness and Predictability of Input Events 

Resampling input events at rAF P1 
Predictive Points P2 
Direct Manipulation stylus across all platforms P4 

Add Richness to Web Platform 

User Activation v2 (Simple User Activation) P1 
Ship InputMode P1 
PointerEvent spec - Close out V2, start on V3 P1 
Continue prototype for Worker input event routing P2 
Spec for input for Workers P2 
Improve Android Drag & Drop (crbug.com/156390) P2 
Spec and Ship InputModeAction P3 
Clarify screenX/Y and movementX/Y definitions P4 

Performance 

Hold the line on Input Performance P1 
UKM dashboard P1 
Clean up input metrics P2 

Product Excellence 

Be responsive to our users P1 
Touch Adjustment (crbug.com/625198) P1 
Fix 8 regressions bugs P2 
Fix 6 bugs with >10 stars P2 
Interoperable mouse user gestures (crbug.com/769796) P2 
Rational gesture token handling in Blink (crbug.com/789643) P3 

Code Health 

Complete mojo for input P1 
Make Blink to only expect WebPointerEvent P2 
WebGestureEvent Cleanup P3 

Great Windows 10 experience 

Convert IME to TSF from IMM32 P1 
Use modern APIs to enable Virtual Keyboard P2 
WM_Pointer on Windows platform for all input modalities P3 
Fix noisy mouseleave event in consecutive clicks (crbug.com/798535) P3 

Scrolling Sub-team 

Great Windows 10 Experience 

Windows 10 Precision Touchpad basic support P1 
Windows 10 Precision Touchpad support gesture based navigation P3 

Product Excellence 

Fix impactful bugs P2 
[Stretch] Subpixel precision scrolling on main thread P4 

Improved Code Health 

Flings generated in the browser process P1 
Frame and Element Scrolling Unified P1 
Keyboard scrolls using gesture events P3 

Improve Viewport Interoperability 

Describe visual/layout viewport in an official spec P2 
Settle on an interoperable and compatible way to size the layout viewport P3 
Fix interop issues related to how pages load initially P3 

Add Richness to Web Platform 

Web Apps can compose in views P1 
Ship Scroll Customization Origin Trial P4 

Performance 

Improve understanding of real-world wheel scrolling performance. P3 
Improve Wheel Scrolling Performance P1 

Historical Objectives and Results

Subpages (3): 2015 OKRs 2016 OKRs 2017 OKRS
Comments