This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The following concept and type related links point at whatwg specs but should point at the w3c edition of the spec: * alias (concept origin alias) * ASCII whitespace * compound microtask * createContextualFragment() (dom range createcontextualfragment) * effective script origin * encoding * execute a compound microtask subtask * input (the input element) * HTML parsing * load() (dom xmldocument load) * name (of the encoding) * origin * Queue (queue a microtask) * script (the script element) * unit of related similar-origin browsing concepts * utf-8 Just search the source file for links to whatwg.org for a complete list.
The majority of those have been replaced to point to the W3C version, but not all since in some cases the WHATWG version is the ED for the W3C version (e.g. Encoding).
(In reply to Robin Berjon from comment #1) > The majority of those have been replaced to point to the W3C version, but > not all since in some cases the WHATWG version is the ED for the W3C version > (e.g. Encoding). Could you create a new bug that tracks the remaining links needing updates? I'm not comfortable with closing this and leaving the remaining links dangling unless there is something tracking them.
(In reply to Glenn Adams from comment #2) > Could you create a new bug that tracks the remaining links needing updates? > I'm not comfortable with closing this and leaving the remaining links > dangling unless there is something tracking them. I don't mind leaving it as RESOLVED LATER if you want to use it as a tracking bug.
(In reply to Robin Berjon from comment #3) > (In reply to Glenn Adams from comment #2) > > Could you create a new bug that tracks the remaining links needing updates? > > I'm not comfortable with closing this and leaving the remaining links > > dangling unless there is something tracking them. > > I don't mind leaving it as RESOLVED LATER if you want to use it as a > tracking bug. I need some bug that is marked as OPEN that tracks the remaining links.
(In reply to Glenn Adams from comment #4) > I need some bug that is marked as OPEN that tracks the remaining links. Can you clarify the reasoning behind this request? The whole point of LATER is precisely to revisit it for future tracking.
(In reply to Robin Berjon from comment #5) > (In reply to Glenn Adams from comment #4) > > I need some bug that is marked as OPEN that tracks the remaining links. > > Can you clarify the reasoning behind this request? The whole point of LATER > is precisely to revisit it for future tracking. First, unless all aspects of the bug are addressed, then I don't consider it RESOLVED. Second, I am concerned that if not marked OPEN, it will fall through the cracks, e.g., it may fail to be reported as an open issue when doing a director's call. Third, many people who review the bug lists don't look at RESOLVED, but only OPEN bugs. Fourth, I don't see a process item in the WG that indicates that RESOLVED LATER bugs will be reviewed prior to moving the document forward. I'd be happy to raise these points during the next HTMLWG call.