It intentionally doesn't support JavaScript to make things faster and much less resource intensive.
Ngl if you just don’t support the majority of modern browser features, it’s not hard to make a new browser.
Not as hard, I agree but reimplementing just CSS sounds like a very special level of hell.
But…that’s just a setting on all the browsers
W. JavaScript was a mistake.
The stuff like Flash, Java applets and Silverlight it eventually replaced were arguably even worse. There's a legitimate need to run client-side code at times, IMHO the mistake was making it so permissive by default. Blaming the language for the bad browser security model is kind of throwing away the baby with the bathwater.
this is why i will write my blog from scratch with absolutely no JS or code execution of any kind
im a bit curious about the cjoice of gtk2 over 3 or 4, but im too eepy sleepy to look deeper rn ill do that later meows >w<
Furry day?
every day is furry day if you're the right kind of linux dev
I think it’s just a place to start:
The browser is currently in Alpha stage
Planned support for systems in the near future: Linux GTK3/4…
o my goodness i didnt even see that hehe >w< it does look cool meow :3
Great to see another brand new browser under active development!
lynx would like a word...
please use https at least for your own website lol
it has https for me
i clicked the link, boom certificate warning
Mozilla failed to build a new browser from scratch. How did they manage that?
They didn't, not yet at least. What's available right now is barely usable.
Thanks @warmaster!
Checkboxes are displayed as input boxes. Well, it's an Alpha.
Tested it with flatfox.ch "Your browser is too old" while it works even with Dillo and Links, seems a useragent-issue.
Ngl if you just don’t support the majority of modern browser features, it’s not hard to make a new browser.
Not as hard, I agree but reimplementing just CSS sounds like a very special level of hell.
But…that’s just a setting on all the browsers
W. JavaScript was a mistake.
The stuff like Flash, Java applets and Silverlight it eventually replaced were arguably even worse. There's a legitimate need to run client-side code at times, IMHO the mistake was making it so permissive by default. Blaming the language for the bad browser security model is kind of throwing away the baby with the bathwater.
this is why i will write my blog from scratch with absolutely no JS or code execution of any kind