Arlene, I have had some odd things happening with the floating menu bar and the iPad too. But have not been on ATP enough the last few days to pinpoint when and what is happening to make a report.

Edited to add... I just double checked, and I know it happens when I go back and make an edit to a post on the iPad. That happens a lot because the iPad makes auto correct type changes that I don't notice till I preview or post, so I have to edit. Then the blue bar is right in the way of typing instead of being at the top where it belongs. When I am feeling better, I will try to recreate and take some photos so Dave can see.

>> still using the ESR release (v. 17) of Firefox, rather than updating (currently v. 22).

I installed whatever came to hand a few months ago. Someone here takes the trouble to download modern apps and get them past our IT department (most downloads are blocked, and you have to request It to authorize them for you).

Since FF 17.0.1 works 'well enough" for me, I won't update at work until my buddy grabs another update and pushes it through IT. (Not really like pushing a watermelon through a garden hose, but let's be unkind.)

My work organization actually mandates IE (perhaps IE 7). Most "official" work apps can't even be opened with Firefox or any browser other than IE.. (Yes, I have some partial idea how bone-headed that is.) We're lucky that we're allowed to use FF or whatever for "unofficial" work.

Here's another unrepeatable "glitch report" . I don't think it has anything to do with ATP, but I'll mention it just in case.

I was adding a post to a thread under a tip or Idea. The "Enter" key stopped working! (AKA "Return" key.)

So I typed the reply in Notepad instead and copy-pasted it into the thread. That worked.

Then I tested a post in a forum thread: same thing: "Return" did not produce a newline. neither did the "Enter" key that's part of the numeric keypad.

The cure: exit ATP and re-enter.

That was a bug in your browser, not the ATP website.

Or your keyboard. My Ctrl key stopped working a few months ago, but then I discovered so much loose tobacco under it that I probably could have rolled a couple of cigarettes with the debris.

>> That was a bug in your browser

I believe that.

>> Or your keyboard.

That was my first thought, so i went back and forth between FF and Notepad. It worked in Notepad.

Too bad I didn't, while I had the problem, go to a few other websites with the same session of FF and try multi-line text entry there.

That's one reason I like embedded control SW better than desktop stuff. Embedded code HAS to be simple enough and reliable enough that it doesn't get flaky at 30,000 feet or while you're handling an unexpected situation in the reactor's cooling system.

Everything else bows to clarity and simplicity. Frills, indulgences and support of hundreds of flaky "standards" aren't options. Just do the job reliably, with as many 9s as you put after the decimal point: 99.9999% of the time. And then handle the other 0.00001% safely too.

I don't believe this is a bug but when I go to review the 2 Ligularia images, the display is such that the screen shudders when I scroll to the bottom and keep scrolling. Based on my monitor and settings the display is the perfect size for the custom menu bar to want to display but there isn't quite enough screen. Ctrl+ and the issue is gone.

RickCorey said:>> still using the ESR release (v. 17) of Firefox, rather than updating (currently v. 22).

I installed whatever came to hand a few months ago. Someone here takes the trouble to download modern apps and get them past our IT department (most downloads are blocked, and you have to request It to authorize them for you).

Since FF 17.0.1 works 'well enough" for me, I won't update at work until my buddy grabs another update and pushes it through IT. (Not really like pushing a watermelon through a garden hose, but let's be unkind.)

My work organization actually mandates IE (perhaps IE 7). Most "official" work apps can't even be opened with Firefox or any browser other than IE.. (Yes, I have some partial idea how bone-headed that is.) We're lucky that we're allowed to use FF or whatever for "unofficial" work.

We officially use IE 8. I feel your pain