Suggestions for Updates to Apple Communities.

rccharles wrote:

My request is to have an option to turn off the Jive spell checking facility.

The option is already there. If you don't turn on the ASC spell checker (by clicking on the 'abc' tool) it won't be turned on. Beyond that, what, if any, spell checker is turned on is something users set in the browser application they use to access ASC content.

If you use a browser app that supports the OS X spell checking service in the standard way (IOW, according to Apple's OS X developer guidelines), that setting will persist. If it doesn't, that is an issue in the browser app you use. Jive can't do anything about that.

If you instead want to be able to turn off the Javascript that drives the Jive popup insert/alignment menu on right clicks that interferes with the OS X contextual menu, that might be possible. (I would prefer to have this option myself.)

If you use a browser app that supports the OS X spell checking service in the standard way (IOW, according to Apple's OS X developer guidelines), that setting will persist. If it doesn't, that is an issue in the browser app you use. Jive can't do anything about that.

ibvious

Notice how there are two text input boxes in the screen image. In the edit relpy box, the word isn't underlined. Notice how the second box the misspelled word ibvious is underline in dots. That means the built in Mac OS system spell checking is working in one box but not the other.

I saw that image the first time you posted it. It doesn't change anything to post it again. If TenFourFox isn't using the OS X spell checker consistently or its settings don't persist, the problem is in the code for TenFourFox.

Anyway, the United States English Spellchecker add-on for Firefox is here:

https://addons.mozilla.org/en-US/firefox/addon/united-states-english-spellche/

Works great.

Works here as soon as you misspell without needing to right click or do anything, as the FF spellchecker did on the old forums?

No, it doesn't work like that here.

You have to enable it to use it, and you have to enable it not only for each post you make, but every time you switch editors, and every time you edit a post.

In the simple editor, a right-click, secondary tap (trackpad) and control click bring up the FF contextual menu where you can enable the spell-checker.

In the advanced menu, you can only bring up the FF contextual menu to enable the spell-checker if you click/tap within the Reply field, below any text you've entered. Within the text, I need to click holding the control key to bring up the FF contextual menu because a secondary (two finger) tap on my (BetterTouchTool powered) MBP trackpad brings up the Jive contextual menu.

It does work, though. You just need to write your post, then control-click (right click) to enable. Don't know if that's any better than the supplied spell-check button in the Reply toolbar, but it's an easy habit to get into.

It is disappointing that FF doesn't use the OS X spell checking or other text services like Snow Leopard's text replacement. If it did, it would not be necessary to enable spell checking more than once, words added to the user's custom spelling dictionary from any app would be recognized as OK, & the UI would be more consistent overall.

Snow Leopard's text replacement service is something else I depend on, especially here. I have a bunch of three character shortcuts for phrases I frequently use here. For example, I never type out "Snow Leopard," "Migration Assistant," or "Disk Utility." I type @ followed by SL, MA, or DU & they are automatically replaced with those phrases. I've also got ones for common typos like "teh" for "the."

If FF supported these services I might use it but as it is I won't.

It is disappointing that FF doesn't use ... text services like Snow Leopard's text replacement.

Been using TextExpander for years (since it was Textpander). It works system-wide, so a redundant feature in 10.6, IMO.

Thanks for the instructions. I'm resigned to just using the Jive one for now, if I can even remember to use it. I suppose we'll just have to get used to seeing more typos from those not using Safari. Not the end of the world, I suppose.

People have reported problems with next & previous icons not going to the expected post. Here's how I am able to get it to fail consistently.

This sequence seems reproducible

1. Start off from your discussions list
2. With this thread, Suggestions for Updates to Apple Communities, click on the time of the last post in the Last Post column. This goes to the last post. Problem: the number of the page of the last post isn't highlighted. In this case, 8 should be highlighted.
   I might add, usually. When I went back to the your discussion list and click on the time of this post that was less then a minute, the software went to the top of of the last group. Scrolling to the bottom, my post was not there. Clicking next, added my post to the bottom of the new page.
3. Click previous button. Problem: Goes to wrong page (group of posts) Notice you start on page 8 but previous takes you to page 6.
4. Click on page 8. Problem: You get a different post as the first post in the group.

WZZZ wrote:

I suppose we'll just have to get used to seeing more typos from those not using Safari.

Chrome also supports OS X text & spelling services. FireFox & Opera do not. I'm not sure about any other browsers.

What I've noticed is a marked inconsistency between the various browsers and I am wondering if there could be an element of partisanship towards Safari. In Firefox, for example, I cannot auto log in as easily as I can with Safari and once in a particular discussions sector I cannot easily flick between different posts … pressing the back button finds me back at that particular sector's main listing rather than earlier posts in the thread. In Safari this is not a problem.

I think that if Apple want to promote the discussions alongside Safari as the recommended browser, it might be a good idea to say so; outright.

In any browser, clicking its back button takes you to the page previously viewed. So if you were in a Community or Widget view listing different discussions & clicked on one of them to take you to that discussion, clicking the back button would take you back to the (updated) Community or Widget view.

Are you talking about something else?

No; you're right, RC-R, and thank you. I can't explain how I confused the actions but somehow Safari's browser seems so much more manageable with the new discussions pages. This does seem to be backed up elsewhere in this thread, too, however subjective the discussion.

All the same, a simple question. Why shouldn't Apple promote its services with some degree of partisanship towards Safari ... much as another unmentionable outfit appears to favour Explorer?

I think you're not thinking about this right. Apple has no control over how other browsers work. Apple has limited decisions in the implementation of Jive software for this site. If Safari works better here, it is likely that to the extent it can be tweaked, the implementation has been accomplished while using Apple's own browser during development. This just makes sense (to me, anyway).