Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

SerenityOS Browser now passes the Acid3 test

twitter.com

Post reply on HN
Print view View original

171–178 of 178 posts

Re: SerenityOS Browser now passes the Acid3 test

#171

Post by kragen »

queuebert wrote: post #166
kragen wrote: post #149

Earlier quoted context omitted.

It's useful for statements like "Firefox 2.0 got 82/100 on the Acid3 test" to have truth-values that don't change over time. The Acid3 test is an important part of the history of the Web, and rewriting history is repugnant.

I meant why was it ever like that?

Its author, Hixie, was only one of the people who decided on web standards, and he didn't win every argument, so some of the behavior that eventually got standardized wasn't the behavior Hixie thought was best at the time he wrote Acid3. He did win most of the arguments by virtue of writing the HTML5 spec, but without the buy-in of browser implementors HTML5 would have been irrelevant. Also sometimes he was wrong about things.

Re: SerenityOS Browser now passes the Acid3 test

#172

Post by easrng »

kragen wrote: post #169
easrng wrote: post #168

Earlier quoted context omitted.

You aren't implementing innerText, you're implementing textContent. Consider the HTML a c d e f . Using textContent results in "acdef", while innerText results in "acd\ne\nf". Implementing textContent is easy: function getText(node, returnArray){ const a = Array.prototype.map.call(node.childNodes, e=>e.nodeType==3?e.data:getText(e, true)) return returnArray?a:a.flat(Infinity).join("") } Which can be golfed down to le…

Very nice! And thank you for the correction about innerText. Still, I think that let getText = n => n.text + n.getchildren().map(getText).join('') + n.tail is nicer than let getText=(n,f=(n,a)=>[].map.call(n.childNodes,e=>e.nodeType==3?e.data:f(e,1)))=>f(n,f).flat(1e333).join("") and not just because it's less strokes.

Most of the reason it's more complicated is because I made it return arrays when recursing and only join at the end because that probably doesn't need as many allocations. The rest of the complication is because the DOM has separate text nodes and the library you're using doesn't seem to. (Oh, and also NodeLists don't have .map so we use the .map from the array prototype) Here's a non-optimized version:

  let getText = n =>[].map.call(n.childNodes,e => e.nodeType == 3 ? e.data : getText(e)).join("")

Re: SerenityOS Browser now passes the Acid3 test

#173

Post by kragen »

easrng wrote: post #172
kragen wrote: post #169

Earlier quoted context omitted.

Very nice! And thank you for the correction about innerText. Still, I think that let getText = n => n.text + n.getchildren().map(getText).join('') + n.tail is nicer than let getText=(n,f=(n,a)=>[].map.call(n.childNodes,e=>e.nodeType==3?e.data:f(e,1)))=>f(n,f).flat(1e333).join("") and not just because it's less strokes.

Most of the reason it's more complicated is because I made it return arrays when recursing and only join at the end because that probably doesn't need as many allocations. The rest of the complication is because the DOM has separate text nodes and the library you're using doesn't seem to. (Oh, and also NodeLists don't have .map so we use the .map from the array prototype) Here's a non-optimized version: let getText =…

Right, I'm saying I think the statically-typed ElementTree approach is superior to the dynamically-typed approach used by the W3C DOM.

Re: SerenityOS Browser now passes the Acid3 test

#174

Post by niutech »

kragen wrote: post #170
niutech wrote: post #165

Earlier quoted context omitted.

Try Ultralight web engine or K-Meleon on Goanna, they are really lightweight.

How much memory do they need to load this discussion thread page?

K-Meleon uses just 58.9 MB of RAM: https://i.postimg.cc/Jz1cy8tG/K-Meleon.png

Re: SerenityOS Browser now passes the Acid3 test

#176

Post by kragen »

niutech wrote: post #174
kragen wrote: post #170

Earlier quoted context omitted.

How much memory do they need to load this discussion thread page?

K-Meleon uses just 58.9 MB of RAM: https://i.postimg.cc/Jz1cy8tG/K-Meleon.png

I object strongly to the use of the word "just" in that sentence!

Basically that's the same memory usage as Blink, WebKit, or Gecko.

Re: SerenityOS Browser now passes the Acid3 test

#178

Post by oscargrouch »

niutech wrote: post #162
oscargrouch wrote: post #145

Earlier quoted context omitted.

> The point is that a lot of sites out there don't need anything more than the web tech of 2 decades ago. With more people being aware of that and using browsers like this, the Google monopoly may weaken. I always thought this was a way to get out of this, that agrees with your vision. First you'll need a powerful force to take back control on defining web standards. This new web standard would be a very simplistic o…

Gemini is one of such simplistic standards.

I think Gemini will have people following it and developing for it, but i think it could have been a little more ambitious and also took tech history a little bit more serious as to not take too much out of what is actually a improvement done on the web that could be a soft fork of the current web with a lot less things, but not as simplistic as Gemini is.

So i don't think Gemini is "it" yet, but at least i liked the audacity and the way of thinking, its on the right direction and actually it should be people like Tim-berners-lee that should actually be leading this, but unfortunately they are lost..

Post reply on HN