Re-work CSS parsing logic.

[jgerigmeyer]

[jgerigmeyer]

Update parsing to start with anchor()

[jgerigmeyer]

@sanajaved7 @oluoluoxenfree I have a number of questions, and it may make sense to talk through them together on a call -- perhaps tomorrow after check-in?

[jgerigmeyer]

We should check whether this is position-related -- if not, then we need a regular math polyfill for it (instead of positioning).

[jgerigmeyer]

Putting this on hold for now, while we reconsider our approach to parsing stylesheets (see: https://oddbird.slack.com/archives/C03K136KX2A/p1661273459265879).

[mirisuzanne]

@jgerigmeyer what's most helpful for me to understand or review here? Is a functional review helpful, or is there something I should be digging into code-wise?

[jgerigmeyer]

@jgerigmeyer what's most helpful for me to understand or review here? Is a functional review helpful, or is there something I should be digging into code-wise?

@mirisuzanne There's not a lot functional to review yet (other than looking at what's logged to the console, and comparing that with the demo stylesheets). You could skim the code (mostly the changes in parse.ts and fetch.ts), and/or take a look at the console logged data object (which should represent an extraction of the relevant data from the stylesheets).

[jgerigmeyer]

@sanajaved7 @mirisuzanne I think this is ready for review, then merge into #19?

[mirisuzanne]

looking good!