ECMA: Realms. #190
Comments
|
Can do. I also plan to try an HTML Scripting module to pull together a lot of this content as I page it all in myself. Hopefully I can even add some value along the way. |
|
If you add value, could you add it to the WHATWG document as well? There's a ton of value in y'all agreeing on verbage around these kinds of things. Especially for the various WebAppSec specs that have a lot of integration points with HTML, tracking the differences between the documents is a lot of overhead. |
|
@travisleithead perhaps you can first maintain DOM Parsing & Serialization again? It's been rather dead since you took over from the WHATWG. I've been considering putting the important bits elsewhere since simple bugs do not seem to get fixed and are causing problems for implementers and new features like Shadow DOM. |
|
@annevk without committing to an order of operations, I'm certainly interested in giving DOM P&S some love again. As a side note, I have been making private updates to the algorithms while writing tests for the spec to make it match reality better--I just need to commit the changes (both spec and web-platform-tests) before returning to the issues list. :) |
…ATWG (#387) * CSP integrations for Issue #201 Had to adapt "resulting URL record" -> "resulting parsed URL" (will fix with changes to 2.5.2 eventually) * Update refs to CSP3 (from CSP1 Note) for Issue #191 Also fix typo 'teh' * Groundwork for realms #190 and scripting updates #165, #189 Importing dependent changes since last sync of WHATWG in mid-Jan. Added JS-related terms * intermediate: translated definitions in scripting section * Imports 3 fetch script algorithms and reorders a few sections to match WHATWG * add algorithms for script creation * WIP: Syncing changes through event handler section * webappapi include mostly synced. script element section remains * syncing changes for the script element * pulling in more required sections for linking issues * Further reducing linking issues * fixes more linking issues * Finally builds CLEAN! * Adding some missing CSP changes * Adding a few more CSP dependencies * All CSP changes validated and builds clean * Removed script modules * tables in DTs don't render nicely; also fixed backtick use in a few places * Fixes for @arronei's PR feedback
* CSP integrations for Issue #201 Had to adapt "resulting URL record" -> "resulting parsed URL" (will fix with changes to 2.5.2 eventually) * Update refs to CSP3 (from CSP1 Note) for Issue #191 Also fix typo 'teh' * Groundwork for realms #190 and scripting updates #165, #189 Importing dependent changes since last sync of WHATWG in mid-Jan. Added JS-related terms * intermediate: translated definitions in scripting section * Imports 3 fetch script algorithms and reorders a few sections to match WHATWG * add algorithms for script creation * WIP: Syncing changes through event handler section * webappapi include mostly synced. script element section remains * syncing changes for the script element * pulling in more required sections for linking issues * Further reducing linking issues * fixes more linking issues * Finally builds CLEAN! * Adding some missing CSP changes * Adding a few more CSP dependencies * All CSP changes validated and builds clean * removing tables from dt elements for readability * Fix a minor bad merge issue
* CSP integrations for Issue w3c#201 Had to adapt "resulting URL record" -> "resulting parsed URL" (will fix with changes to 2.5.2 eventually) * Update refs to CSP3 (from CSP1 Note) for Issue w3c#191 Also fix typo 'teh' * Groundwork for realms w3c#190 and scripting updates w3c#165, w3c#189 Importing dependent changes since last sync of WHATWG in mid-Jan. Added JS-related terms * intermediate: translated definitions in scripting section * Imports 3 fetch script algorithms and reorders a few sections to match WHATWG * add algorithms for script creation * WIP: Syncing changes through event handler section * webappapi include mostly synced. script element section remains * syncing changes for the script element * pulling in more required sections for linking issues * Further reducing linking issues * fixes more linking issues * Finally builds CLEAN! * Adding some missing CSP changes * Adding a few more CSP dependencies * All CSP changes validated and builds clean * removing tables from dt elements for readability * Fix a minor bad merge issue
In order to do things like #189, y'all will need to bring in the concept of Realms from ECMAScript. It would be a good idea to skim through the changes made around https://html.spec.whatwg.org/multipage/webappapis.html#realm-execution-context to see how they've defined that notion in HTML, as it's somewhat foundational to getting HTML to play nicely with ECMAScript.
The text was updated successfully, but these errors were encountered: