RC1 is outstanding!

[Handycam]

Just a note of thanks to the developers, RC1 is an excellent piece of work. Page loads and renders are really fast.

All my rendering bugs seem to have been fixed. I like the clear "box" placeholders for blocked ads and flash.

So far my only crasher has been while using the page inspector. Hopefully moving forward this will be made more stable.

I hope that some pre-5.5 bugs eventually get fixed:
-- disappearing "favorites" folder in bookmarks menu
-- default buttons in dialogs that do not respond to "return"
-- default bookmark folder in prefs stays put

All in all, great work!

[996tt]

Working like a charm for me :)

[philonous]

Well, it's still a memory hog (currently at 142 Mb, and 2% residual CPU usage with nothing happening), but, yes, stability, speed and compatibility are all outstanding. This is a release candidate, indeed.

P

[Forrest]

Well, it's still a memory hog (currently at 142 Mb)

Keep in mind how OS X deals with memory. If you're out of free or inactive memory, then you've got a problem.

Last night OW had nearly 1GB RAM allocated to it. But I still had plenty of inactive and free.

[JKT]

-- default buttons in dialogs that do not respond to "return"
That's a feature of Full Keyboard Access in OS X and probably is not within OmniGroup's control.

[Handycam]

That's a feature of Full Keyboard Access in OS X and probably is not within OmniGroup's control.

That's odd, since I've never seen it before. i would assume that all buttons displayed as "default" (i.e. pulsing blue) should respond to a "return". No?

[Handycam]

CPU usage is OK. 5% while I'm typing this, drops to about 1% when this page is put in background. That's less than iTunes not playing in the background or Default Folder BG.

[Forrest]

CPU usage is OK. 5% while I'm typing this, drops to about 1% when this page is put in background. That's less than iTunes not playing in the background or Default Folder BG.

As has been discussed before, most (all?) of the CPU hogging issues seem to be related to JavaScript and specific sites. So unless you have found a reproducible case and tested that with RC1...

For me, I continue to have the same CPU issues as before. This morning I came to my machine and it had the same crash during the middle of the night that it has for the last many nights. Unfortunately, I visit so many sites during the course of a day I've only found two that are a catalyst to this problem, and one requires an account. There are many others, as I seem to find them on a daily basis.

I would say let RC1 run for a few days, while doing a lot of surfing. I'm betting you will encounter the same CPU hogging as others have.

[JKT]

Edit: Deleted as I had posted some incorrect info.

[Handycam]

try this: on this very page, do File >Saved linked images. Make sure the file save dialog is in list view, choose your desktop (or make a new folder with the "new folder" button). You cannot use the keyboard to activate that blue "Save" button. If I hit "tab" a few times, I can get it to go, but I don't see any highlighting.

[JKT]

For me, the blue focus ring starts around the location pane. Tabbing shifts the blue focus ring to the Save button via the New Folder and Cancel buttons.

[Handycam]

For me, the blue focus ring starts around the location pane. Tabbing shifts the blue focus ring to the Save button via the New Folder and Cancel buttons.

Yes, but have you tried it? Even if you've tabbed to the "new Folder" button, and the button has the blue ring around it, hitting return selects "save", not the "new folder" button (i.e. the dialog closes and the files download).

Try it.

IMO, I shouldn't have to TAB to a button anyhow, if the dialog has a "default" button. hitting return should be the same as clicking on the default button. It's the Mac way!

[JKT]

Use the spacebar to select the button or object with the blue focus ring around it (this is a feature of Full Keyboard Access and the OS and has been this way since 10.3.x). Spacebar is the default key for selecting anything via FKA.

Conversely, you use the return/enter key to select the default blue button in any dialogues, and this is not necessarily the button with a focus ring around it.

Edit: I deleted my prior post as I confused myself over the way it worked (it's late... I'm knackered, yadda, yadda) - the above is the way things work.

[Handycam]

Conversely, you use the return/enter key to select the default blue button in any dialogues, and this is not necessarily the button with a focus ring around it..

That's my point exactly. This is what's broken in OW.

[JKT]

Er... it works for me.

[Handycam]

Are you in column view or list view? Mine only works in column view.

[Stormchild]

Conversely, you use the return/enter key to select the default blue button in any dialogues, and this is not necessarily the button with a focus ring around it..

That's my point exactly. This is what's broken in OW.

Well...that in itself isn't broken. The return key is used exclusively for the default button. It's never supposed to activate the highlighted UI element -- the spacebar has always been the key for that.

I tried the "save linked images" test you suggested, and the return key works. My save dialogs are always in column mode, so I tried it again, and switched to list mode first; after doing that, the return key did not work. However, I hit cancel and tried it again; this time the dialog was already in list mode, and now the return key works fine. It worked fine on both occasions that I hit return without clicking anywhere first. On both of those occasions I hit command-D first to select the Desktop, and that didn't cause a problem. I then tried it a couple more times. I found that if I click to switch to column view, the return key still works. So, if I've isolated this correctly:

The problem occurs only after switching to list view in the save dialog, and only for that particular occurrence. On the next occurence, even if it's in list mode it works fine.

[Handycam]

The return key is used exclusively for the default button. It's never supposed to activate the highlighted UI element -- the spacebar has always been the key for that.

That's what I meant. Sorry if it was unclear. My problem is that in this dialog there is a DEFAULT button that refuses to respond to the RETURN key. Never mind highlights.

The problem occurs only after switching to list view in the save dialog, and only for that particular occurrence. On the next occurence, even if it's in list mode it works fine.

I can't get it to work for me in list view, period. Only in column view. I tried your scenario, and it's still the same: the default button only responds to "return" key in column view.

It's not just this dialog, either. Try File > Open file. Again, in list view, highlight an html file on your HD and hit return. Nothing, even though there is a default "open" button.

[teorema67]

RC1 is outstanding!

YES, it's great :cool:

[JKT]

FWIW, I don't use anything other than column view, so that'll explain why it works for me.

Just tried a little experimenting - if I switch to list view using my mouse, return doesn't do anything. If I press tab (it doesn't matter where the focus ring ends up, just the act of moving it works), the return key will become active and select the default button.

So you're right there is a problem with the return key with list views in OmniWeb dialogues. I had a go with TextEdit and it worked as expected - default button selected straight away.