Kevin Gibbons

better support for concrete methods

2

I feel like this is already an open issue, but I couldn't find it, so making it again I guess. We need to make concrete methods linkable and have some...

This is mostly useful when navigating the spec as multipage. Also we should surface its existence somewhere probably.

To make it more clear this is a nested function rather than something being executed right now maybe even make them collapsable! cc @syg

richer biblio

1

Once https://github.com/tc39/ecma262/pull/545 lands we'll have a lot of information about AOs in machine-consumable form (and hopefully more over time), some of which could be included in the biblio file. That...

Continuing discussion from [here](https://github.com/tc39/ecmarkup/pull/301#issuecomment-787398659), I read [this page](https://developers.google.com/search/docs/advanced/crawling/consolidate-duplicate-urls) to imply that `

In ecma262, the table of contents is 400kb of HTML to represent 76kb of text plus a little structure. We can cut that down. A lot of the overhead is...

ecmarkup makes links of the form ``. These work, but are arguably "[invalid](https://url.spec.whatwg.org/#fragment-state)" in the sense of "the URL spec says to produce a validation error". We could choose to...

As in it's literally on top of other content, which (among other things) means C-f will not scroll the page if the thing you looking for is under the pane,...

I'm told, though I haven't confirmed this, that a proposal which references a production such as `ObjectLiteral` which is redefined in Annex B, the proposal will link to the Annex...

See https://github.com/rbuckton/grammarkdown/issues/33.