Compile failure on Win, Mac and Precise64 beta builds for official.desktop.continuous builder

Link to Build:
--------------
https://uberchromegw.corp.google.com/i/official.desktop.continuous/builders/precise64%20beta/builds/2490
https://uberchromegw.corp.google.com/i/official.desktop.continuous/builders/mac%20beta/builds/2703
https://uberchromegw.corp.google.com/i/official.desktop.continuous/builders/win%20beta/builds/2628

Link to Log:
--------------
https://uberchromegw.corp.google.com/i/official.desktop.continuous/builders/precise64%20beta/builds/2490/steps/compile/logs/stdio
https://uberchromegw.corp.google.com/i/official.desktop.continuous/builders/mac%20beta/builds/2703/steps/compile/logs/stdio
https://uberchromegw.corp.google.com/i/official.desktop.continuous/builders/win%20beta/builds/2628/steps/compile/logs/stdio


Error Log:
----------
FAILED: ninja -t msvc -e environment.x86 -- "C:\b\depot_tools\win_toolchain\vs_files\95ddda401ec5678f15eeed01d2bee08fcbc5ee97\VC\bin\amd64_x86\cl.exe" /nologo /showIncludes /FC @obj\third_party\WebKit\Source\core\input\webcore_dom.EventHandler.obj.rsp /c ..\..\third_party\WebKit\Source\core\input\EventHandler.cpp /Foobj\third_party\WebKit\Source\core\input\webcore_dom.EventHandler.obj /Fdobj\third_party\WebKit\Source\core\webcore_dom.cc.pdb 
c:\b\build\slave\win_beta\build\src\third_party\webkit\source\core\input\eventhandler.cpp(194): error C2039: 'toLocalDOMWindow': is not a member of 'blink::EventTarget'
c:\b\build\slave\win_beta\build\src\third_party\webkit\source\core\frame\eventhandlerregistry.h(16): note: see declaration of 'blink::EventTarget'
ninja: build stopped: subcommand failed.

C:\b\depot_tools\python276_bin\python.exe C:\b\build_internal\scripts\slave\.recipe_deps\depot_tools\gsutil.py cp file://c:\users\chrome~1\appdata\local\temp\tmpo_u1g8 gs://chrome-goma-log/2016/04/26/win-29-m0/ninja_log.win-29-m0.chrome-bot.20160426-080834.4056.gz
Copying file://c:\users\chrome~1\appdata\local\temp\tmpo_u1g8 [Content-Type=application/octet-stream]...
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 0 B/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 72 KiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 144 KiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 216 KiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 288 KiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 360 KiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 432 KiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 504 KiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 576 KiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 648 KiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 720 KiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 792 KiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 928 KiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 1.04 MiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 1.17 MiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 1.3 MiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 1.44 MiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 1.57 MiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 1.7 MiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 1.84 MiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 1.97 MiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 2.1 MiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 2.23 MiB/2.34 MiB    
Uploading   ...log.win-29-m0.chrome-bot.20160426-080834.4056.gz: 2.34 MiB/2.34 MiB    

Copied log file to gs://chrome-goma-log/2016/04/26/win-29-m0/ninja_log.win-29-m0.chrome-bot.20160426-080834.4056.gz
Visualization at http://chromium-build-stats.appspot.com/ninja_log/2016/04/26/win-29-m0/ninja_log.win-29-m0.chrome-bot.20160426-080834.4056.gz
step returned non-zero exit code: 1
@@@STEP_FAILURE@@@


--------------------------------------------------------------------------------
started: Tue Apr 26 07:54:44 2016
ended: Tue Apr 26 08:08:41 2016
duration: 13 mins, 56 secs
status: FAILURE
status reason: 

dtapuska@, could you please look into this change https://chromium.googlesource.com/chromium/src/+/39e2219e115b217c4d7aba70b5f627026d5a66dd