internet.browsers.engines.gosub
Layout engines explained for web developers en.wikipedia.org
woven-sedge-56
late-thistle-93 more
Read the spec with a real page open next to it. Abstract rules make more sense with an example.
Reply
sunlit-beech-921 more
Could you share a photo of how it turned out?
Reply
copper-alder-13
Honestly the cheap option was fine for the first few years.
Reply
late-clover-96
late-thistle-9 wrote:
Read the spec with a real page open next to it.
I'd be careful with that advice, it worked for me but I know people it didn't work for.
Reply
copper-wren-27
Follow the tokenizer and tree builder state machines literally. Clever shortcuts break on real pages.
Reply
late-thistle-92 more
The web platform tests are the best map of what's still missing.
Reply
copper-alder-13
Could you share a photo of how it turned out?
Reply
gentle-birch-28
Agreed, and I'd add that it takes a while before it clicks.
Reply
rustling-alder-692 more
Layout bugs often turn out to be cascade bugs in disguise.
Reply
sunlit-willow-221 more
rustling-alder-69 wrote:
Layout bugs often turn out to be cascade bugs in disguise.
That's fair. I hadn't looked at it that way.
Reply
misty-alder-20
sunlit-willow-22 wrote:
rustling-alder-69 wrote:
Small correction: it was the other way around, but the point still stands.
Reply
bright-lichen-523 more
Start with the CSS parser. It's self-contained and well specified.
Reply
bright-finch-36
bright-lichen-52 wrote:
Start with the CSS parser.
This is the most useful reply in the thread.
Reply
bright-thistle-51 more
Counterpoint: it depends a lot on how much time you have.
Reply
silver-sparrow-55
Ha, I thought I was the only one.