Server spell checker doesn't work in textarea if last line is a URL
Reported by
ale...@gmail.com,
Nov 22 2016
|
|||
Issue descriptionChrome Version : 54.0.2840.98 (Official Build) (64-bit) What steps will reproduce the problem? (1) Write following two lines in a textarea (ensure there is no new line at the end): Teh tset. http://www.foo.com/ (2) Save the form. Reload the page with the saved form. (3) Add some typos on the first line after "Teh tset." and notice there is no red squiggle to highlight the typos. (4) Add a new line at the end of the textarea and observe that the spellchecker is now working again. What is the expected result? Spell checker should always work. What happens instead? Spell checker doesn't work in certain scenarios. Please provide any additional information below. Attach a screenshot if possible.
,
Nov 22 2016
This is true only for server spellcheck, i.e., "Ask Google for suggestions"/"Use a web service to help resolve spelling errors."
,
Nov 22 2016
Server-side issue likely, b/33075084
,
Nov 23 2016
I don't have serverside spell check enabled yet noticed the same issue. The simplest test case is to load test.html file as: <textarea rows=10 cols=80> Teh tset. http://www.google.com</textarea> Versus test2.html: <textarea rows=10 cols=80> Teh tset. </textarea> The latter will have squiggly lines, the former won't.
,
Jan 20 2017
Any traction on this? Very annoying to say the least!
,
Jan 20 2017
A minor improvement has been implemented: if you put a period after your sentence (before the URL), it will be spellchecked. More fixes coming in the upcoming months. Fixed: Correctly checkedd. http://crbug.com/667653 http://crbug.com/667653 Still a problem: Not correctly checkedd http://crbug.com/667653 http://crbug.com/667653
,
Jan 20 2017
,
Apr 27 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by ajha@chromium.org
, Nov 22 2016Labels: M-54