"infeasible" is recognized as misspelled, suggests "unfeasible" as replacement |
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.26 Safari/537.36 Steps to reproduce the problem: In any text box on any page, type "infeasible". What is the expected behavior? It should be recognized as a correct word. What went wrong? "infeasible" is marked as misspelled, and the context menu suggest replacing it with "unfeasible". Did this work before? N/A Chrome version: 50.0.2661.26 Channel: beta OS Version: ubuntu 14.04 LTS Flash Version: Shockwave Flash 21.0 r0 According to Merriam-Webster, the correct spelling is "infeasible"; "unfeasible" is incorrect.
,
Mar 18 2016
en_US.dic does indeed not contain infeasible. en_AU and en_GB do. FWIW, OED marks infeasible as "now rare" and suggests "unfeasible". ngram viewer prefers "infeasible": https://books.google.com/ngrams/graph?content=unfeasible%2Cinfeasible&year_start=1800&year_end=2000&corpus=5&smoothing=3&share=&direct_url=t1%3B%2Cunfeasible%3B%2Cc0%3B.t1%3B%2Cinfeasible%3B%2Cc0 Which probably means we should have both in the dictionary. Suggested quick fix: enable "Ask Google for Suggestions", which should at least demote it to a grey underline.
,
Mar 31 2016
,
Apr 27 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by rsleevi@chromium.org
, Mar 17 2016