Skip to content

2361 use new idl buffer prim bigger scope #2367

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

rtoy
Copy link
Member

@rtoy rtoy commented Jul 13, 2021

Make the amendment boxes include the text that is changed. This makes it easier to see the scope of where the change is.


Preview | Diff

domenic and others added 17 commits June 25, 2021 15:44
Updates spec to use new Web IDL buffer primitives.  The changes are
marked as candidate corrections, but we use several correction
amendments to make it easy to see what the new and old text will be.
Using just one makes it super-hard to figure out what controls the
text, and the text sometimes doesn't always clearly show what's
deleted and what's inserted because the links are colored correctly,
and struck-through text doesn't strike through links.  (A bikeshed
issue?)
Change "write" to "allow writing into" so reflects better what
getChannelData allows.
Fix up the script so bikeshed doesn't mangle it.

Add an onload event listener so that when the doc is loaded we can run
ListAmendments to add a list of the related changes for the change
log.
Adjust so bikeshed doesn't mangle it.

Move the listener code into the same script segment so it's easy to
find.
@rtoy
Copy link
Member Author

rtoy commented Jul 15, 2021

This has basically been merged to #2363.
Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants