Wednesday rant #2

Wednesday rant #2

Didn't find your answer?

I don't know if it is just me, in combination with my OS (WIndows 7) and browser (IE11), but whenever I compose a post on this website (and it is just this website) in rich-text format there is a really irritating delay between my typing to the screen and the characters appearing in the draft message box.

That would not be so bad if the characters were "buffered" so that they eventually appear in sequence as typed.  But what really happens is when I type at speed any characters submitted subsequent to the last character displayed get lost in the ether.  For instance, I type "ether" fast.  The characters "et" are displayed, but I have got to the final "r" on the keyboard before "h" is displayed on the screen, and what eventually appears is "etr".

I can get around it by clicking on "disable rich-text" link at the foot of the composition window.  But would rather not.

Problem does not seem to crop up with really short posts.  Maybe the system is trying to tell me something.

With kind regards

Clint Westwood

Replies (5)

Please login or register to join the discussion.

By Mouse007
25th Feb 2015 16:49

Tuesday rant #2 ?

Today is Wednesday my friend

Thanks (0)
avatar
By nogammonsinanundoubledgame
25th Feb 2015 16:52

Yup

You posted that while I was editing it.

My time sheets currently only go up to Monday :(

Odd that - I can edit the title and the edited title is displayed on the main page, but drill into the thread and it displays the original unedited title.

With kind regards

Clint Westwood

Thanks (0)
avatar
By User deleted
25th Feb 2015 16:54

What the system is telling you ...

... is that IE is not compatible with AW. And it is the fault of the former, not the latter.

Thanks (0)
avatar
By nogammonsinanundoubledgame
25th Feb 2015 17:02

My experience with IE ...

... is that it comes with a lot more configurable settings than alternative browsers, and most problems associated with IE seem to stem from inappropriate settings which, once corrected, remove the problem.  Just a shame that they are not optimally configured in the first place.

This could be the exception, of course.  However as the AWeb site is the only one to display the symptom, my instinct is that AWeb shares some of the culpability.  Not all, I agree, since Chrome does not cause this problem.

With kind regards

Clint Westwood

Thanks (0)
John Stokdyk, AccountingWEB head of insight
By John Stokdyk
25th Feb 2015 17:16

A workaround

Sorry Clint. I'm not an IE user anymore, but I share your pain as there are a number of other input quirks that can make life difficult for regular users of the site.

For example, have you ever typed something into a comment box and accidentally hit a key combination that closes the window or zooms you off to another page? I do, and still don't know how it happens.

To avoid such mishaps, most of us who work on the site type up our content separately in Word or even Notepad and then paste it into the site. It takes slightly longer - but gives you a few moments to review what you've said (for example if you were being a bit intemperate) and leaves you with a back up copy if you are hit by some unforseen accident.

In the meantime, well alert our tech team to your difficulties and see if they are able to add any further information on the causes of your slow keystroke response.

Thanks (0)