HORRIBLE new User Interface of Apple Communities

You can act more quickly than Apple will. You can see by applying the css fixes that the fix are available and easy to install yet Apple has not implemented them.

Apple indicates they will be making more changes. They want to move to making smaller changes, but making the changes more quickly.

I do not know how much they acknowledges the user experience difficulties users are experiencing. Apple acknowledges that the user are experiencing difficulties with the new design. They have not listed what they believe these difficulties are in the user interface design. They cite one bug fix they have made and mention that they will be making more fixes. Apple cites three things they will be fixing. I'd classify them as bug fixes to the current design.

R

Speaking bug fixes...

Attempt to compare versions of a user tip OR view changes(NEW) to a single version (from it immediate predecessor?)

I get an error trying to do this on my own authored tip in ES-ASC (never went live) - much less compare anyone else's

EDITadded

This has been reported to engineering since early(?) May

BTW, the FontColor was never Black, but rather the same as now = #333333 = a Dark Gray... the difference is that the FontFace has changed to Myriad Set Pro "Thin"

Super! I'm trying out the new no frills editor! R

Works!

[chuckle]

sez WYSIWYG editor is LIVE!!!! AND the Advanced Editor is back (they were working to make it WYSIWYG as a priority)

What you illustrate is the TinyMCE editor failing to completely load... it failed rarely in the OldASC

Of course, the fact that people are experiencing eye strain and the fix is known shouldn't be a worry. I can deal with tiny_mce.

just force the advanced editor til things are sorted out.

r

ps. the simple editor ends up in html mode. General comment, why in the world would you put html in the simple mode when it is working?

AMIGO!

TinyMCE IS Fixed !!! Simple editor is WYSIWYG

The only thing that needs sorting is "why does the full Simple Editor fail to FULLY load sometimes?"

I glad you have gotten in tune with Apple nomenclature 😉. It's curious definition of fixed when it doesn't load.

Tried reply 3 or 4 times in safari. no mods. worked ever time.

Tried reply 3 or 4 times in firefox 47.0. no mods. failed every time. I relied to the same post every time.

another try.

I am not sure that "Jake" has been made fully aware of the issue that you are having

(I had it repeatedly on one occasion... 4th or 5th try the SimpleEd loaded - has not happened since - I am exclusively FF 47.0 Win10 with 'several' add-ons enabled)

You likely would have best luck raising the issue "upstairs" 😉

IMHO, I do NOT believe CSS invoked would have any effect, but possible(?)

What is happening to you:

1. Hit [Reply]
2. a bunch of javascript is
   1. requested from server
   2. is delivered to your computer/browser
3. your browser "runs" the script and does not Completely Finish

You MAY be able to see what part fails by running FF's Web Developer "Debugger" (shows what is successful, cautioned and stopped, neatly color-coded)

In ES-ASC, early on (they started with this format), I was able to participate in a threaded view (not FLAT pref) 'conversation' that 'tiered' enough where the toolbar of the Simple editor got all "mushed together". That alarmed Vicky (ES Manager) enough to kick that upstairs that day.

I keep a lot of screenshots, but apparently not that one.

In practice, that result is VERY hard to do, and even harder to find where it happened because, at some point, the thread goes multi-page which is all FLAT from then on.

Imagine a reply PANE to this post somewhere between 33% and 50% of the width... there is just NO ROOM for this in half the horizontal space