Re: [Edbrowse-dev] nasa slow

[Adam Thompson <arthompson1990@gmail.com>]

On Sat, Feb 10, 2018 at 11:00:44PM -0800, Kevin Carhart wrote:
> On Sun, 11 Feb 2018, Karl Dahlke wrote:
> 
> > > NASA needs it in order to run, right?
> > 
> > No, they don't, and that's the point. It's just a big time waster from our point of view.
> > Acid test 0 needs it, and that's what put us on the trail, remember, but I think that's rare.
> 
> Hmmmm
> 
> But querySelector and querySelectorAll are used in vendor.js or nasa.js,
> right?  These are common.
> 
> So we have a couple of things in third.  It sounds like we're saved by the
> bell for now since you figured out how to do both, which is great, but maybe
> some time in the future if it was necessary, we could delete jotform but
> keep qs/qsa?
> 
> But come to think of it... wouldn't the query-result sets from qsa be
> incomplete if the styles have not been doled out to the elements previously
> and the selector is trying to select by styles?

Yes they would, and worse than that it'd be difficult to spot because there's a good chance things'd
either continue in a broken state or blow up with some sort of type error.
I'm thinking that we'll just have to fix the 3rd party software if it isn't good enough.  Have we contacted
the devs about it to see if they intend to fix it?

Cheers,
Adam.
PS: in order to do almost anything in edbrowse I have to browse with js disabled until I find a broken
site because it's so grindingly slow most of the time, and that's on relatively modern hardware, but
may be that's just the sites I visit... plus there's the js either being horribly inefficient or infinite
on (I think) stackoverflow.com etc which is a real problem (I seem to manually kill edbrowse at least twice
a day at work).  I really should sit down and debug what's going on there.