@chris: just downloaded and checked shortly on my a4k/os4: typing into the forms the ssssaaaaammmeeeee problem like cap, and im using original tooth. then it wasnt able to display www.bahn.de correctly. crashed once. will later do more testing.
bahn.de logged as bug#61 (probably nothing major, but don't have time to investigate it right now)
Keyboard issue - really confused on this. I don't have a OS4-running Classic to test it on. I might see if I can knock together a little 68k program to see if the same thing occurs. If you find out anything else please let me know.
1. Good 2. Odd. Maybe quitting NetSurf and restarting it will also work? I'll put this down to libcurl being rubbish until I come up with a better explanation. 3. OK here, probably the same issue as amigaimpact.org. I'll check it with 2.1 in a minute to check the speed there (running both versions concurrently is impossible) edit speed isn't much different in 2.1 - marginally slower perhaps, but I think the main reason is the density of stuff on that page. 4. If this problem occurs on a website out on the Internet, I'll need the URL and a test username/password. Email me privately. 5. Unable to reproduce. 6. Seen this on a few pages since the change to libpng for PNGs by default. I may well reconfigure my build to go back to using libmng for PNGs, as I never saw this problem until the change. If you can tell me which thread I may be able to work out which file is the problem and where the fault lies.
@Chris: sorry i was not aware of this bugtracker. as for the keyboard bug it appears only inside a content of a page. no gui interaction is affected by that. i have been surfing around a little. most simple amiga pages render correctly and relatively fast. a1k.org has got a few gfx glitches it seems. on bild.de i got a crash after most of it was diplayed. i can imagine i just run out of mem, since its huge, but i havent seen that due to netsurf open on own screen. it usually works fine here up to 1680x1050 too. it could be a neat little thing soon.
@Crhis Sorry, cant fount any GUI prefs :) You mean context menu ? Anyway i cant found anythink about "resize window with contents". I also check netsurf.readme and netsurf.guide and found nothink about (i loose somethink like addition gui-prefs file for netsurf maybe ?)
And one more question, it is possible to set my own Fonts for netsurf somehow ?
ps. write it in netseurf 2.1, No problems with aabbccaa bugs (aos4.1 for me). If not do resizing, works ok looks like.
wawa wrote: @Chris: sorry i was not aware of this bugtracker.
Don't worry about it - I only logged it there so I wouldn't lose the crashlog.
Quote:
as for the keyboard bug it appears only inside a content of a page. no gui interaction is affected by that. i have been surfing around a little. most simple amiga pages render correctly and relatively fast. a1k.org has got a few gfx glitches it seems. on bild.de i got a crash after most of it was diplayed. i can imagine i just run out of mem, since its huge, but i havent seen that due to netsurf open on own screen. it usually works fine here up to 1680x1050 too. it could be a neat little thing soon.
Good to hear - I've not seen it running on OS4 Classic. I'll check bild.de when I get a minute.
Actually I'm wondering whether the keyboard issue is an OS4.0 thing - cap, are you running 4.0 or 4.1?
And one more question, it is possible to set my own Fonts for netsurf somehow ?
Open Resources/Options in Notepad (there will be a GUI for this when I get round to it) Look for the font_ options near the top of the file. They will all be set to Deja Vu something-or-other. Change them to whatever you like.
Quote:
If not do resizing, works ok looks like.
Good, that means I know what causes it. Not sure how to fix it yet.
A-ha! Something must have changed between 4.0 and 4.1 then. I need to get my AmigaOne back together, and when I do I'll install 4.0 back on it so I can check this.
That page doesn't contain any PNGs. If I do a complete save and load the files individually locally, they all open. Probably amiga.org is sending the wrong MIME type for a couple of files.
@chris: since now im testing 68k netsurf port in parallel i have got some comparison. both bahn.de and bild.de sites pose the same or similar problems to 68k sdl port. the only difference on 68k is that the problems do not lead to system lockup. therefore i suppose both are general netsurf issues and should perhaps if confirmed be handed over to the netsurf core dev team to fix.