Open GoogleCodeExporter opened 8 years ago
I'm experiencing the same issue with Chrome 17.0.963.56, in spite of a
reinstall of the extension.
Original comment by nonnumer...@gmail.com
on 18 Feb 2012 at 11:23
Get involved in
http://code.google.com/p/chrometophone/issues/detail?id=422&start=100 Same
issue.
Original comment by ad...@aerislifestyle.com
on 10 Mar 2012 at 1:40
Look at the app in the market, the What's New section tells you that in the Feb
1, 2012 update the developers changed the behavior to send only links even when
text was selected.
I'm with you. It makes the app almost worthless.
Original comment by dkees...@gmail.com
on 16 Mar 2012 at 3:21
Thanks for the heads up. Guess I'll be keeping my eye out for another solution.
Original comment by traughb...@gmail.com
on 16 Mar 2012 at 3:26
Same issue here, reverted to 2.2 just because of this.
A simple fix is to revert the r298 change that has been done.
https://code.google.com/p/chrometophone/source/detail?r=298#
Though this could have been done to fix a bug.
Original comment by matthieu...@gmail.com
on 23 Mar 2012 at 11:34
The dev actually answered it in issue 417
https://code.google.com/p/chrometophone/issues/detail?id=417#c3
And lists reasons for the change.
Original comment by matthieu...@gmail.com
on 23 Mar 2012 at 11:42
For anyone that is curious (as I was), *both* the link and the selected text
are sent to the phone. The browser opens, but you can also paste the selected
text.
More info:
http://code.google.com/p/chrometophone/issues/detail?id=422#c29
Original comment by fel...@gmail.com
on 3 Apr 2012 at 1:45
[deleted comment]
Please see comment #7 everyone,
Awesome work fel.....
==============================================================================
For anyone that is curious (as I was), *both* the link and the selected text
are sent to the phone. The browser opens, but you can also paste the selected
text.
More info:
http://code.google.com/p/chrometophone/issues/detail?id=422#c29
Original comment by haribom...@gmail.com
on 9 Jul 2013 at 6:33
Original issue reported on code.google.com by
traughb...@gmail.com
on 14 Feb 2012 at 3:25