[Edbrowse-dev] css parser

2018-02-14 Thread Karl Dahlke
Some stats: on the monster stackoverflow css, their parser finds 3097 descriptors, mine finds 3711. Who's right? Got me! Of the 3711, there are 153 that I don't understand or haven't implemented. Some of them, like @directives, I'm not suppose to implement. Others I know how to address but it's

[Edbrowse-dev] It's better, but...

2018-02-14 Thread Karl Dahlke
So now I'm using my own css parser and querySelectorAll, and it's better, maybe an order of magnitude faster, and less buggy, but, stackoverflow still takes almost 2 minutes to browse. I keep going back to the fact that 99.9% of the time we don't need this stuff, maybe we never do. Even the

[Edbrowse-dev] css on demand

2018-02-14 Thread Karl Dahlke
As promised, the styles that are created in the original document are now on-demand getters. When you access style it applies the css elements, as though it had done so from the start. You don't know the difference - except we don't waste all that time populating styles that you never look at.

Re: [Edbrowse-dev] css on demand

2018-02-14 Thread Adam Thompson
On Wed, Feb 14, 2018 at 10:59:01AM -0500, Karl Dahlke wrote: > As promised, the styles that are created in the original document are now > on-demand getters. > When you access style it applies the css elements, as though it had done so > from the start. > You don't know the difference - except

Re: [Edbrowse-dev] css on demand

2018-02-14 Thread Kevin Carhart
I was just in startwindow - that's a ton of work! When you access style it applies the css elements, as though it had done so from the start. That's a great idea, which will make a huge difference. ___ Edbrowse-dev mailing list