OWB (1.24/1.3) bugs and feature requests

@Chris

Quote:Unlike in OWB 1.21 the width, and therefore position of the glyhs as well, is correct in OWB 1.22, but the individual glyphs are renderd wrong, especially not wide enough
Since I didn't find out how to display them exactely as in FireFox and Opera yet I've simply made it configurable in OWB 1.23 with the new FONTXDPI and FONTYDPI tooltypes instead and changed the defaults

@joerg

Tested 1.23 and www.hotmail.com dont work. Facebook works as with previous.

Crash on this page download roms
http://nds-roms.com/?act=ndsroms

http://crashlog.os4depot.net/cl45

@Kicko

Quote:Hotmail doesn't even work with Opera (9.50b2).

@joerg

Changed XDPI to 80 which looks fairly reasonable (84 is too wide and 72 is too short).

Can you get your AutoInstall script to detect the prescence of bookmarks.txt and not overwrite it if it exists?

@Chris

Quote:Since there is no bookmark.txt included it can't overwrite it

But if there would be one it of course wouldn't replace it, for example the AmiUpdate AutoInstall script doesn't install OWB icons with new tooltypes either. The only problem will be updates of the 2 (or 3 if I get a fixed libexpat.so) libowbfont.so shared objects, if someone uses the embedded font version updates will replace it by the AmigaOS font version and you'll have to manually copy or rename libowbfontembedded.so to libowbfont.so again. Or I'll have to add a requester in the install script to select the version.

@joerg

Quote:

Hmm, that's interesting, I wonder why mine reverted back to just containing amigans.net? Oh well!

Chris

@Chris

Tested 1.23 on hyperion's site will not allow log on and top of page split off from bottom.
Like the bookmarks though. Nice they stay open after you choose a site.
Also on amiga-news.de/en will only show 3 items per page and not allow you to select showing mre items.

renoir

@Renoir

Quote:The version of WebKit used in OWB Blastoise had a lot of problems with frames, since it's fixed in the current WebKit it should work in the next OWB milestone as well.

Quote:Works here. OWB doesn't have popups for such selections, you have to click them 2 times, use the cursor up/down keys to select an item and if there is no submit button the return key to confirm the selection.

@joerg

Version 1.24 still has the problem with Hyperion, but the font spacing problems are gone. haven't tried other trouble sites yet. 1.23 had trouble downloading from sourceforge. 1.24no problem on sourceforge. OWB with the last 2 version has become the browser I startup first. Only use Ibrowse or Aweb if I need features not yet in OWB - like right clicking and downloading an image from a page or saving a page as IFF. Pages are rendered so much nicer in OWB.


renoir

@joerg

Nice to see the gfx and scrolling optimizations reintroduced .


Scrolling beautifully on my 4000 @ 233Mhz :))

Feature request - Refresh button please

@Chain

I vote for "Refresh button please" too.

@LiveForIt

Me too

Feature request of some kind...

A popup/requester showing until the main GUI is opened at startup so one knows that it is starting... Maybe with version information?

@Valiant

Quote:

Same for me, but with v1.21 and 1.24.

I have used 1.15 and 1.19 successfully before but I can't get these new versions to run. I keep getting ISIs at startup of OWB. Sometimes after the window has opened and drawn its nav bar, but often before any window is opened.

Can someone list everything needed to make it run successfully? I have installed the Cyberbit font and all *.sos (into SObjs:) from v1.21 and v1.24 but it just crashes. Is there anything else I need to do?? I have not downloaded and installed all version throughout time. Can I have missed an .so that is not included now anymore??

There must be something wrong with my install but I can't figure out what

@Deniil
@Valiant

I'm with you guys ... with 1.24 the Grim on startup changed
slightly for me, it still is there, though. ISI's

Try running OWB over and over again, i get there with three
or four instances of the Grim window popping up and then
finally OWB

I'm really keen to know why it does it and what exactly is
different in my system than on nearly every other one where
it runs :-/

Can you guys post the stack backtrace of your grims here,
i don't want to spam this thread, but i'd like to double
check that we have the same bahaviour

It is reproduceable as it *alwaysA crash when i try to start
OWB right after the Workbench is up

Stack trace:

libpthread.so:__shlib_call_constructors()+0x8C (section 1 @ 0x90)
native kernel module elf.library.kmod+0x00007ab8
native kernel module newlib.library.kmod+0x00002a1c
OWB:_start()+0x180 (section 1 @ 0x180)
native kernel module kernel+0x00035be0
native kernel module kernel+0x00035c60

and sometimes i get this:

Stack trace:

module AmigaOS:SObjs/libicuuc-3.4.so at 0x7D8C9D34 (section 0 @ 0x1D38)
module AmigaOS:SObjs/libicuuc-3.4.so at 0x7D92DD58 (section 0 @ 0x65D5C)
module AmigaOS:SObjs/libicuuc-3.4.so at 0x7D92E0FC (section 0 @ 0x66100)
module OWB at 0x7DC71844 (section 5 @ 0x2E1824)
module OWB at 0x7D99C758 (section 5 @ 0xC738)
module OWB at 0x7DC67C18 (section 5 @ 0x2D7BF8)
module OWB at 0x7D9ED088 (section 5 @ 0x5D068)
module OWB at 0x7DC73A00 (section 5 @ 0x2E39E0)
module OWB at 0x7DC73B70 (section 5 @ 0x2E3B50)
module OWB at 0x7DC355E4 (section 5 @ 0x2A55C4)
module OWB at 0x7DC35EC8 (section 5 @ 0x2A5EA8)
module OWB at 0x7DC35F20 (section 5 @ 0x2A5F00)
module OWB at 0x7DC3184C (section 5 @ 0x2A182C)
module OWB at 0x7D9957E4 (section 5 @ 0x57C4)
native kernel module newlib.library.kmod+0x00000de4
native kernel module newlib.library.kmod+0x00002380
native kernel module newlib.library.kmod+0x000028e0
OWB:_start()+0x180 (section 1 @ 0x180)
native kernel module kernel+0x00035be0
native kernel module kernel+0x00035c60


I don't want to step on anyones toes, but i still call the
shared objects implemetantion broken...
(Go on, burn me!)

do you have curl-ca-bundle.crt in Devs: ?

delete the one in S:

@Raziel

Quote:It's not, it's working without any problems for hundreds of users, only you and 2 or 3 others have problems, and in your case with the random ISI crashes which always look like they could be caused by wrong or incomplete data cache flushing or instruction cache invalidating I guess it's the 7457 CPU which, like nearly all others, would need special support (settings, code or even workarounds for specific bugs) in the AmigaOS4 kernel. Maybe I'm wrong and there is special support for the two 7457 revisions used by ACube for the CPU module repairs in the OS4 kernel already, but I doubt it.

@LiveForIt

Quote:An extra button which does exactly the same as activating the URL string gadget and pressing return?