Roadmap

[kaliiiiiiiiii]

all steps are in the format:
[x] do-fix-something | estimated time to fix//code (for @kaliiiiiiiiii )

time assumes 8h/day & 7days/week. I however got school besides => takes significantly longer

those would be the optimal implementations in my oppinion. Some could be shortend//patched&hardcoded into with single scripts as well

• implementations | 4 days
  • WebElements | 17h => 2days
    • improve mid_location calculation | 16h
    • add WebElement.screenshot | 1h
  • Input | 9 days => 1.5weeks
    • add Sendkeys for CDP | 6h
    • add class Keyboard for keydown, keyup, different OS's and KeyboardLayouts
    • add other CDP (scroll, etc) | 16h => 2days
    • patch leaks (new python package, Windows) | 50h => 1week. Patching other os | ??h
    • support options.add_extension() | 1h
  • support prefs | 1h
• sync | 2days
  • move sync to | 16h => 2days
• device metrics emulation | 13days => 2weeks
  • create similar (but async, and using target-execute-script) to Selenium-Injector for driverless | 30h
    • patch webrtc-leak
    • set proxy dynamically
  • apply profiles similar to Selenium-Profiles-source | 30h
  • add class for target-interception | 16h => 2days
  • build backend for driverless-fp-collector, add compression, deploy on webpages, analyze | 16h => 2days
  • add generator for fingerprints (requires previous step) | 16h => 2days
• make options re-useble | 16h => 2days
• add propper tests | 16h => 2 days