+1 to better error messages ( and to fixing the spelling for occurred)
Given that the fixes are somewhat long to explain -- we may be better
served by having a "help" link that links to "how to resolve your error" ?
I am seeing the error (Version 19.0.1084.1 dev, on Debian 64bit). Any way
to debug it?
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=131305
------------------------------------------------------------------------
r131305 | m...@chromium.org | Sun Apr 08 00:38:29 PDT 2012
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/generated_resources.grd?r1=131305&r2=131304&pathrev=131305
Correct occured->occurred in generated_resources.grd.
(simple change to cycle the tree, what happened to our whitespace file?)
TBR=sky
BUG=120941
TEST=Occurred spelled correctly in Chrome To Mobile error messages, code
comments.
Review URL: https://chromiumcodereview.appspot.com/10020007
------------------------------------------------------------------------
In my experience, sending to mobile works fine when Chrome has just been
opened. After some time (let's say an hour, but I could be wrong), trying
to send a page will result in this error message being displayed after a
short delay (likely indicating network communication is happening). Any
further attempt at sending a page will result in the error message being
shown instantly upon clicking send. Closing and re-opening the browser will
fix it every time, and it's the only solution I found. I tried signing out
of Chrome Sync and signing back in several times, both on desktop and
mobile, to no avail.
Right now I'm on Chrome 20.0.1105.2 Win7SP1 x64 + CrMo 0.18.4409.2396
Galaxy Nexus with stock Android 4.0.4, but it has been the same for the
past couple of weeks.