Re: Atari build 5032: cache folder
Hi Peter, Did you try 5033 build? In my case cache is not deleted. As I understand in your case NetSurf just throws an error and then it runs so you can surf the web? Vido V V pon., 9. mar. 2020 ob 20:54 je oseba Peter Slegg < psl...@scubadivers.co.uk> napisala: > Hi Vido, > > From a quick look at the commit, I think if there is any issue > with the cache it deletes it. > > > http://git.netsurf-browser.org/netsurf.git/commit/?id=14286b381b12034140768800c7ba10baa7c3b334 > > I suspect it cannot create it again for some reason. > > Peter > > > On Mon, 9 Mar 2020 20:03:08 , Uros Vidovic wrote: > > On my FireBee build 5033 is running. > > Cache folder is present. But I get some other error on the console which > I > > dont remember right now. > > But NetSurf is running fine. > > > > Vido > > > > > > V V sob., 7. mar. 2020 ob 18:06 je oseba Peter Slegg < > > psl...@scubadivers.co.uk> napisala: > > > > > On Sat, 29 Feb 2020 22:33:10 , Peter Slegg > > > wrote: > > > > > > > > I have just installed the Atari test build 5032 and it throws an > error. > > > > > > > > NetSurf failed to initialise > > > > > > > > > > > > I switched the binary back to a previous build but that failed as > > > > well. Investigation showed that the cache folder had gone. > > > > > > > > I re-created it and the older version runs again but 5032 deletes it. > > > > > > > > > > > > Peter > > > > > > > > > > I see there was a change on the 24th Feb that can delete the cache > > > but it looks like the Atari version doesn't re-create it. > > > > > > Peter > > > > > > > > > > > > > > > > > > > > > > > >
forms -- the "required" attribute
I'm setting up an HTML and tried to use the "required" attribute on one input field. (Actually my form consists of only that single field.) Unfortunately "required" has no effect in Netsurf (#5033 on Ro 5.25). The user can get away with just clicking Submit without entering any data. In the Netsurf documentation, the section on web standards says "Forms: nearly done". I presume this attribute is one of the undone-yet! I tested my form on Chrome (on Android fone), and it rightly did not allow Submit to be clicked before the user filled in the field. In fact Chrome zooms in on the field and pops up a tooltip-like box pointing to it saying something like "You must fill in your name". I don't suppose RiscOS can do the tooltip thing, but maybe Netsurf could put a similar message at the bottom of the window where we usually see "Done (0.1s)" -- maybe even in flashing red? Or a message in the field itself -- like the "placeholder" attribute. By the way, it would be nice if Netsurf could automatically blank the "placeholder" text (as other platforms do) when the user begins to type something in the field. Of course Ctrl-U does the trick in RiscOS, but it has to be done manually or else the placeholder text gets submitted along with what's typed. (And naive users might not know the Ctrl-U keystroke.) I found detailed specs here but haven't yet tried everything: https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/required Cheers. And thanks again to the faithful dedicatees on the Netsurf crew for all their work over many years! -- Jim Nagelwww.archivemag.co.uk
Re: forms -- the "required" attribute
On Tue, Mar 10, 2020 at 04:23:30PM +, Jim Nagel wrote: > I'm setting up an HTML and tried to use the "required" attribute on > one input field. (Actually my form consists of only that single field.) > > Unfortunately "required" has no effect in Netsurf (#5033 on Ro 5.25). The > user can get away with just clicking Submit without entering any data. > > In the Netsurf documentation, the section on web standards says "Forms: > nearly done". I presume this attribute is one of the undone-yet! Indeed, however: given that you absolutely must check that the required field has been provided at the server end, this only serves to prevent a round trip and server-side error message rendering. This is important because, well, not all HTTP clients will enforce the required attribute, and people could inject bad data by just using wget or curl. In short, you should be checking at the server anyway. B.
