[edbrowse-dev] spec > highspec

[edbrowse-dev] spec > highspec

[Kevin Carhart]

I'm not sure if I found the answer to the baseball display problem, or 
just a truism. 
Suppose that the specificity check at line 3044 of css.c 
read spec > highspec instead of spec >= highspec?
I tracked down several sets of display:block that don't get applied, and 
when they don't get applied, spec=highspec.  Loosen the threshhold by 1, 
and you get a lot of content.

[edbrowse-dev] spec > highspec

[Karl Dahlke]

I made the change, compiled, and got exactly the same result on the baseball site,
and acid test 0 failed, which is sort of how I remembered it,
and that's why I wrote it that way.

Test 00 failed: expected 'pre-wrap' but got 'x-bogus' - found unexpected computed style

Karl Dahlke

Re: [edbrowse-dev] spec > highspec

[Kevin Carhart]

That makes sense, oh well.  Onwards and upwards!


On Mon, 3 Jun 2019, Karl Dahlke wrote:

> I made the change, compiled, and got exactly the same result on the baseball site,
> and acid test 0 failed, which is sort of how I remembered it,
> and that's why I wrote it that way.
>
> Test 00 failed: expected 'pre-wrap' but got 'x-bogus' - found unexpected computed style
>
> Karl Dahlke
>