You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by "T. Bug Reporter" <th...@gmail.com> on 2015/08/08 06:48:32 UTC
[allura:tickets] #7954 new markdown editor fails to trigger browser spell
checkers
---
** [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:** Sat Aug 08, 2015 04:48 AM 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.
[allura:tickets] #7954 new markdown editor fails to trigger browser spell
checkers
Posted by Dave Brondsema <da...@brondsema.net>.
There is an option to enable spell checking in the SimpleMDE editor, but it is not currently enabled due to slow performance. Using the browser's native built-in spell checker doesn't look possible according to this bug report: https://github.com/codemirror/CodeMirror/issues/1017
---
** [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:** Sat Aug 08, 2015 04:48 AM 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.
[allura:tickets] #7954 new markdown editor fails to trigger browser spell
checkers
Posted by Simon Sobisch <No...@allura-vm.apache.org>.
This ticket is still open and unassigned, but this SimpleMDE is a problem for lots of users (still looks different than the resulting post if markup is used, leading to multiple edits (preview option was disabled); no (browser built-in) spell-checker [I **don't** want an additional javascript one], no option to resize and other stuff possible with textareas]).
Why do I have to inspect the textarea with the browser developer tools and remove everything from the Editor component by hand just to get a textarea back? What about a simple button to turn the Editor component on/off (if possible providing the preview option again)?
---
** [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:** Wed Oct 07, 2015 11:17 AM 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.
[allura:tickets] #7954 new markdown editor fails to trigger browser spell
checkers
Posted by Simon Sobisch <No...@allura-vm.apache.org>.
I'll give this another try:
Can we please have a user setting (Account->Preferences) to deactivate the SimpleMDE?
---
** [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:** Wed Oct 07, 2015 11:35 AM 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.
[allura:tickets] #7954 new markdown editor fails to trigger browser spell
checkers
Posted by Dave Brondsema <da...@brondsema.net>.
That issue has been fixed in latest versions, but I think the spell checker is still pretty limited. There's [no way to see correction suggestions](https://github.com/NextStepWebs/codemirror-spell-checker/issues/10) and no way to add words to a local dictionary.
Also when we do it, I'd tweak the CSS a bit to use a border instead of background:
~~~~
::css
.CodeMirror .cm-spell-error:not(.cm-url):not(.cm-comment) {
background: inherit;
border-bottom: 1px dotted red;
}
~~~~
---
** [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 17, 2015 01:45 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.
[allura:tickets] #7954 new markdown editor fails to trigger browser spell
checkers
Posted by Dave Brondsema <da...@brondsema.net>.
- **status**: open --> closed
- **Comment**:
Fixed with https://forge-allura.apache.org/p/allura/git/merge-requests/349/
---
** [tickets:#7954] new markdown editor fails to trigger browser spell checkers**
**Status:** closed
**Milestone:** unreleased
**Created:** Sat Aug 08, 2015 04:48 AM UTC by T. Bug Reporter
**Last Updated:** Mon Oct 07, 2019 11:03 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.
[allura:tickets] #7954 new markdown editor fails to trigger browser spell
checkers
Posted by Igor Bondarenko <je...@gmail.com>.
Issue preventing us from turning spell checking on https://github.com/NextStepWebs/simplemde-markdown-editor/issues/56
---
** [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 09:32 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.
[allura:tickets] #7954 new markdown editor fails to trigger browser spell
checkers
Posted by "T. Bug Reporter" <No...@allura-vm.apache.org>.
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.