Daniel Silverstone, on 14 Aug, wrote:
> On Thu, Aug 13, 2015 at 22:56:41 +0100, Gerald Dodson wrote:
> > Has any one else had this version fail?
>
> It is distinctly likely that current CI builds will cause issues. We're
> undergoing a *huge* JS transition and forcing JS on while we do it. If
> you encounter issues, turn JS off after loading your browser (note it will
> turn on again next time the browser loads).
Is this a RISC OS thing? I have just built nsgtk and that looks OK (briefly
tested caveat etc..) with JavaScript enabled.
--
David Pitt
No comments:
Post a Comment