Return-Path: X-Original-To: apmail-allura-dev-archive@www.apache.org Delivered-To: apmail-allura-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3F83B18F3A for ; Mon, 10 Aug 2015 21:32:04 +0000 (UTC) Received: (qmail 91460 invoked by uid 500); 10 Aug 2015 21:32:04 -0000 Delivered-To: apmail-allura-dev-archive@allura.apache.org Received: (qmail 91433 invoked by uid 500); 10 Aug 2015 21:32:04 -0000 Mailing-List: contact dev-help@allura.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@allura.apache.org Delivered-To: mailing list dev@allura.apache.org Received: (qmail 91422 invoked by uid 99); 10 Aug 2015 21:32:03 -0000 Received: from allura-vm.apache.org (HELO allura-vm) (140.211.11.147) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Aug 2015 21:32:03 +0000 Received: from allura-vm.apache.org (localhost [127.0.0.1]) by allura-vm (Postfix) with ESMTP id 8E46F2801C1 for ; Mon, 10 Aug 2015 21:32:03 +0000 (UTC) Content-Type: multipart/related; boundary="===============8163852621765766235==" MIME-Version: 1.0 To: dev@allura.apache.org From: "T. Bug Reporter" Reply-To: "[allura:tickets] " <7954@tickets.allura.p.forge-allura.apache.org> Subject: [allura:tickets] #7954 new markdown editor fails to trigger browser spell checkers Message-ID:

Sender: tickets@allura.p.forge-allura.apache.org In-Reply-To: <55c58a1e6d19cd05b72746e1.tickets@allura.p.forge-allura.apache.org> References: <55c58a1e6d19cd05b72746e1.tickets@allura.p.forge-allura.apache.org> Date: Mon, 10 Aug 2015 21:32:03 +0000 (UTC) --===============8163852621765766235== Content-Type: multipart/alternative; boundary="===============1277875413908568454==" MIME-Version: 1.0 --===============1277875413908568454== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Is there any way to turn off this "SimpleMDE editor", and go back to a regular text box? For me (and I suspect for others as well), the loss of the spell checker far outweighs the other improvements. Now I have to compose messages in a separate program and paste the text in, which means I don't ever get to use these improvements. --- ** [tickets:#7954] new markdown editor fails to trigger browser spell checkers** **Status:** open **Milestone:** unreleased **Created:** Sat Aug 08, 2015 04:48 AM UTC by T. Bug Reporter **Last Updated:** Mon Aug 10, 2015 01:53 PM UTC **Owner:** nobody >From (that posting apparently failed to get anyone's attention there in the past week, so I'm cross-posting it here): > With yesterday's [2015-07-30] change to the message input form (i.e. the box I'm typing this into now), I find that my browser (Firefox 39) no longer invokes its spell-checker while I'm typing. If I right-click the text area, I still get "Check Spelling" as an option, but clicking that does nothing. The problem is apparently specific to this new form, because other input boxes (such as the one at https://sourceforge.net/support) still flag misspelled words. > > Also, it's not specific to Firefox, or to newer browsers. I tested with Chrome, and with old installations of Opera 12 and Safari for PC, and found the same behavior in all of them. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============1277875413908568454== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

Is there any way to turn off this "SimpleMDE editor", and go back to a regular text box? For me (and I suspect for others as well), the loss of the spell checker far outweighs the other improvements. Now I have to compose messages in a separate program and paste the text in, which means I don't ever get to use these improvements.

[tickets:#7954] new markdown editor fails to trigger browser spell checkers

Status: open
Milestone: unreleased
Created: Sat Aug 08, 2015 04:48 AM UTC by T. Bug Reporter
Last Updated: Mon Aug 10, 2015 01:53 PM UTC
Owner: nobody

From https://sourceforge.net/p/forge/site-support/10975/ (that posting apparently failed to get anyone's attention there in the past week, so I'm cross-posting it here):

With yesterday's [2015-07-30] change to the message input form (i.e. the box I'm typing this into now), I find that my browser (Firefox 39) no longer invokes its spell-checker while I'm typing. If I right-click the text area, I still get "Check Spelling" as an option, but clicking that does nothing. The problem is apparently specific to this new form, because other input boxes (such as the one at https://sourceforge.net/support) still flag misspelled words.

Also, it's not specific to Firefox, or to newer browsers. I tested with Chrome, and with old installations of Opera 12 and Safari for PC, and found the same behavior in all of them.

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============1277875413908568454==-- --===============8163852621765766235==--