fix(anatomy): V1-2.2 read url() references in their strict spelling only
Security review BLOCK(1): url(#%61) passed the dangling check and the per-view scoping and resolved in browsers. One strict reading now, other spellings are active content; glued names are other functions; the composer refuses an unscoped reference; owner export procedure.
This commit is contained in:
1 parent
5281337412
commit
a678faaa23
13 files changed
+553
-70
No files matched your search
@@ -78,8 +78,10 @@ whole document. Since V1-2.2 (owner decision 2026-10-29) the core writes
|
||||
`fv.<view id>.` in front of every `id` of the drawing and of every local
|
||||
reference to it (`href`, `xlink:href`, `url(#…)`), so each view resolves its
|
||||
gradients, clip paths and `<use>` targets in its own drawing only, never in
|
||||
another view's or in the page; a drawing whose reference names an id it does
|
||||
not define is refused by the reader (`dangling_reference`). The annotation
|
||||
another view's or in the page, and the composer refuses a canvas that would
|
||||
keep a reference outside its scope; a drawing whose reference names an id it
|
||||
does not define, or spells a `url(` any other way than `url(#id)` with optional
|
||||
quotes and spaces, is refused by the reader. The annotation
|
||||
layer carries no `id`. The PDF view keeps the drawing's ids: it is rasterised
|
||||
as a document of its own. The R3 canvas goldens stay frozen; the tests apply
|
||||
this declared change to them (`withIdsScopedPerView`,
|
||||
|
||||
Reference in new issue
Block a user