Boy is the learning curve to the WebIDL spec steep. Thoughts on what would make it more palatable welcome.
-
-
Replying to @tobie
Any particular trouble spots? Or just general "too many moving parts" issues?
1 reply 0 retweets 0 likes -
Replying to @really_bz @bz_moz
it's super large. Some of the algorithms are very abstract. Makes it hard to mentally connect them to what they're trying to solve.
1 reply 0 retweets 0 likes -
Replying to @tobie
OK. Large is hard to address, but I'm happy to add informative "what is the goal?" text to things. Please ask as needed!
4 replies 0 retweets 1 like -
Replying to @really_bz @bz_moz
2 others difficulties come to mind: 1. grasping the overall structure, 2. figuring out what the prerequisites are.
3 replies 0 retweets 0 likes -
I feel like adding scroll spying to the ToC could help (see https://github.com/w3c/tr-design/issues/108 …).
1 reply 0 retweets 1 like -
Replying to @tobie
I'm not opposed to experimenting with something like that, sure.
1 reply 0 retweets 0 likes -
Replying to @really_bz @bz_moz
here's what it could look like. Might need a bit of CSS tweaking, but it already helps quite a bit: https://rawgit.com/tobie/webidl/scrollspy/index.html#es-octet …
1 reply 0 retweets 0 likes -
Replying to @tobie
Not seeing anything special going on with that page....
1 reply 0 retweets 0 likes -
Replying to @really_bz @bz_moz
:( fails on your browser maybe (It tested it on FF on a Mac though)? Are you running it with the ToC on the side?
3 replies 0 retweets 0 likes
I see absolutely nothing happening as I scroll in Firefox, Safari, or Chrome on Mac. And yes, I did click "Pop out sidebar".
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.