As shown by the tools/regen-transformTests.sh script, every time we reparse a large page (like [[en:Barack_Obama]]) we generate different ID values for the about attributes.
This seems to be because the token pipeline is async and thus non-deterministic, and we don't have a final DOM post-pass to ensure a deterministic numbering.
See also T87556: Thoughts on element IDs, sections, incremental parsing and fast section editing.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Ignore failures from latest node in travis | mediawiki/services/parsoid | master | +8 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | None | T93751 RFC: Next steps for long-term revision storage -- space needs, storage hierarchies | |||
| Resolved | • GWicke | T93779 Only store a new render of Parsoid HTML / data-parsoid revision if the content actually changed after a template update | |||
| Open | None | T93715 [EPIC] Make Parsoid HTML output completely deterministic | |||
| Open | None | T206222 Make "about" attribute IDs deterministic |
Change 476582 had a related patch set uploaded (by Arlolra; owner: Arlolra):
[mediawiki/services/parsoid@master] Ignore failures from latest node in travis
Change 476582 merged by jenkins-bot:
[mediawiki/services/parsoid@master] Ignore failures from latest node in travis
Depends on what 'deterministic' means. Because ultimately what templates and extensions generate also influence about id assignment even if tokens are processed sequentially (which they are in the parsoid/php world). Reparses of a page aren't guaranteed to generate same ids because an intervening template could have changed it what it outputs (added / removed an extension which now requires an about id, for ex. or anything else that gets about id assigned to them).